Select Page

Analyst says disclaimers are bad becuase:

Any standardized, boilerplate text is a godsend for a malicious network sniffer who’s hell-bent on stealing your secrets. Imagine you are trying to commit corporate espionage by tapping into an ISP’s network and watching all the network packets go by. It would be like drinking from a fire hose: very difficult to select the packets containing email text from the organization you’re targeting. However, if you knew that organization used a standard disclaimer, you could have your packet sniffer search for packets containing that text. It’s likely it would pick up a very large proportion of the messages you’re interested in.

Link here.

I disagree and admit to being somewhat baffled by this article.  A bad guy can just as easily sniff for source IP, the From address, domain, etc.

And even if the message is encrypted,  that data won’t be because it needs to be cleartext in order to be sent — then you would get some of the details regardless of what is done to the message.    

Alex Eckelberry

Fatal error: Uncaught wfWAFStorageFileException: Unable to save temporary file for atomic writing. in /home/eckelberry1966/public_html/sunbeltblog/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:34 Stack trace: #0 /home/eckelberry1966/public_html/sunbeltblog/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(658): wfWAFStorageFile::atomicFilePutContents('/home/eckelberr...', '<?php exit('Acc...') #1 [internal function]: wfWAFStorageFile->saveConfig('livewaf') #2 {main} thrown in /home/eckelberry1966/public_html/sunbeltblog/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 34