Date: Mon, 24 Aug 1998 02:46:42 -0400 From: "Brian Haskin" <haskin@ptway.com> To: "Brian Beattie" <beattie@aracnet.com> Cc: <hackers@FreeBSD.ORG> Subject: Re: I want to break binary compatibility. Message-ID: <002801bdcf2b$06858940$0b00000a@brianjr.haskin.org>
next in thread | raw e-mail | index | archive | help
-----Original Message----- From: Brian Beattie <beattie@aracnet.com> To: Mikael Karpberg <karpen@ocean.campus.luth.se> Cc: B. Richardson <rabtter@aye.net>; hackers@FreeBSD.ORG <hackers@FreeBSD.ORG> Date: Sunday, August 23, 1998 9:16 PM Subject: Re: I want to break binary compatibility. >This approach will no no good, if the hackesr can down load a binary, >because they see what has been done. I thought scrambling the syscall >table was good but it also falls to the dowloaded binaty, although it is a >lot harder to decipher. I was thinking you could encrypt all your >binariaes and use a scheme like the compressed executables. unfortubately >this would fall prey to the know plaintext attack. > umm, any decent modern block cipher can withstand a plaintext attack. That being said it really doesn't provide you with much more protection than simply chmoding your executables to execute only, no read access. Because you have to keep the key somewhere on the system and if they can get around not having read access on the executable they can probably read where ever it is you have the key stored. It would also add quite a bit of overhead when opening a program. Brian Haskin haskin@ptway.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002801bdcf2b$06858940$0b00000a>