Yeah, but the article discusses encrypting packets. Insofar as I could tell, it discussed the premise of encrypting all packets through SSL. I would assume that login information would encompass that as well... I can only assume that SQL Server authentication is natively encrypted, but passing it over ssl would add to the security... That's a bit buttcheek if you ask me though.
-----Original Message----- From: Jim McAtee [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 08, 2001 10:36 AM To: CF-Talk Subject: Re: SQL Server And Datasource Authentication I thought the original question regarded whether or not the username/password, not the data, were encrypted? Jim ----- Original Message ----- From: "Costas Piliotis" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Thursday, November 08, 2001 11:27 AM Subject: RE: SQL Server And Datasource Authentication > Go for it! Wouldn't do me any harm =) > > If he's really concerned, IPSec OR SSL would help. > > Here's a snippet from SQL Server BOL that my help: > > "SQL Server allows data sent between the client and the server to be > encrypted. This ensures that any application or user intercepting the > data ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
