51–60 of 93 posts
My father is a radio lover, a DXer, and sometimes nearly contemplated a ham license. So I grew up with him listening to shortwave and other bands, he explained all the concepts, WWV would be on for two hours at a time (you could literally count every minute). Another fixture was the police/fire scanner that would be on most evenings, especially when we heard sirens. Dad put up a nice rotary Yagi VHF/UHF tower for the…
Quick summary: > Many navigational and meteorological satellites carry a search and rescue (SAR) repeater which is intended to receive UHF emergency locator beacons and rebroadcast them in the L-band or higher. However the repeaters appear to be picking up all sorts of other signals from the ground, including voice transmissions.
Earlier quoted context omitted.
Referring to Navajo code talkers I assume... https://en.m.wikipedia.org/wiki/Code_talker
Which is especially funny, because their communications were encrypted after they encoded them into Navajo.
Earlier quoted context omitted.
Yes, once you form the connection it is secure. The handshake is the part that isn't secure on open airwaves. This is how 'evil middle boxes' mitm connections from corporate networks. Edit to add: yes, there are CA's to sign the bits on a network. There is no CA for the radio, only proprietary ones. These can be reverse engineered, subpoenaed, or bought by state actors. Chances are, if you're broadcasting loud enough…
I think there is some confusion here. HTTPS is secure. Even with MITM attacks. This is because the MITM will not have a valid certificate to provide authenticity for the public key returned. The reason why middle boxes in corp networks can MITM is because the the corp owns the device and has installed their own domain trust to the device. This means the MITM can return a cert and public key that your device will trus…
There is absolutely nothing inherently secure about HTTPS without a secure CA.
Earlier quoted context omitted.
[flagged]
I'd take it easy with the name calling. Your replies in this thread have shown a pretty fundamental misunderstanding of the OSI model, PKI, and encryption in general.
Hmmm. Yes, I'll take my 20 years of experience in this field and see myself out the door... I'm really sucking at explaining this to strangers on the internet.
What did the conversation overheatd in that video say?
Quick summary: > Many navigational and meteorological satellites carry a search and rescue (SAR) repeater which is intended to receive UHF emergency locator beacons and rebroadcast them in the L-band or higher. However the repeaters appear to be picking up all sorts of other signals from the ground, including voice transmissions.
Makes me wonder if these ever were used out-of-spec for transmission deliberately by parties. (Thinking spy stuff but it could also be just hijinx.)
https://www.wired.com/2009/04/fleetcom/ https://archive.ph/1WyGR
https://www.wired.com/2009/12/insurgents-intercept-drone-vid... https://archive.ph/xyW4E
Earlier quoted context omitted.
You are ignoring HTTPS allows people half a world awaywo exchange keys with a server and prevents other people follow interfering other than DoS attacks. >As we all learned in WWII, a code is better than encryption when you need complex PKI to achieve encryption I was never in WWII and I'm not sure what you mean by code as typically that's just encryption but less formalized.
Https works because there is a destination address that goes to a physical network card. Over the air, there is no 'routing'. Alice can intercept my transmission, then literally, just use a more powerful radio to 'talk over me' with her keys. Ergo, MITM. I worked with guys in the military who did this for a living... Radio is like being able to packet sniff (and modify) packets from anywhere.
This could be done with radio too but we don’t because a typical website transfers hundreds of megabytes and the traffic involved in negotiating an encrypted connection is a drop in the bucket, whereas with most radio traffic, it would comprise a much higher percentage of all your radio traffic.
Plus your average radio equipment has a tiny CPU (although this is changing) whereas your phone or desktop computer has hundreds of gigaflops to do all the encryption and decryption math that you want and then still draw a gif.
Earlier quoted context omitted.
You are ignoring HTTPS allows people half a world awaywo exchange keys with a server and prevents other people follow interfering other than DoS attacks. >As we all learned in WWII, a code is better than encryption when you need complex PKI to achieve encryption I was never in WWII and I'm not sure what you mean by code as typically that's just encryption but less formalized.
Https works because there is a destination address that goes to a physical network card. Over the air, there is no 'routing'. Alice can intercept my transmission, then literally, just use a more powerful radio to 'talk over me' with her keys. Ergo, MITM. I worked with guys in the military who did this for a living... Radio is like being able to packet sniff (and modify) packets from anywhere.
Earlier quoted context omitted.
Referring to Navajo code talkers I assume... https://en.m.wikipedia.org/wiki/Code_talker
Which is especially funny, because their communications were encrypted after they encoded them into Navajo.
So they developed a vocabulary of 411 Navajo words to stand for common military terms. E.g., BESH-LO, which is Navajo for "iron fish", meant "submarine".
The vocabulary included a phonetic alphabet to represent the 26 English letters. E.g., the three Navajo words MOASI, TLA-GIN, and BA-GOSHI all represent English words beginning with C (cat, coal, cow). So, they could spell out arbitrary English words not in their vocabulary.
It was secure against an enemy that lacked Navajos and probably didn't even know what language was being spoken or if they were intercepting some weird form of audio scrambling. But, if the Japanese had been able to translate the messages to English, the code would probably not have survived cryptanalysis for long.
https://www.cia.gov/stories/story/navajo-code-talkers-and-th...