Well, I also have to deal with XP home edition. Plus the network admins wouldn't like 1000 open IIS servers. It'd just make the LAN an attractive target for hackers. The appliction needs to be simple and relatively self sufficient. If I use IIS, I have to give directions to Joe Average on how to set up a IIS server. Not a good idea.
Ravi ----- Original Message ----- From: "Craig Andera" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, September 07, 2002 11:30 AM Subject: Re: [ADVANCED-DOTNET] Encryption and Hashing algorithm choices > > I'm writing a secure P2P application for internal use for file > sharing. > > Because of budget constraints, it wouldn't be feasible to buy new > > dedicated > > server hardware. But it needs to be secure, so files cannot be > intercepted > > by packet sniffers. I have the following requirements for the > algorithms I > > choose. > > Why not leverage HTTPS support in IIS? Then it's all done for you. IIS > is part of both of those OSes, and you'd have to do zero work yourself. > > Security is one of those things like dentistry that is best not to do > yourself. > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
