From: beretta@nun-ya-bizness.com   
      
   On 4/29/20 4:19 PM, BYANYOTHER NAME wrote:   
      
    >>   
    >   
    > You're just playing with semantics. By "down" I meant that no data   
    > transfers are occurring because the DNS server at the ISP is blocking or   
    > dropping them. Yeah I can connect, but you cannot do anything unless you   
    > encrypt everything so the ISP cannot get it's hands on your DNS lookups.   
    >   
    > Sorry I offended your sense of word definitions!   
    >   
      
   If you "encrypt your data" for DNS look-ups, then DATA TRANSFERS ARE   
   OCCURRING.   
      
   Initial exchanges of keys, for secure communications, OCCUR IN THE   
   CLEAR. The whole protocol operates in the clear. That's how it was designed.   
      
   You can't encrypt your data BEFORE you exchange temporary keys with the   
   remote computer/server/device.   
      
   Otherwise, it would be like writing the combo to a safe on a   
   sticky-note, putting the sticky note in the safe, closing and locking   
   it, and then mailing it to a friend.   
      
   How is he gonna open it?   
      
   Furthermore, when I turn off the internet for a customer (non-payment,   
   planned cancellation, etc) all the encrypted bullshit in the world isn't   
   going to sneak by the system because we shut off ALL data transfers to   
   the customer's IP address. Nothing in, nothing out. Even encrypted data   
   still has bits in the clear. DESTination IP address data must be visible   
   (internet has to know where to send that encrypted data) and there are a   
   handful of other bits (header sizes, payload sizes, ACK packets, NACK   
   packets, etc) that all must traverse in the clear.  Even if you could   
   come up with a system that could obfuscate all of that, you MUST have   
   the IP address data in the clear. You cannot get around that. That's   
   what is blocked when you are shut-off BY ANYONE.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)