/
nerfur
/
openbsd-src
ОбзорДокументацияВойти
/
nerfur
/
openbsd-src
Код
Запросы
0
Задачи
Вики
Пакеты
0
Релизы
0
Аналитика
Безопасность
ДокументацияПоддержка
Политика конфиденциальностиПользовательское соглашениеПолитика использования «cookies»Согласие субъекта персональных данных
2026 ©
openbsd-src/
lib/libkeynote/
..
Misc

Update for version 2.0

27 лет назад
testsuite

Simplify a couple of things in the lexer, make the compiler happy so -Wall doesn't complain at the lexers.

27 лет назад
HOWTO.add.crypto

Sync with current version (just the file renamed).

27 лет назад
LICENSE

with or without fee; received mail permitting this change from angelos

25 лет назад
Makefile

repair the tree, make sure y.tab.h is there before compiling yacc files.

9 лет назад
README

Sync.

26 лет назад
assertion.h

remove prototypes with no matching function

2 года назад
auxil.c

libkeynote: fix build with opaque RSA and DSA

5 лет назад
base64.c

remove duplicate rcs id

2 года назад
environment.c

remove a few NULL-checks before free()

11 лет назад
header.h

Move sessid definition to keynote-verify.c to avoid issues with -fno-common

6 лет назад
keynote-keygen.c

libkeynote: use DSA_generate_parameters_ex()

3 года назад
keynote-main.c

Make crufty configure stuff go away. Remove all unused code paths. No change in binaries.

22 года назад
keynote-sign.c

For open/openat, if the flags parameter does not contain O_CREAT, the 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert

5 лет назад
keynote-sigver.c

For open/openat, if the flags parameter does not contain O_CREAT, the 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert

5 лет назад
keynote-ver.l

Add %option noinput to suppress an unused function warning. Noticed by and OK ottot@

9 лет назад
keynote-ver.y

Header cleanup. ok hshoexer@

22 года назад
keynote-verify.c

For open/openat, if the flags parameter does not contain O_CREAT, the 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert

5 лет назад
keynote.1

prefer https links in man pages ok gnezdo@ miod@ jmc@

4 года назад
keynote.3

.Lb libkeynote libm libcrypto ; OK tedu@

год назад
keynote.4

.Lb libkeynote libm libcrypto ; OK tedu@

год назад
keynote.5

prefer https links in man pages ok gnezdo@ miod@ jmc@

4 года назад
keynote.h

make keynote.h C++ safe ok todd@

22 года назад
keynote.l

Add %option noinput to suppress an unused function warning. Noticed by and OK ottot@

9 лет назад
keynote.y

spelling fixes; from paul tagliamonte any changes not taken noted on tech, but chiefly here i did not take the cancelation - cancellation changes;

4 года назад
parse_assertion.c

spelling fixes; from paul tagliamonte any changes not taken noted on tech, but chiefly here i did not take the cancelation - cancellation changes;

4 года назад
sample-app.c

Header cleanup. ok hshoexer@

22 года назад
signature.c

Passing preallocated keys to d2i_RSAPublicKey() does not work anymore with LibreSSL. This caused a crash in isakmpd with libkeynote. Better pass NULL and let libcrypto do the allocation. from markus@; OK tb@

4 года назад
signature.h

with or without fee; received mail permitting this change from angelos

25 лет назад
README
# $OpenBSD: README,v 1.10 2000/09/26 23:28:45 angelos Exp $
 
This is release 2.3 of the KeyNote trust management library reference
implementation (in case you are wondering, there was never an official 1.0
release).
 
For details on the KeyNote spec, read RFC 2704, included in this distribution
(in the doc/ directory).
 
To build the distribution, just type "./configure" and then "make" or
"make crypt". To test the distribution, type "make test". The query should
evaluate to "true" (look at the last line of output). To build without
crypto support, use "make nocrypto" instead (you still need to run
"configure"). If you have built crypto support, "make test-sig" will run
some more tests on the cryptographic algorithms.
 
A sample application is provided in sample-app.c. To build it, use
"make test-sample".
 
Compile tips:
- You need the SSLeay/OpenSSL library if you compile with crypto
(default), version 0.8.1b or later. OpenSSL can be found at:
http://www.openssl.org/
 
The Makefile creates the libkeynote.a library and the keynote program.
*** Notice that the 4 programs of previous releases have been folded into one
 
There is a man page for the library calls (keynote.3) and one for the command
line tool (keynote.1), in the man/ directory. There is also a man page
about KeyNote itself (keynote.4) and one about assertion syntax
(keynote.5) which contain some text from the spec.
 
To view them, use:
 
nroff -mandoc keynote.1 | more
nroff -mandoc keynote.3 | more
nroff -mandoc keynote.4 | more
nroff -mandoc keynote.5 | more
 
Alternatively, you can just install them in your manpath. If your
nroff does not support the -mandoc flag, use -man instead. For those
systems that do not have nroff, the text version of the man pages are
provided as well (the files with .cat? suffixes in the same directory).
 
The "keynote verify" function can be used to verify a request, given a
set of assertions and an environment file. The directory testsuite/
has some examples assertions. The "keynote keygen" function can
be used to generate keys. The "keynote sign" and "keynote sigver" can be
used to sign assertions, and verify signed assertions respectively.
 
The file base64.c was taken from the OpenBSD libc and was slightly
modified.
 
Read the TODO file to see what's missing (and eventually coming).
 
When in doubt on how to use a library call (despite the man pages),
consult the implementation of the various utilities.
 
For any questions, comments, bug reports, praise, or anything else,
contact us at keynote@research.att.com
 
There is also a users mailing list at keynote-users@nsa.research.att.com
To subscribe, send a message to majordomo@nsa.research.att.com with the word
"subscribe keynote-users" (without the quotes) in the message body.
 
Finally, there is a web page for KeyNote at
http://www.cis.upenn.edu/~keynote
 
Angelos D. Keromytis