January 14, 2002 at 6:48 am
What is the best way to configure security & replication so a packet sniffer cannot hunt out the login id and password used by replication. Publisher/distributor is inhouse (behind a firewall), and the subscriber is a machine hosted by an ISP.
Out of all the notes on security, I've never seen anything dealing with this issue.
January 14, 2002 at 7:46 am
With SQL Server 2000, you have the option of putting certificates from a public certificate authority and connecting via SSL. For both SQL Server 7 and 2000, there is the Multiprotocol Net-Library, but I've not seen any documentation on how it fares going through the firewall.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
January 21, 2002 at 12:04 pm
Not sure here either and I'm not sure the multi-protocol will easily pass a firewall.
I'd agree that SSL and public certificates might be your best bet.
Steve Jones
January 28, 2002 at 4:46 am
Ok thanks, I'll look down the SSL route.
February 6, 2002 at 2:08 pm
You may have to have a port added to the firewall that will allow you to pass thru if your network guys are willing to do.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply