Re: crypt(table.field) ?
От | Marko Kreen |
---|---|
Тема | Re: crypt(table.field) ? |
Дата | |
Msg-id | 20010426223227.B3683@l-t.ee обсуждение исходный текст |
Ответ на | Re: crypt(table.field) ? (will trillich <will@serensoft.com>) |
Список | pgsql-general |
On Thu, Apr 26, 2001 at 02:01:46PM -0500, will trillich wrote: > On Thu, Apr 26, 2001 at 05:20:53PM +0200, Peter Eisentraut wrote: > > will trillich writes: > > > > > i know "password" can be used in creating/altering user > > > information (as used via GRANT and REVOKE) but is there any > > > facility within postgres to CRYPT() a value? > > > > See contrib/pgcrypto for hashing functions. > > I've got 7.0.3potato on my debian system, and i've also done ... > Care to explain -- in terms a Debian newbie might grok -- > what "contrib/pgcrypto" means? First contrib/pgcrypto is 7.1-only. It is supposed to be a place for cryptography-related functions. At the moment it contains only hashing and ascii-conversion functions: digest(), encode(), decode(). Now I have released my newer code as separate release (they were not fit for 7.1-in-freeze) and it contains more stuff: crypt(password, salt) - like the crypt(3) in UN*X-like systems for password crypting - DES and MD5-based crypt is supported. gen_salt(type) for above crypt() as generating salts with only SQL is pain. hmac(key, hash_type) is a implementation of RFC2104 "Hashed Message Authentication Code". Sorta passworded-hash. encrypt(data, key, type) with decrypt() - access to raw ciphers with little bit more. They should be used only when you know what you are doing. In the next release they will be renamed to raw_encrypt()/raw_decrypt() and much better encrypt()/decrypt() will be provided based on OpenPGP (RFC2440) - I am still developing this. Also pgcrypto-0.3 should work with both 7.0 and 7.1. -- marko
В списке pgsql-general по дате отправления: