Of course it's possible to write something that's not exploitable. However, it's tougher than most people think. For example, I've seen applications that the authors assumed were not networked whatsoever, and had no special local privilege. However, if the files they read and wrote were stored on a remote file system such as an SMB mount, then their otherwise non-networked program was completely exploitable. John On Friday, December 27, 2002, at 07:46 AM, Rahul Chander Kashyap wrote: > Hi people, > > I've been going through some articles on how to write secure code esp. > from: http://www.shmoo.com/securecode/ > > I am looking for something more specific for the windows platform. Are > there any specific guidelines/standards that one could follow? > > And one more thing...<this one might be intresting ;-)> Is it possible > to write code that is completely secure and not exploitable? > > Thanks for parsing thru my mail :-) > > Regards, > > Rahul Kashyap > > www.nsecure.net > ------------------------ > Layered Defence > ------------------------ > >
This archive was generated by hypermail 2b30 : Fri Dec 27 2002 - 15:48:00 PST