But just cbc a256 with known IV and some preset bytes, and the five eyes even spare the cost for asking birdsite for raw data, for later decr, when they run the relays. Disposable ID is what makes sense, but is something no generation got for free.
We are 24/7 under eyes, since NROL-37 \â—‹/ ,
and i myself doubt without oversight humans would behave most of the time in culture mode.
Most important seam to me to circumvent any form of silencing data form once legal cultures by the new cultures.
At least as long people live that witnessed that different old culture as legal, and just want to talk and post as they where socialized.
Could u compose a valid raw IP packet and encode it HR in HEX?
That was the original rfc, pls compose a valid ip udp paket from 10.0.01 port 1234 to 10.0.0.2 port 1234
Sorry but even the total lenght is wrong, pls www.ietf.org/rfc/rfc791.txt and tell me how an ip packet is composed
This wrong again, and even if i told u the whole ip stack, i fear u will not remember. But just for the record pls compose a valid ethernet udp packet
04 for ip type and 05 for the ip header would be correct so 04 05
Ok they even taught u wrong ethernet types and ip4 types, i guess u will never learn to format a correct packet.
Sorry that ur overlords had misguided u the correct ethenet type is 0800 for IP
Hmm why just lcc, lets make it more easy asume, an simple udp client at 104.0.0.1 port 1234 and greet it with hello
Supose a udp tunnel is at port 10.0.0.7 port 1234 and u want to tcp sync from ur address to 104.0.0.1:1234 where u assume a html site to fetch, how would the HR Hex look like
Or try a tcp one, do you know by now the steps?