2010-09-21 04:08:53 +08:00
|
|
|
/* contrib/pgcrypto/sha1.h */
|
2001-03-22 12:01:46 +08:00
|
|
|
/* $KAME: sha1.h,v 1.4 2000/02/22 14:01:18 itojun Exp $ */
|
2000-10-31 21:11:28 +08:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
|
|
|
|
|
* All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
|
* are met:
|
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
2001-03-22 12:01:46 +08:00
|
|
|
* notice, this list of conditions and the following disclaimer.
|
2000-10-31 21:11:28 +08:00
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
2001-03-22 12:01:46 +08:00
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
2000-10-31 21:11:28 +08:00
|
|
|
* 3. Neither the name of the project nor the names of its contributors
|
2001-03-22 12:01:46 +08:00
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
|
* without specific prior written permission.
|
2000-10-31 21:11:28 +08:00
|
|
|
*
|
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
2014-05-07 00:12:18 +08:00
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
|
2000-10-31 21:11:28 +08:00
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
|
*/
|
|
|
|
|
/*
|
|
|
|
|
* FIPS pub 180-1: Secure Hash Algorithm (SHA-1)
|
2010-04-02 23:21:20 +08:00
|
|
|
* based on: http://www.itl.nist.gov/fipspubs/fip180-1.htm
|
2000-10-31 21:11:28 +08:00
|
|
|
* implemented by Jun-ichiro itojun Itoh <itojun@itojun.org>
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _NETINET6_SHA1_H_
|
|
|
|
|
#define _NETINET6_SHA1_H_
|
|
|
|
|
|
2001-03-22 12:01:46 +08:00
|
|
|
struct sha1_ctxt
|
|
|
|
|
{
|
|
|
|
|
union
|
|
|
|
|
{
|
2001-01-10 00:07:14 +08:00
|
|
|
uint8 b8[20];
|
|
|
|
|
uint32 b32[5];
|
2001-03-22 12:01:46 +08:00
|
|
|
} h;
|
|
|
|
|
union
|
|
|
|
|
{
|
2001-01-10 00:07:14 +08:00
|
|
|
uint8 b8[8];
|
|
|
|
|
uint64 b64[1];
|
2001-03-22 12:01:46 +08:00
|
|
|
} c;
|
|
|
|
|
union
|
|
|
|
|
{
|
2001-01-10 00:07:14 +08:00
|
|
|
uint8 b8[64];
|
|
|
|
|
uint32 b32[16];
|
2001-03-22 12:01:46 +08:00
|
|
|
} m;
|
|
|
|
|
uint8 count;
|
2000-10-31 21:11:28 +08:00
|
|
|
};
|
|
|
|
|
|
2001-03-22 12:01:46 +08:00
|
|
|
extern void sha1_init(struct sha1_ctxt *);
|
|
|
|
|
extern void sha1_pad(struct sha1_ctxt *);
|
/contrib/pgcrypto:
* remove support for encode() as it is in main tree now
* remove krb5.c
* new 'PX library' architecture
* remove BSD license from my code to let the general
PostgreSQL one to apply
* md5, sha1: ANSIfy, use const where appropriate
* various other formatting and clarity changes
* hmac()
* UN*X-like crypt() - system or internal crypt
* Internal crypt: DES, Extended DES, MD5, Blowfish
crypt-des.c, crypt-md5.c from FreeBSD
crypt-blowfish.c from Solar Designer
* gen_salt() for crypt() - Blowfish, MD5, DES, Extended DES
* encrypt(), decrypt(), encrypt_iv(), decrypt_iv()
* Cipher support in mhash.c, openssl.c
* internal: Blowfish, Rijndael-128 ciphers
* blf.[ch], rijndael.[ch] from OpenBSD
* there will be generated file rijndael-tbl.inc.
Marko Kreen
2001-08-21 08:42:41 +08:00
|
|
|
extern void sha1_loop(struct sha1_ctxt *, const uint8 *, size_t);
|
|
|
|
|
extern void sha1_result(struct sha1_ctxt *, uint8 *);
|
2000-10-31 21:11:28 +08:00
|
|
|
|
2016-03-16 06:06:11 +08:00
|
|
|
/* compatibility with other SHA1 source codes */
|
2000-10-31 21:11:28 +08:00
|
|
|
typedef struct sha1_ctxt SHA1_CTX;
|
2001-03-22 12:01:46 +08:00
|
|
|
|
2000-10-31 21:11:28 +08:00
|
|
|
#define SHA1Init(x) sha1_init((x))
|
2001-03-22 12:01:46 +08:00
|
|
|
#define SHA1Update(x, y, z) sha1_loop((x), (y), (z))
|
2000-10-31 21:11:28 +08:00
|
|
|
#define SHA1Final(x, y) sha1_result((y), (x))
|
|
|
|
|
|
2001-03-22 12:01:46 +08:00
|
|
|
#define SHA1_RESULTLEN (160/8)
|
2001-10-28 14:26:15 +08:00
|
|
|
|
Phase 2 of pgindent updates.
Change pg_bsd_indent to follow upstream rules for placement of comments
to the right of code, and remove pgindent hack that caused comments
following #endif to not obey the general rule.
Commit e3860ffa4dd0dad0dd9eea4be9cc1412373a8c89 wasn't actually using
the published version of pg_bsd_indent, but a hacked-up version that
tried to minimize the amount of movement of comments to the right of
code. The situation of interest is where such a comment has to be
moved to the right of its default placement at column 33 because there's
code there. BSD indent has always moved right in units of tab stops
in such cases --- but in the previous incarnation, indent was working
in 8-space tab stops, while now it knows we use 4-space tabs. So the
net result is that in about half the cases, such comments are placed
one tab stop left of before. This is better all around: it leaves
more room on the line for comment text, and it means that in such
cases the comment uniformly starts at the next 4-space tab stop after
the code, rather than sometimes one and sometimes two tabs after.
Also, ensure that comments following #endif are indented the same
as comments following other preprocessor commands such as #else.
That inconsistency turns out to have been self-inflicted damage
from a poorly-thought-through post-indent "fixup" in pgindent.
This patch is much less interesting than the first round of indent
changes, but also bulkier, so I thought it best to separate the effects.
Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org
Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
2017-06-22 03:18:54 +08:00
|
|
|
#endif /* _NETINET6_SHA1_H_ */
|
