| |||||||||||||
Security in the 20-teensSecurity in the 20-teensPosted Feb 2, 2010 1:30 UTC (Tue) by dlang (✭ supporter ✭, #313)In reply to: Security in the 20-teens by jamesmrh Parent article: Security in the 20-teens
this is not was I was saying is missing, what I am saying is missing are controls that would prevent you from inserting 8 bit data into a file of type 'ascii text'
in a network firewall, this would be an application proxy that would check that what you send over port 80 is really valid http (and a really good one would check that it is one of the requests that it has been configured to allow)
(Log in to post comments)
Security in the 20-teens Posted Feb 4, 2010 10:12 UTC (Thu) by dgm (subscriber, #49227) [Link]
Exactly what purpose would this be useful for?
Security in the 20-teens Posted Feb 4, 2010 20:39 UTC (Thu) by dlang (✭ supporter ✭, #313) [Link]
way back up the thread the statement was made that using SELinux for many processes on one machine was as secure as having the processes on separate machines separated by firewalls.
This is an example of capability that you could have to filter communication between apps on different machines that you do not get with SELinux securing things on one machine.
as for what this would be useful for.
if you have apps that expect things to be text files and throw arbitrary binary data at them you may find a flaw in them and be able to do things as the owner of that process. If you make sure that such bad data can not get to the app you eliminate an entire class of exploits.
|
|||||||||||||