Index: doc/src/sgml/pgcrypto.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/pgcrypto.sgml,v
retrieving revision 1.4
diff -p -u -c -r1.4 pgcrypto.sgml
*** doc/src/sgml/pgcrypto.sgml 5 Jan 2008 13:17:00 -0000 1.4
--- doc/src/sgml/pgcrypto.sgml 17 Jan 2008 09:56:51 -0000
***************
*** 26,33 ****
Computes a binary hash of the given data>.
type> is the algorithm to use.
! Standard algorithms are md5 and
! sha1. If pgcrypto> was built with
OpenSSL, more algorithms are available, as detailed in
.
--- 26,35 ----
Computes a binary hash of the given data>.
type> is the algorithm to use.
! Standard algorithms are md5, sha1,
! sha224, sha256,
! sha384 and sha512.
! If pgcrypto> was built with
OpenSSL, more algorithms are available, as detailed in
.
***************
*** 390,396 ****
PGP encryption functions
! The functions here implement the encryption part of the OpenPGP (RFC 2440)
standard. Supported are both symmetric-key and public-key encryption.
--- 392,398 ----
PGP encryption functions
! The functions here implement the encryption part of the OpenPGP (RFC 4880)
standard. Supported are both symmetric-key and public-key encryption.
***************
*** 657,663 ****
Which compression algorithm to use. Only available if
! pgcrypto> was built with zlib.
Values:
--- 659,665 ----
Which compression algorithm to use. Only available if
! PostgreSQL was built with zlib.
Values:
***************
*** 689,695 ****
Whether to convert \n into \r\n when
encrypting and \r\n to \n when
! decrypting. RFC 2440 specifies that text data should be stored using
\r\n line-feeds. Use this to get fully RFC-compliant
behavior.
--- 691,697 ----
Whether to convert \n into \r\n when
encrypting and \r\n to \n when
! decrypting. RFC 4880 specifies that text data should be stored using
\r\n line-feeds. Use this to get fully RFC-compliant
behavior.
***************
*** 706,712 ****
Do not protect data with SHA-1. The only good reason to use this
option is to achieve compatibility with ancient PGP products, predating
! the addition of SHA-1 protected packets to RFC 2440.
Recent gnupg.org and pgp.com software supports it fine.
--- 708,714 ----
Do not protect data with SHA-1. The only good reason to use this
option is to achieve compatibility with ancient PGP products, predating
! the addition of SHA-1 protected packets to RFC 4880.
Recent gnupg.org and pgp.com software supports it fine.
***************
*** 1172,1187 ****
!
OpenPGP message format.
-
-
-
- New version of RFC 2440.
-
-
The MD5 Message-Digest Algorithm.
--- 1174,1183 ----
!
OpenPGP message format.
The MD5 Message-Digest Algorithm.