Change in SQL functionality between 7 and 2k
From: James (James_at_south.africa)
Date: 09/26/03
- Next message: Russell Fields: "Beware the SWEN Virus"
- Previous message: Eric Lauzon: "Rename Cluster Domain name Question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 26 Sep 2003 11:48:06 -0700
Hi,
Does anyone know why MS changed the way that the ENCRYPT
('message') function works? I am in the process of
replacing an old authentication method which uses this
function because it works differently between SQL 7 and 2K.
Here's an example: on my computer I have SQL 7 running
alongside a SQL 2K instance. I execute exactly the same
statement against both instances. SELECT CONVERT(VARCHAR
(20), encrypt('mysecret'))
In SQL 7 I get what I expect: bSLL’v4
In SQL 2K I get a unicode translation in clear text:
mysecret or something similar.
I have found no info about this in technet or in the
product info for 2000. I am in the process of replacing it
with more secure methods (if I can get the rest of my
company on-board) but I still want to know what changed
and why the chage wasn't documented.
- Next message: Russell Fields: "Beware the SWEN Virus"
- Previous message: Eric Lauzon: "Rename Cluster Domain name Question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
