Language:
switch to room list switch to menu My folders
Go to page: First ... 15 16 17 18 [19]
[#] Thu May 19 2022 16:37:38 EDT from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

Well it did specifically call out DNS hijacking as the permissible "remedy", and not actual network hijacking.

Fortunately, secure DNS servers plus DNSSEC were designed to prevent bad actors from altering DNS results in-stream. This is good because now the ultimate bad actor wants to do it.

The more the Empire tightens its grip, the more star systems slip through its fingers.

[#] Thu May 19 2022 18:08:18 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

Right, there are ways around it, but if they stop the unwashed masses, then they consider it a success. 



[#] Thu May 19 2022 18:12:02 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

I take it back there is one way:

Mandate a compromised IP stack + backdoored CPU ( vpro, for example ) on every machine that connects to the network. 

I remember in the old days of dial-up how some companies had their own custom IP stack + software to be able to connect to their service.  Sure, it was not nefarious at the time as it was still the early days, but i was thinking "this could be really bad if used the wrong way"



[#] Fri May 27 2022 09:25:08 EDT from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

Sure, if it was AOL or Prodigy, they had a custom IP stack, but it was only there so you could run "regular" TCP/IP software while using them as a network provider. Most of the others just shipped a skinned version of Trumpet Winsock.

[#] Fri May 27 2022 11:43:01 EDT from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

A few others did too, the 'local' one i used for a while ( i forget the name now, its been too long ) also did it.

I do realize its long ago not everyone did it, etc. bla bla.  Just pointing out that they could do it, again. 



Go to page: First ... 15 16 17 18 [19]