johnf wrote: > On Thursday 16 November 2006 10:36, Carl Karsten wrote: >> almost OT if it weren't for the recent mssql wrapper development. >> >> A friend (Tim, who is bummed he missed the dabo talk) just found out he >> needs to connect to a client's Ms Sql server. fine, this will be the 3rd >> ms server he is connecting to from the same linux box. then they said >> something like "we force the link to be encrypted." >> >> Um, is that supported on the linux side? If so, how? >> >> and will it effect connections to MsSql that are not encrypted? >> >> He thinks he found the answers to this, but doesn't want to deal with the >> client until he has a better grip on it. they are kinda slow to respond: >> It took them 6 weeks to get him the hostname/user to connect to, and now he >> is waiting for them to let him though their firewall. he has no MsSql >> box to test on, (only one win box in the office) but he can use mine. I >> can tweak mine if someone will give me a clue what to tweak. >> >> Carl K > Carl, > > Well to my knowledge there are only two types of encryption. > 1. You can use the 'WITH ENCRYPTION" on the views. This does not effect the > data returned. Only the access to the source code for the view is effected. > > 2. Have MS SQL use Kerberos. This will encrypt the data. See Linux > Kerberos... I have never used Kerberos. Normally, this is setup in the > protocols for MS SQL. >
Ed and Uwe - your answers look like the smart way. I think John is onto the answer Tim needs. I thought I had seen a server config dialog that had something like this. I'll dig. Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
