jwbensley
Joined 9 years ago
Joined 9 years ago
Classical French Haute cuisine is heavily flavoured with fats (butter and creame) which required a lot of milk to create, i.e. the yield is low considering how much precious milk one had to put in. That was something that was at the time exclusively for the wealthy.
Admitedtly I don't have their data set but I do see it as valid data/an answer. For example, they may have found that in one part of the country (because you can submit your location at the end) everyone uses "baby" and "sprog" and no others and that combination is unique to that area.
I say "mother", why is that not in the list of predefined answers!?!
"Which of these words (if any) would you use for a baby?"
Baby. I say "baby" to describe a baby. How is this also not in the list of common answers!
I say many words for many things, e.g. I also say "sprog" for baby which was one of the predefined answers. What I can't understand is why these predefined answer sets don't contain the question word, do people really use (for example) "baby" less frequently than "sprog" to refer to a baby so it wasn't listed? Seems unlikely to me.
Specifically from the Wiki artical see the Timing Channel section.
Another interesting concept is to hide the bits in the unused options in protocol header fields (see the "Data hiding in TCP/IP Protocol suite by covert channels" section on the same Wiki artical).
I was looking for example code snippets online and found some examples of hiding bits in packet headers but, not in inter-packet timings. I ended up writing a transmit and receive script one afternoon at my desk out of boredom (although, just as a proof of concept to myself, I didn't take the time to refine to the superior levels of the OP, such as bit rate or reliability, as I never intended to use it): https://null.53bits.co.uk/index.php?page=icmp-messages
It would be nice to combine the technique used in some header-bit-packing scripts with the OPs timing based script; whereby one specifies the destination IP we want to communicate to secretly and alter the buffering of packets only to that IP. I never bothered to refine my scripts beyond "Hello World" because the timing based approach requires one to generate traffic that possibly otherwise wouldn't exist between the source and destination IP. Encoding bits in the inter-packet delay of existing "legitimate" flows to the destination would require it to be relatively close in terms of latency.
Edit: sorry didn't understand all the letters in the acronym. I don't think Netflix are bad, Apple I'm on the fence, Goog/Face/Amaz no way.
At the top of the screenshot it says "traceroute from London to ..." - no traceroute program knows where it is in the world!
Also the locations of each hop in traceroute NY > Chicago > Ashburn etc., no traceroute program will know where in the world those IPs are. I suspect the author has guestimated based on the reverse DNS record for the IPs and latency.
Traceroute does have the ability to show you the ASNs in a path but that is based on a WHOIS lookup of the IPs that it's discovering. So it could be wrong by assuming the IP address of each hop was announce by the ASN that owns it.
> I think if you are brought up on mutton, then mutton tastes great
No one has been "brought up on" any kind of meat further ago than the last 100 years or so, people couldn't afford it. People kept animals until they were old and had no other purposes (like milk or wool) before they were killed for meat.