![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Navigation
Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
More options
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Computer Warming a Privacy Risk
- Thread starter Rich Tate
- Start date
An interesting read.
My thoughts on this..
While this could easy effect home users that are not using a real firewall, the corporate world is another story.
Most corporate networks incorporate perimeter firewalls will rewrite the packets as well as check for RFC compliance on all traffic transversing the firewall. Future firewalls that run on desktop PC's will more then likely incorporate a level of protection for these types of attacks.
2000/XP/Vista do not have the timestamp option set in the initial handshake (SYN).
An invalid flag returned on the SYN/ACK with the TCP would be detected and discarded for non-compliance with an invalid flag combination, thwarting man-in-the-middle attacks attempting to determine the offsets of devices behind the perimeter firewall.
In addition, with hosts set to sync to an internal NTP server, or syncing with the perimeter device that does not allow NTP pass through, it would be easy to adjust and randomize internal traffic not leaving the network or for traffic that is not being rewritten as it leaves the internal network through the perimeter device.
my 2 cents
- Spuds
My thoughts on this..
While this could easy effect home users that are not using a real firewall, the corporate world is another story.
Most corporate networks incorporate perimeter firewalls will rewrite the packets as well as check for RFC compliance on all traffic transversing the firewall. Future firewalls that run on desktop PC's will more then likely incorporate a level of protection for these types of attacks.
2000/XP/Vista do not have the timestamp option set in the initial handshake (SYN).
An invalid flag returned on the SYN/ACK with the TCP would be detected and discarded for non-compliance with an invalid flag combination, thwarting man-in-the-middle attacks attempting to determine the offsets of devices behind the perimeter firewall.
In addition, with hosts set to sync to an internal NTP server, or syncing with the perimeter device that does not allow NTP pass through, it would be easy to adjust and randomize internal traffic not leaving the network or for traffic that is not being rewritten as it leaves the internal network through the perimeter device.
my 2 cents
- Spuds
stonedwaldo420
Limp Gawd
- Joined
- Mar 30, 2005
- Messages
- 505
There is an amazingly simple solution for this:
Everyone needs to Fold for the [H]!!!
By keeping the CPU @ 100% load, it would be difficult to significantly alter the temp. Sure, you could probably put a slightly heavier load on it, but the change would be insignificant compared to the diff between idle and load.
Every day I find a new reason to Fold for the [H]
Everyone needs to Fold for the [H]!!!
By keeping the CPU @ 100% load, it would be difficult to significantly alter the temp. Sure, you could probably put a slightly heavier load on it, but the change would be insignificant compared to the diff between idle and load.
Every day I find a new reason to Fold for the [H]