| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Pine.LNX.4.61.0503040950040.1609@high-mountain.nihongo.org>
From: snowhare at nihongo.org (Benjamin Franz)
Subject: re: Bios Programming...
On Fri, 4 Mar 2005, Matt Marooney wrote:
> Most Important Requirements:
>
> 1. Multi-protocol monitoring (HTTP, FTP, Chat, File sharing,
> Newsreaders, etc.)
>
> 2. Thin application, does not *noticeably* interfere with normal
> computer operation
>
> 3. Difficult to remove (disregarding all hardware replacements,
> obviously, the person could go get a new computer) without a password
>
> Again, thanks for your helpful input. I assure you, I am not trying to
> create more problems, and I am just like you guys when it comes to
> hatred of spy ware. I've been making a pretty decent living for years
> securing people's computers.
What you want is a IDS/firewall/DSL/Cablemodem gateway/router that packet
sniffs for 'bad stuff' on the wire. They plug their computer into the
gateway and it connects to the net through it.
That won't stop encrypted traffic, but most anything else should be
managable. There are probably off-the-shelf systems exactly like that
already available ("Corporate firewall applicances").
--
Benjamin Franz
"All right, where is the answer? The battle of wits has begun.
It ends when you click and we both serve pages - and find out who is right,
and who is slashdotted." - David Brandt
Powered by blists - more mailing lists