On Thu, 2008-02-07 at 09:42 +0800, Kenneth P. Oncinian wrote: > _If_ there is really an intention to read someone's email message. > (although the original OP clearly states that there is, I can't imagine > someone spending lots of his time decrypting tons of email messages on a > daily basis just for the sake of someone to read it)
the first step (for the company) is to have the emails on hand. if an investigation occurs, then they can request the employee for the keys. if employee refuses, they can go to court (likely the computers used to send email were company property, certainly the network and servers the email traversed were). likely the employee won't give away the keys, in which case, there's an easy case for firing. in any case, most employees won't know anything about encryption, so this isn't likely to be much of a problem most of the time. > Heck, just use public webmail services for personal emails, and if those > are blocked in the http proxy as well, > then just bypass the http proxy. (which are very-very easy to do > nowadays and is one of my problems right now) how are people bypassing your http proxy? where i used to work, (and let me say, this is the right way to do things) everything outbound was blocked by default. routers just wouldn't forward your packets outward if you didn't go through the proxy servers (some privileged users, e.g., the CEO, some developers [i.e., me] and all sysads [of course] had direct routes outward, but most users didn't). there was some discussion here (maybe two years ago) about remote windows boxes being able to route outward. i think because they were remote and so people onsite were cracking the box and getting admin privileges, (or something) and then changing routes or winproxy settings. but that situation was solvable. it wasn't solved because there wasn't sufficient political will to push through a solution. and because windows was involved, i guess :-). tiger _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
