head	1.155;
access;
symbols
	DEVEL-BRANCH-1-1:1.155
	V1-0-0:1.153
	V0-9-11:1.151
	V0-9-10:1.148
	V0-9-9:1.147
	V0-9-8:1.138
	V0-9-7:1.131
	V0-9-6:1.127
	V0-9-5:1.120
	V0-9-4:1.114
	V0-9-3:1.105
	V0-9-2:1.101
	V0-9-1:1.94
	V0-9-0:1.89
	V0-4-5:1.83
	V0-4-4:1.80
	V0-4-3:1.74
	V0-4-2:1.70
	V0-4-1:1.67
	V0-4-0:1.62
	V0-3-5:1.60
	V0-3-4:1.58
	V0-3-3:1.57
	V0-3-2:1.48
	V0-3-1:1.46
	V0-3-0:1.43
	V0-2-19:1.41
	V0-2-18:1.39
	V0-2-17:1.36
	V0-2-15:1.31
	V0-2-10:1.25
	V-0-2-8:1.24
	V0-2-6:1.22
	V0-2-0:1.15
	V0-1-0:1.12
	V0-0-0:1.12;
locks; strict;
comment	@# @;


1.155
date	99.09.17.10.58.14;	author wkoch;	state Exp;
branches;
next	1.154;

1.154
date	99.09.15.15.58.38;	author wkoch;	state Exp;
branches;
next	1.153;

1.153
date	99.09.07.15.12.51;	author wkoch;	state Exp;
branches;
next	1.152;

1.152
date	99.09.06.18.10.08;	author wkoch;	state Exp;
branches;
next	1.151;

1.151
date	99.09.02.14.50.28;	author wkoch;	state Exp;
branches;
next	1.150;

1.150
date	99.08.31.15.30.02;	author wkoch;	state Exp;
branches;
next	1.149;

1.149
date	99.08.30.18.48.45;	author wkoch;	state Exp;
branches;
next	1.148;

1.148
date	99.08.04.08.45.08;	author wkoch;	state Exp;
branches;
next	1.147;

1.147
date	99.07.23.12.02.47;	author wkoch;	state Exp;
branches;
next	1.146;

1.146
date	99.07.22.18.11.48;	author wkoch;	state Exp;
branches;
next	1.145;

1.145
date	99.07.15.08.16.37;	author wkoch;	state Exp;
branches;
next	1.144;

1.144
date	99.07.13.15.41.01;	author wkoch;	state Exp;
branches;
next	1.143;

1.143
date	99.07.12.16.49.09;	author wkoch;	state Exp;
branches;
next	1.142;

1.142
date	99.07.12.12.57.43;	author wkoch;	state Exp;
branches;
next	1.141;

1.141
date	99.07.07.11.27.59;	author wkoch;	state Exp;
branches;
next	1.140;

1.140
date	99.07.01.10.53.23;	author wkoch;	state Exp;
branches;
next	1.139;

1.139
date	99.06.29.19.50.40;	author wkoch;	state Exp;
branches;
next	1.138;

1.138
date	99.06.26.10.22.47;	author wkoch;	state Exp;
branches;
next	1.137;

1.137
date	99.06.10.12.24.34;	author wkoch;	state Exp;
branches;
next	1.136;

1.136
date	99.06.05.13.36.10;	author wkoch;	state Exp;
branches;
next	1.135;

1.135
date	99.06.01.14.08.45;	author wkoch;	state Exp;
branches;
next	1.134;

1.134
date	99.05.31.17.49.22;	author wkoch;	state Exp;
branches;
next	1.133;

1.133
date	99.05.27.07.45.38;	author wkoch;	state Exp;
branches;
next	1.132;

1.132
date	99.05.25.17.56.04;	author wkoch;	state Exp;
branches;
next	1.131;

1.131
date	99.05.23.18.32.26;	author wkoch;	state Exp;
branches;
next	1.130;

1.130
date	99.05.22.20.54.41;	author wkoch;	state Exp;
branches;
next	1.129;

1.129
date	99.05.19.14.12.20;	author wkoch;	state Exp;
branches;
next	1.128;

1.128
date	99.05.08.17.35.08;	author wkoch;	state Exp;
branches;
next	1.127;

1.127
date	99.05.06.12.25.58;	author wkoch;	state Exp;
branches;
next	1.126;

1.126
date	99.04.28.11.06.46;	author wkoch;	state Exp;
branches;
next	1.125;

1.125
date	99.04.26.15.52.50;	author wkoch;	state Exp;
branches;
next	1.124;

1.124
date	99.04.18.18.53.31;	author wkoch;	state Exp;
branches;
next	1.123;

1.123
date	99.04.18.08.18.33;	author wkoch;	state Exp;
branches;
next	1.122;

1.122
date	99.04.09.10.34.33;	author wkoch;	state Exp;
branches;
next	1.121;

1.121
date	99.04.07.18.58.19;	author wkoch;	state Exp;
branches;
next	1.120;

1.120
date	99.03.20.11.56.56;	author wkoch;	state Exp;
branches;
next	1.119;

1.119
date	99.03.20.10.53.32;	author wkoch;	state Exp;
branches;
next	1.118;

1.118
date	99.03.17.12.12.54;	author koch;	state Exp;
branches;
next	1.117;

1.117
date	99.03.14.18.35.13;	author koch;	state Exp;
branches;
next	1.116;

1.116
date	99.03.11.15.41.57;	author koch;	state Exp;
branches;
next	1.115;

1.115
date	99.03.10.10.27.47;	author koch;	state Exp;
branches;
next	1.114;

1.114
date	99.03.08.19.50.02;	author koch;	state Exp;
branches;
next	1.113;

1.113
date	99.03.02.15.48.29;	author koch;	state Exp;
branches;
next	1.112;

1.112
date	99.03.02.09.41.45;	author koch;	state Exp;
branches;
next	1.111;

1.111
date	99.02.28.18.14.15;	author koch;	state Exp;
branches;
next	1.110;

1.110
date	99.02.26.16.59.38;	author koch;	state Exp;
branches;
next	1.109;

1.109
date	99.02.25.17.51.50;	author koch;	state Exp;
branches;
next	1.108;

1.108
date	99.02.24.10.12.20;	author koch;	state Exp;
branches;
next	1.107;

1.107
date	99.02.22.19.08.41;	author koch;	state Exp;
branches;
next	1.106;

1.106
date	99.02.20.20.45.34;	author koch;	state Exp;
branches;
next	1.105;

1.105
date	99.02.19.14.53.47;	author koch;	state Exp;
branches;
next	1.104;

1.104
date	99.02.16.13.16.17;	author koch;	state Exp;
branches;
next	1.103;

1.103
date	99.02.13.11.19.07;	author koch;	state Exp;
branches;
next	1.102;

1.102
date	99.02.10.16.22.17;	author koch;	state Exp;
branches;
next	1.101;

1.101
date	99.01.21.05.25.11;	author koch;	state Exp;
branches;
next	1.100;

1.100
date	99.01.19.18.37.32;	author koch;	state Exp;
branches;
next	1.99;

1.99
date	99.01.16.20.26.05;	author koch;	state Exp;
branches;
next	1.98;

1.98
date	99.01.16.08.29.18;	author koch;	state Exp;
branches;
next	1.97;

1.97
date	99.01.13.11.51.39;	author koch;	state Exp;
branches;
next	1.96;

1.96
date	99.01.12.10.20.11;	author koch;	state Exp;
branches;
next	1.95;

1.95
date	99.01.10.14.13.01;	author koch;	state Exp;
branches;
next	1.94;

1.94
date	99.01.09.15.06.45;	author koch;	state Exp;
branches;
next	1.93;

1.93
date	99.01.07.17.05.33;	author koch;	state Exp;
branches;
next	1.92;

1.92
date	99.01.03.14.33.26;	author koch;	state Exp;
branches;
next	1.91;

1.91
date	98.12.29.18.58.13;	author koch;	state Exp;
branches;
next	1.90;

1.90
date	98.12.29.13.46.55;	author koch;	state Exp;
branches;
next	1.89;

1.89
date	98.12.23.16.16.48;	author koch;	state Exp;
branches;
next	1.88;

1.88
date	98.12.23.12.41.10;	author koch;	state Exp;
branches;
next	1.87;

1.87
date	98.12.17.17.35.49;	author koch;	state Exp;
branches;
next	1.86;

1.86
date	98.12.14.20.22.31;	author koch;	state Exp;
branches;
next	1.85;

1.85
date	98.12.12.17.44.27;	author koch;	state Exp;
branches;
next	1.84;

1.84
date	98.12.10.19.20.25;	author koch;	state Exp;
branches;
next	1.83;

1.83
date	98.12.08.12.20.30;	author koch;	state Exp;
branches;
next	1.82;

1.82
date	98.11.27.11.42.38;	author koch;	state Exp;
branches;
next	1.81;

1.81
date	98.11.25.11.55.48;	author koch;	state Exp;
branches;
next	1.80;

1.80
date	98.11.20.19.22.51;	author koch;	state Exp;
branches;
next	1.79;

1.79
date	98.11.20.17.42.03;	author koch;	state Exp;
branches;
next	1.78;

1.78
date	98.11.18.19.59.00;	author koch;	state Exp;
branches;
next	1.77;

1.77
date	98.11.14.10.21.57;	author koch;	state Exp;
branches;
next	1.76;

1.76
date	98.11.13.19.41.32;	author koch;	state Exp;
branches;
next	1.75;

1.75
date	98.11.10.12.59.41;	author koch;	state Exp;
branches;
next	1.74;

1.74
date	98.11.08.17.23.10;	author koch;	state Exp;
branches;
next	1.73;

1.73
date	98.11.03.19.38.46;	author koch;	state Exp;
branches;
next	1.72;

1.72
date	98.10.25.18.59.49;	author koch;	state Exp;
branches;
next	1.71;

1.71
date	98.10.21.17.34.23;	author koch;	state Exp;
branches;
next	1.70;

1.70
date	98.10.18.15.21.10;	author koch;	state Exp;
branches;
next	1.69;

1.69
date	98.10.16.15.59.56;	author wk;	state Exp;
branches;
next	1.68;

1.68
date	98.10.12.20.16.19;	author wk;	state Exp;
branches;
next	1.67;

1.67
date	98.10.07.13.30.36;	author wk;	state Exp;
branches;
next	1.66;

1.66
date	98.10.06.12.09.47;	author wk;	state Exp;
branches;
next	1.65;

1.65
date	98.10.01.07.22.48;	author wk;	state Exp;
branches;
next	1.64;

1.64
date	98.09.29.16.15.12;	author wk;	state Exp;
branches;
next	1.63;

1.63
date	98.09.28.19.25.11;	author wk;	state Exp;
branches;
next	1.62;

1.62
date	98.09.18.15.24.38;	author wk;	state Exp;
branches;
next	1.61;

1.61
date	98.09.15.19.56.21;	author wk;	state Exp;
branches;
next	1.60;

1.60
date	98.09.14.15.49.37;	author wk;	state Exp;
branches;
next	1.59;

1.59
date	98.09.11.05.47.15;	author wk;	state Exp;
branches;
next	1.58;

1.58
date	98.08.11.17.29.15;	author wk;	state Exp;
branches;
next	1.57;

1.57
date	98.08.08.21.13.58;	author wk;	state Exp;
branches;
next	1.56;

1.56
date	98.08.08.19.26.43;	author wk;	state Exp;
branches;
next	1.55;

1.55
date	98.08.07.08.53.30;	author wk;	state Exp;
branches;
next	1.54;

1.54
date	98.08.05.16.51.46;	author wk;	state Exp;
branches;
next	1.53;

1.53
date	98.07.30.17.36.58;	author wk;	state Exp;
branches;
next	1.52;

1.52
date	98.07.29.19.34.38;	author wk;	state Exp;
branches;
next	1.51;

1.51
date	98.07.21.12.53.27;	author wk;	state Exp;
branches;
next	1.50;

1.50
date	98.07.15.18.04.59;	author wk;	state Exp;
branches;
next	1.49;

1.49
date	98.07.14.17.10.11;	author wk;	state Exp;
branches;
next	1.48;

1.48
date	98.07.09.13.37.04;	author wk;	state Exp;
branches;
next	1.47;

1.47
date	98.07.08.09.29.36;	author wk;	state Exp;
branches;
next	1.46;

1.46
date	98.07.06.10.23.43;	author wk;	state Exp;
branches;
next	1.45;

1.45
date	98.07.02.19.31.35;	author wk;	state Exp;
branches;
next	1.44;

1.44
date	98.06.29.12.30.41;	author wk;	state Exp;
branches;
next	1.43;

1.43
date	98.06.25.10.18.52;	author wk;	state Exp;
branches;
next	1.42;

1.42
date	98.06.09.15.13.53;	author wk;	state Exp;
branches;
next	1.41;

1.41
date	98.05.29.11.53.40;	author wk;	state Exp;
branches;
next	1.40;

1.40
date	98.05.26.13.37.44;	author wk;	state Exp;
branches;
next	1.39;

1.39
date	98.05.15.18.49.04;	author wk;	state Exp;
branches;
next	1.38;

1.38
date	98.05.13.17.53.19;	author wk;	state Exp;
branches;
next	1.37;

1.37
date	98.05.05.20.34.13;	author wk;	state Exp;
branches;
next	1.36;

1.36
date	98.05.04.18.49.11;	author wk;	state Exp;
branches;
next	1.35;

1.35
date	98.05.03.19.35.30;	author wk;	state Exp;
branches;
next	1.34;

1.34
date	98.05.03.15.42.04;	author wk;	state Exp;
branches;
next	1.33;

1.33
date	98.04.25.08.08.27;	author wk;	state Exp;
branches;
next	1.32;

1.32
date	98.04.20.14.47.17;	author wk;	state Exp;
branches;
next	1.31;

1.31
date	98.04.09.11.19.00;	author wk;	state Exp;
branches;
next	1.30;

1.30
date	98.04.08.19.48.45;	author wk;	state Exp;
branches;
next	1.29;

1.29
date	98.04.07.18.15.56;	author wk;	state Exp;
branches;
next	1.28;

1.28
date	98.04.02.10.29.49;	author wk;	state Exp;
branches;
next	1.27;

1.27
date	98.03.19.15.27.14;	author wk;	state Exp;
branches;
next	1.26;

1.26
date	98.03.09.21.43.46;	author wk;	state Exp;
branches;
next	1.25;

1.25
date	98.02.26.16.56.12;	author wk;	state Exp;
branches;
next	1.24;

1.24
date	98.02.24.18.50.02;	author wk;	state Exp;
branches;
next	1.23;

1.23
date	98.02.16.20.04.37;	author wk;	state Exp;
branches;
next	1.22;

1.22
date	98.02.13.20.58.36;	author wk;	state Exp;
branches;
next	1.21;

1.21
date	98.02.11.23.21.57;	author wk;	state Exp;
branches;
next	1.20;

1.20
date	98.02.11.03.25.31;	author wk;	state Exp;
branches;
next	1.19;

1.19
date	98.02.04.18.54.23;	author wk;	state Exp;
branches;
next	1.18;

1.18
date	98.02.02.14.35.57;	author wk;	state Exp;
branches;
next	1.17;

1.17
date	98.01.28.16.09.30;	author wk;	state Exp;
branches;
next	1.16;

1.16
date	98.01.26.22.08.48;	author wk;	state Exp;
branches;
next	1.15;

1.15
date	98.01.25.18.56.25;	author wk;	state Exp;
branches;
next	1.14;

1.14
date	98.01.12.10.17.58;	author wk;	state Exp;
branches;
next	1.13;

1.13
date	98.01.07.20.47.36;	author wk;	state Exp;
branches;
next	1.12;

1.12
date	98.01.02.20.39.59;	author wk;	state Exp;
branches;
next	1.11;

1.11
date	97.12.31.12.32.45;	author wk;	state Exp;
branches;
next	1.10;

1.10
date	97.12.20.17.23.22;	author wk;	state Exp;
branches;
next	1.9;

1.9
date	97.12.16.19.14.54;	author wk;	state Exp;
branches;
next	1.8;

1.8
date	97.12.12.12.03.41;	author wk;	state Exp;
branches;
next	1.7;

1.7
date	97.12.09.12.46.12;	author wk;	state Exp;
branches;
next	1.6;

1.6
date	97.12.02.19.36.47;	author wk;	state Exp;
branches;
next	1.5;

1.5
date	97.12.01.10.33.05;	author wk;	state Exp;
branches;
next	1.4;

1.4
date	97.11.27.11.44.02;	author wk;	state Exp;
branches;
next	1.3;

1.3
date	97.11.24.11.03.56;	author wk;	state Exp;
branches;
next	1.2;

1.2
date	97.11.23.15.38.22;	author wk;	state Exp;
branches;
next	1.1;

1.1
date	97.11.21.14.53.50;	author wk;	state Exp;
branches;
next	;


desc
@@


1.155
log
@See ChangeLog: Fri Sep 17 12:56:42 CEST 1999  Werner Koch
@
text
@
  * try to do --verify even if the files are swapped on the commandline
    (requested by Herny Spencer) or change the error message to
    a more clear one.

Scheduled for 1.1
-----------------
  * With option -i prompt before adding a key to the keyring and show some
    info what we are about to add.

  * Speed up calculation of key validation.

  * Allow a replacement for the progress functions in ./cipher

  * print a warning when a revoked/expired _secret_ key is used.

  * --disable-asm should still assemble _udiv_qrnnd when needed

  * Skip RO keyrings when importing a key.

  * Use the newest encryption key if only the main key has been given.

  * replace the keyserver stuff either by a call to a specialized
    utility and SOCKSify this utility.

  * Check the beginning of file to detect already compressed files (gzip,
    bzip2, xdelta and some picture formats)

  * Delay the read of the passphrase-fd afte a NEED_PASSPHRASE.  But this
    may break some scripts.


Nice to have
------------
  * Official test vectors for 3DES-EDE3
  * use DEL and ^H for erasing the previous character (util/ttyio.c).
    or better readline.
  * Print a warning if the directory mode is wrong.
  * Do a real fix for bug #7 or document that it is a PGP 5 error.
  * preferences of hash algorithms are not yet used.
  * Replace the SIGUSR1 stuff by semaphores to avoid loss of a signal.
    or use POSIX.4 realtime signals.  Overhaul the interface and the
    test program.  Use it with the test suite?
  * add test cases for invalid data (scrambled armor or other random data)
  * add checking of armor trailers
  * Burn the buffers used by fopen(), or use read(2). Does this
    really make sense?	And while we are at it:  implement a secure deletion
    stuff?
  * the pubkey encrypt functions should do some sanity checks.
  * dynload: implement the hint stuff.
  * "gpg filename.tar.gz.asc" should work like --verify (-sab).
  * for messages created with "-t", it might make sense to append the
    verification status of the message to the output (i.e. write something to
    the --output file and not only to stderr.
  * configure option where to find zlib
  * Display more validity information about the user IDs at certain places.
    We need a more general function to extract such kind of info from the
    trustdb.
  * Evaluate whether it make sense to replace the namehashs either by
    using the user ID directly or by using pointers into the trustdb.
  * --gen-prime may trigger a log_bug; should be a log_fatal.

@


1.154
log
@See ChangeLog: Wed Sep 15 17:57:13 CEST 1999  Werner Koch
@
text
@d3 2
a4 1
    (requested by Herny Spencer)
d28 3
@


1.153
log
@See ChangeLog: Tue Sep  7 17:08:10 CEST 1999  Werner Koch
@
text
@d2 3
@


1.152
log
@See ChangeLog: Mon Sep  6 19:59:08 CEST 1999  Werner Koch
@
text
@a1 4
    Gael has added a LF to helptext.c:185  check other translations.
    (03.09.99)


@


1.151
log
@See ChangeLog: Thu Sep  2 16:40:55 CEST 1999  Werner Koch
@
text
@d2 4
@


1.150
log
@See ChangeLog: Tue Aug 31 17:20:44 CEST 1999  Werner Koch
@
text
@a10 3
  * add an option to use an OpenPGP packet as input (and don't build a literal
    data packet)

d17 8
a31 2
  * replace the keyserver stuff either by a call to a specialized
    utility and SOCKSify this utility.
a48 2
  * Check the beginning of file to detect already compressed files (gzip,
    bzip2, xdelta and some picture formats)
@


1.149
log
@See ChangeLog: Mon Aug 30 20:38:33 CEST 1999  Werner Koch
@
text
@a1 9
  * use-emmbeded-filename ist nicht dokumentiert.

  * --disable-asm should still assemble _udiv_qrnnd when needed

  * Skip RO keyrings when importing a key.

  * help the translaters to catch changes made to helptext.c
    and tell that, that they have to translate those strings.

d16 4
d23 1
a23 1
  * Offcial test vectors for 3DES-EDE3
d46 1
a46 1
  * Check the beginning of file to detect already compresssed files (gzip,
@


1.148
log
@See ChangeLog: Wed Aug  4 10:34:46 CEST 1999  Werner Koch
@
text
@d2 8
@


1.147
log
@See ChangeLog: Fri Jul 23 13:53:03 CEST 1999  Werner Koch
@
text
@d50 1
a50 1

@


1.146
log
@See ChangeLog: Thu Jul 22 20:03:03 CEST 1999  Werner Koch
@
text
@a1 3
  * Check that uids without a self signature don't become fully trusted and
    print a warning when such a key is used.

d43 8
@


1.145
log
@See ChangeLog: Thu Jul 15 10:15:35 CEST 1999  Werner Koch
@
text
@d2 8
a9 2
  * add some status output put for signing and encryption.
    replace the putc in primegen with some kind of status-fd outputs.
d13 1
a13 1
  * print a warning when a revoked/expired _secret_ key is used.
d15 2
a16 1
  * Add NO_PUBKEY and NO_SECKEY status lines.
d18 1
a18 5
  * Solaris make has problems with the generated POTFILES - seems to be a
    gettext bug.

  * find a way to allow the import of non-self-signed keys.  This is needed
    for the IN ENCR/SIGN hack.
a19 2
  * add an option to use a OpenPGP packet as input (and don't build a literal
    data packet)
@


1.144
log
@See ChangeLog: Tue Jul 13 17:39:25 CEST 1999  Werner Koch
@
text
@d5 1
a5 1
  * Speed up calculation of key validity.
@


1.143
log
@See ChangeLog: Mon Jul 12 18:45:57 CEST 1999  Werner Koch
@
text
@d17 2
@


1.142
log
@See ChangeLog: Mon Jul 12 14:55:34 CEST 1999  Werner Koch
@
text
@d42 1
@


1.141
log
@See ChangeLog: Wed Jul  7 13:23:40 CEST 1999  Werner Koch
@
text
@a8 5
  * remove more "Fixmes"

  * when decryptiong multiple key: print a warning only if no usable pubkey
    encrypt package was found.	Extension: display a list of all recipients.

a16 2
  * Not all user names are correctly converted to UTF8.

a19 1
  * Let take --help an option to select some topics.
d38 1
a38 1
  * "gpg filename.tar.gz.asc" sollte wie mit --verify funktionieren (-sab).
@


1.140
log
@See ChangeLog: Thu Jul  1 12:47:31 CEST 1999  Werner Koch
@
text
@a35 1
  * new menu to delete signatures and list signature in menu
a43 1
  * Stats about used random numbers.
@


1.139
log
@See ChangeLog: Tue Jun 29 21:44:25 CEST 1999  Werner Koch
@
text
@a1 2
  * add keylength and type to status output.

d22 1
a22 1
  * convert the given user ID to UTF-8 and add an option to suppress this.
a51 1

@


1.138
log
@See ChangeLog: Sat Jun 26 12:15:59 CEST 1999  Werner Koch
@
text
@a8 3
  * See why we always get this "Hmmm, public key not anymore available"
    Rewrite that stuff.

a12 3
  * Use capabilities if available.  glibc2 does not support it yet?
    What about 2.2 or should we use the system calls directly?

a24 2

  * A way to disable keys.
@


1.137
log
@See ChangeLog: Thu Jun 10 14:18:23 CEST 1999  Werner Koch
@
text
@d32 2
@


1.136
log
@See ChangeLog: Sat Jun  5 15:30:33 CEST 1999  Werner Koch
@
text
@d32 1
@


1.135
log
@See ChangeLog: Tue Jun  1 16:01:46 CEST 1999  Werner Koch
@
text
@d30 2
@


1.134
log
@See ChangeLog: Mon May 31 19:41:10 CEST 1999  Werner Koch
@
text
@a39 1
  * clearsig: Keep lineendings while writing the output of a clearsig
a53 2
  * Den Dateinamen aus der message nicht benutzen, sondern nur
    das gpg/asc strippen.
@


1.133
log
@See ChangeLog: Thu May 27 09:40:55 CEST 1999  Werner Koch
@
text
@d2 2
@


1.132
log
@See ChangeLog: Tue May 25 19:50:32 CEST 1999  Werner Koch
@
text
@a1 6
  * gppm links in doc und bin sind inkonsistent

  * remove signature:
Got an idea:  just specify the keyid of the signature - this can be
done quite easily.

@


1.131
log
@See ChangeLog: Sun May 23 20:25:57 CEST 1999  Werner Koch
@
text
@d2 6
@


1.130
log
@See ChangeLog: Sat May 22 22:47:26 CEST 1999  Werner Koch
@
text
@a1 2
  * Don't access the trustdb if always-trust is active.

@


1.129
log
@See ChangeLog: Wed May 19 16:04:30 CEST 1999  Werner Koch
@
text
@d2 2
d38 1
a38 1
    utility or SOCKSify the stuff.
d57 4
@


1.128
log
@See ChangeLog: Sat May  8 19:28:33 CEST 1999  Werner Koch
@
text
@d8 1
a24 2
  * cvs -d :pserver:anoncvs@@anoncvs.gnu.org:/gd/gnu/anoncvsroot co common

d52 3
@


1.127
log
@See ChangeLog: Thu May  6 14:18:17 CEST 1999  Werner Koch
@
text
@d31 1
d34 1
d48 2
a49 2
    really make sense?
  * change the fake_data stuff to mpi_set_opaque
@


1.126
log
@See ChangeLog: Wed Apr 28 13:03:03 CEST 1999  Werner Koch
@
text
@a4 2
  * Fix revocation and expire stuff.  Subkey revocations are not detected.

a19 1
  * Add more NODATA status lines
@


1.125
log
@See ChangeLog: Mon Apr 26 17:48:15 CEST 1999  Werner Koch
@
text
@d5 1
a5 1
  * Fix revocation and expire stuff.
d7 1
a7 1
  * Check calculation of key validity.
@


1.124
log
@See ChangeLog: Sun Apr 18 20:48:15 CEST 1999  Werner Koch
@
text
@d11 1
a11 1
  * print a warning when a revoked/expired secret key is used.
@


1.123
log
@See ChangeLog: Sun Apr 18 10:11:28 CEST 1999  Werner Koch
@
text
@d29 2
a30 1

@


1.122
log
@See ChangeLog: Fri Apr  9 12:26:25 CEST 1999  Werner Koch
@
text
@d9 1
a9 1
  * See why we always get this "Hmmm public key lost" - Is it fixed?
d27 2
d33 1
d51 2
@


1.121
log
@See ChangeLog: Wed Apr  7 20:51:39 CEST 1999  Werner Koch
@
text
@d24 1
a24 1
  * Solaris make as problems with the generated POTFILES - seems to be a
a26 4
  * Need suffix rules for .S to produce .s for some systems

  * do a chmod as soon as the secring is created.  Print a warning if
    the directory mode is wrong.
d32 1
@


1.120
log
@See ChangeLog: Sat Mar 20 12:55:33 CET 1999  Werner Koch
@
text
@a4 2
  * Implement 256 bit key Twofish.

d27 5
d35 1
@


1.119
log
@See ChangeLog: Sat Mar 20 11:53:40 CET 1999  Werner Koch
@
text
@a4 2
  * Finish the EGD module.

d7 1
a7 1
  * Check revocation and expire stuff.
d11 1
a11 1
  * See why we always get this "Hmmm public key lost"
@


1.118
log
@See ChangeLog: Wed Mar 17 13:09:03 CET 1999  Werner Koch
@
text
@d28 2
a29 2
  * gpg --keyserver wwwkeys.us.pgp.net --importserver 0x12345678
    (or --importserver warner@@lothar.com, etc)
d34 2
@


1.117
log
@See ChangeLog: Sun Mar 14 19:34:36 CET 1999  Werner Koch
@
text
@a1 3
  * Replace --trusted-keys by a local certificate (which does not get
    exported).

d3 1
a3 1
    replace the puc in primegen with some kind of status-fd outputs.
d7 1
a7 1
  * Implement 256 bit key Twofish (wait until the 2nd AES conference).
d9 1
a9 1
  * Check revocation and expire stuff.	[I'm currently working on this.]
d11 1
a11 1
  * Check calculation of key validity. [I'm currently working on this.]
d25 2
a26 10
* an ERRSIG argument like
  ERRSIG <keyid>, where <keyid> is the id of the missing public key
    or a new keyword
  PUBLIC_MISSING <keyid>
* a status line complaining about a missing secret key like
  SECRET_MISSING <keyid>, where <keyid> is the id of the missing secret key
* a status line complaining about a bad passphrase like
  BADPASS


d28 2
@


1.116
log
@See ChangeLog: Thu Mar 11 16:39:46 CET 1999  Werner Koch
@
text
@d5 3
d27 12
@


1.115
log
@See ChangeLog: Wed Mar 10 11:26:18 CET 1999  Werner Koch
@
text
@d2 3
d7 1
a7 1
  * Implement 256 bit key Twofish.
a24 1
  * describe the Lim-Lee algorithms
d33 2
a34 1
    or use POSIX.4 realtime signals.
@


1.114
log
@See ChangeLog: Mon Mar  8 20:47:17 CET 1999  Werner Koch
@
text
@d22 1
@


1.113
log
@See ChangeLog: Tue Mar  2 16:44:57 CET 1999  Werner Koch
@
text
@d2 2
d25 1
@


1.112
log
@See ChangeLog: Tue Mar  2 10:38:42 CET 1999  Werner Koch
@
text
@a3 3
  * clearsig: keep lineendings as they are. Remember that trailings
    blanks are not hashed.

d23 1
@


1.111
log
@See ChangeLog: Sun Feb 28 19:11:00 CET 1999  Werner Koch
@
text
@a22 1
  * Can't import ring1.pgp. Compressed keys? Should print a warning.
a34 2
  * How about letting something like 'gpg --version -v', list the
    effective options. [Too much work.]
@


1.110
log
@See ChangeLog: Fri Feb 26 17:55:41 CET 1999  Werner Koch
@
text
@d23 1
@


1.109
log
@See ChangeLog: Thu Feb 25 18:47:39 CET 1999  Werner Koch
@
text
@d21 1
a21 11
    encrypte package was found.  Extension: display a list of all recipients.

  * in pkclist.c : display info about the key before saying that
    we have (no) trust info.

  * for new key: the last keyring specified is used.  Order is: default
    keyrings, keyrings from options, keyrings from the command line.

  * display a kind of message-id from a signature (the timestamp may not
    be suffiecient but DSA signatures are always different).  This can
    be used to prevent replay attacks.	(something is mentioned in rfc2440).
@


1.108
log
@See ChangeLog: Wed Feb 24 11:07:27 CET 1999  Werner Koch
@
text
@d20 1
a20 1
  * wehndecryptiong multiple key: print a warning only if no usable pubkey
d23 9
@


1.107
log
@See ChangeLog: Mon Feb 22 20:04:00 CET 1999  Werner Koch
@
text
@d20 4
@


1.106
log
@See ChangeLog: Sat Feb 20 21:40:49 CET 1999  Werner Koch
@
text
@a0 7
Bugs
----
    * clearsig: keep lineendings as they are. Remember that trailings
      blanks are not hashed.  Funny: pgp263in works fine even with
      a source file with CR,LF but GnuPG and pgp263in has problems
      if the clearsign has been created by pgp263ia.
      Needs more investigation - anyone?
d2 1
a2 1
    * replace my type 20 subkeys by type 16 ones.
d4 2
a5 3
Important
----------
    * Check revocation and expire stuff.  [I'm currently working on this.]
d7 1
a7 1
    * Check calculation of key validity. [I'm currently working on this.]
d9 1
a9 1
    * See why we always get this "Hmmm public key lost"
d11 1
a11 1
    * print a warning when a revoked/expired secret key is used.
d13 1
a13 3
Needed
------
    * remove more "Fixmes"
d15 1
a15 1
    * Implement 256 bit key Twofish.
d17 2
a18 2
    * Use capabilities if available.  glibc2 does not support it yet?
      What about 2.2 or should we use the system calls directly?
a19 5
Minor Bugs
----------

    * --list-packets should continue even w/o a passphrase (or in batch
      mode).
d23 12
a34 13
    * preferences of hash algorithms are not yet used.
    * new menu to delete signatures and list signature in menu
    * Replace the SIGUSR1 stuff by semaphores to avoid loss of a signal.
      or use POSIX.4 realtime signals.
    * add test cases for invalid data (scrambled armor or other random data)
    * add checking of armor trailers
    * Burn the buffers used by fopen(), or use read(2). Does this
      really make sense?
    * change the fake_data stuff to mpi_set_opaque
    * How about letting something like 'gpg --version -v', list the
      effective options. [Too much work.]
    * Stats about used random numbers.

@


1.105
log
@See ChangeLog: Fri Feb 19 15:49:15 CET 1999  Werner Koch
@
text
@d9 2
@


1.104
log
@See ChangeLog: Tue Feb 16 14:10:02 CET 1999  Werner Koch
@
text
@a8 5
    * clearsign bug Greg Troxel Jan 11.

    * README does not verify okay. verify inserts an extra CR,LF
      just before "Esoteric Command" (after ~8k of text).

d11 1
a11 1
    * Check revocation and expire stuff.  PLEASE: THIS MUST BE TESTED!
d13 1
a13 2
    * Check calculation of key validity. PLEASE: IT IS IMPORTED THAT
      THIS GET TESTED.
d25 2
a26 2
    * Use capabilities if available.

a30 5
    * There is a race condition which leaves lock files after process
      termination (a signal while in make_dotlock).  Change the dotlock
      implementaion to a create handle, make and release implemenation
      and use an atexit to cleanup all pending locks.  This is also
      faster.
d46 1
a46 1
      effective options. Too much work.
@


1.103
log
@See ChangeLog: Sat Feb 13 12:14:42 CET 1999  Werner Koch
@
text
@a13 2
    * Did I add -lsocket and -lnls for Solaris?

a15 2
    * replace gettext by a non exploitable one.

a26 3
    * encrypttoself, damit keine Angabe von -r immer noch zu einer
      abfrage fhrt.

d29 1
a29 10
    * Replace Blowfish by Twofish and add the new encrypted packet type
      which has a MACing option (append SHA1 hash to the plaintext and
      encrypt this all) - We need an identifier for Twofish to put this
      one into the cipher preferences.

    * The -export-dynamic flag to ld works only for FreeBSD 3.0.  It does
      not exist on FreeBSD's 2.2.x version of ld.
      Also, on my FreeBSD 2.2-stable box, i simply removed the
      -Wl,-export-dynamic flag from my Makefile and it linked and seems to
      be working OK so far.
d42 2
@


1.102
log
@See ChangeLog: Wed Feb 10 17:15:39 CET 1999  Werner Koch
@
text
@d14 2
d31 3
@


1.101
log
@See ChangeLog: Thu Jan 21 06:22:10 CET 1999  Werner Koch
@
text
@d11 3
d16 2
d42 2
d66 1
a66 1
      effective options.
@


1.100
log
@See ChangeLog: Tue Jan 19 19:34:58 CET 1999  Werner Koch
@
text
@a21 10
> 0.9.1: I get some occasional segfaults during 'make check' unless I use
> --with-included-zlib. It's strange, I have zlib-1.1.2 on one machine, and
> zlib-1.1.3 on another, and both of them fail on occasion (maybe half of the
[ I hope this is fixed ]

> gpg: /home/jam/.gnupg/pubring.gpg: can't open gdbm file: Can't be writer
> gpg: keyblock resource `/home/jam/.gnupg/pubring.gpg': file open error
> gpg: OOPS in close enum_keyblocks - ignored


@


1.99
log
@See ChangeLog: Sat Jan 16 21:25:17 CET 1999  Werner Koch
@
text
@d25 1
a30 5
    > Indeed, comparing zero to 0xfe returns 2, not -something, and this is
> the problem.	This seems to fix it, but I don't know how you want to
> handle this.
>
  I'll better write a autoconf test as memcmp is used all over the place.
a45 2

    * text_filter.c: use iobuf_readline for cleartext signatures.
@


1.98
log
@See ChangeLog: Sat Jan 16 09:27:30 CET 1999  Werner Koch
@
text
@d30 5
a34 1

d76 2
@


1.97
log
@See ChangeLog: Wed Jan 13 12:49:36 CET 1999  Werner Koch
@
text
@d47 3
@


1.96
log
@See ChangeLog: Tue Jan 12 11:17:18 CET 1999  Werner Koch
@
text
@d68 1
a68 1
      effective options. Yep.
@


1.95
log
@See ChangeLog: Sun Jan 10 15:10:02 CET 1999  Werner Koch
@
text
@d9 2
a17 5
    * It has been reported that lockfiles are not removed in all cases.
      cleanup is done with atexit() and all signals trigger exit() -
      anything wrong with this?  - ah yes: a signal while still in
      dotlock_make

a21 3
    * Allow the use of a the faked RNG only for keys which are
      flagged as INSECURE.

d26 5
d36 1
a36 1
    * Replace Blowfish by Twofish and add the new encrypted packet typ
d50 6
d67 2
a68 1

@


1.94
log
@See ChangeLog: Sat Jan  9 16:02:23 CET 1999  Werner Koch
@
text
@d28 4
@


1.93
log
@See ChangeLog: Thu Jan  7 18:00:58 CET 1999  Werner Koch
@
text
@d25 1
a25 1
    * Allow the use of a the faked RNG onyl for keys which are
a57 1
    * rewrite the ugly armor code.
@


1.92
log
@See ChangeLog: Sun Jan  3 15:28:44 CET 1999  Werner Koch
@
text
@d25 2
a26 2
    * display trhe primary keyID in passphrase.c in addition to the
      one for the requested key.
d38 6
d59 1
@


1.91
log
@See ChangeLog: Tue Dec 29 19:55:38 CET 1998  Werner Koch
@
text
@d23 5
a27 1
    * print a warning when a revoked/expired secret is used.
@


1.90
log
@See ChangeLog: Tue Dec 29 14:41:47 CET 1998  Werner Koch
@
text
@d23 2
@


1.89
log
@See ChangeLog: Wed Dec 23 17:12:24 CET 1998  Werner Koch
@
text
@d18 2
a19 1
      anything wrong with this?
d21 1
a21 3
    * I noticed, that we sometimes have only 3 items in a trustrecord, but
      a next pointer ro more records - check wehther the reuse code really
      works. Maybe this is the reason for the "Hmmm public key lost"
d46 1
@


1.88
log
@See ChangeLog: Wed Dec 23 13:34:22 CET 1998  Werner Koch
@
text
@d33 3
a46 4

Minor Bugs
----------
    * md_start_debug used to crash at pgm termination.
@


1.87
log
@See ChangeLog: Thu Dec 17 18:31:15 CET 1998  Werner Koch
@
text
@d1 7
d9 2
a12 2
    * Escape "From "

d16 3
a18 1
    * preferences of hash algorithms are not yet used.
d24 8
a31 11
    * clearsig: keep lineendings as they are. Remember that trailings
      blanks are not hashed.

    * should we flush the getkey.c caches while doing an import?

    * We need a maintainence pass over the trustdb which flags
      signatures as expired if the key used to make the signature has
      expired.	Maybe it is a good idea to store the exiration time
      in the key record of the trustdb.

    * write a tool to extract selected keys from a file.
d33 3
a36 1

a38 1

d40 1
a40 3

    * rewrite --list-packets or put it into another tool.

a42 6

    * Change the buffering to a mbuf like scheme? Need it for PSST anyway;
      see Michael's proposal.
    * add checking of armor trailers
    * remove all "Fixmes" ;-)

d45 3
a47 3
    * Replace Blowfish by Twofish

    * Work on the library
@


1.86
log
@See ChangeLog: Mon Dec 14 21:18:49 CET 1998  Werner Koch
@
text
@d4 2
@


1.85
log
@See ChangeLog: Sat Dec 12 18:40:32 CET 1998  Werner Koch
@
text
@a8 2
    * Check Berkeley BD - it is in glibc - any licensing problems?

a17 3
    * The critical bit of signature subpackets is not yet supported; i.e.
      it is ignored.

a41 4
    * add an option to re-create a public key from a secret key; we
      can do this in trustdb.c:verify_own_keys.
      (special tool?)

d44 1
a44 1
    * Use "user ID", "trustdb", "NOTE" and "WARNING".
d46 1
a46 1
    * Replace Blowfish by Twofish
@


1.84
log
@See ChangeLog: Thu Dec 10 20:15:36 CET 1998  Werner Koch
@
text
@d2 1
a2 1
    * Check revocation and expire stuff.
d4 2
a5 1
    * Check calculation of key validity.
a17 3
    * OpenBSD: dynamic loading with dlopen works on OpenBSD, but:
      OpenBSD binaries are a.out, so every symbol begins with "_"

d33 1
a52 2
    * Add some stuff for DU cc

a55 4

    * Print a warning when a experimental algorithm is used.

    * Remove ElGamal signatures.
@


1.83
log
@See ChangeLog: Tue Dec  8 13:15:16 CET 1998  Werner Koch
@
text
@a13 9
    * use zlib 1.1.13 to avoid a bug with 13 bit windows
      but there are more problems with large files

    * FreeBSD:
	#define USE_DYNAMIC_LINKING
	#define HAVE_DL_DLOPEN
	and the ld option -export-dynamic.
      Why does autoconf not figure that out?

d18 1
a18 1
	OpenBSD binaries are a.out, so every symbol begins with "_"
a33 2
    * -rdynamic auf Solaris Problem

d57 6
@


1.82
log
@See ChangeLog: Fri Nov 27 12:39:29 CET 1998  Werner Koch
@
text
@d8 1
a8 1
    * Check Berkeley BD - it is in glibc -any licensing problems?
a24 4

    * Always use the latest key signature (import).  This is needed, so
      that we are able to chnage the expiration time or other info in the
      selfsignature
@


1.81
log
@Some experimental support for other random gatheres
@
text
@a7 3
    * Hash calculation for cleartext sigs without a "Hash: xxx" line
      does it work as specified in the RFC? - Hmmm, I think so

a13 2
    * check support for mpi/powerpc (see Brian's mail)

a52 3
    * add some sanity checks to read_keyblock, so that we are sure that
     the minimal requirements are met (?)

d65 1
a67 2

    * Is it okay to use gettext for the help system?
@


1.80
log
@Ready for version 0.4.4
@
text
@a16 2
    * Update the keyring at ftp.guug.de

@


1.79
log
@Expiration time works (I hope so)
@
text
@d2 7
a8 1
    * hash calculation for cleartext sigs without a "Hash: xxx" line
d19 1
a19 3
    * expire date is not shown in --edit-key for subkeys.

    * check support for mpi/powerpc
a32 2
    * Check revocation and expire stuff.

a53 2
    * commandline controlled --edit-key with assumed save.

a61 2

    * preferences of hash algorithms are not yet used.
@


1.78
log
@some bug fixes
@
text
@d7 1
a7 1
    * I noticed, that we sometimes have only 3 items in atrustrecord, but
d9 1
a9 1
      works. Maybe this is the reason for the "Hmmm puiblic key lost"
a16 3
    * add a note, that gettext 10.35 is needed (for gettext) - and install
      it on tobold.

d24 1
d31 4
a62 2
    * decryption of message with multiple recipients does not work.

d70 2
a71 1
    * Change the buffering to a mbuf like scheme? Need it for PSST anyway.
d73 1
a73 5
    * remove all "Fixmes"

    * Change the internal represention of keyid into a struct which
      can also hold the localid and extend the localid to hold information
      of the subkey number because two subkeys may have the same keyid.
a77 9
    * signature verification is done duplicated on import: in import.c and
      tehn in trustdb.c too.  Maybe we can use a flag to skip the actual
      verification process (this should work if we use the same keyblock,
      but I'm not sure how to accomplish that).  Another way is to allow
      the import of bogus data and let trustdb mark these keys as invalid;
      I see an advantage in this that it may help to prevent a DoS on a
      keyserver by sending him a lot of bogus signatures which he has
      to check - Needs further investigation.

d84 1
a84 1
    * Use "user ID", "trustdb" and "WARNING".
@


1.77
log
@Spanish laguage support (es_ES)
@
text
@d3 1
a3 1
      does it work as specified in the RFC?
a13 1
      and prefs are not correctly listed for some keys???? (Brian)
d15 1
a15 1
    * support for mpi/powerpc  split is still combined or whatever
a31 2

    * check preferences (cipher and compress)
@


1.76
log
@See ChangeLog ;-).  Key validation should now be faster
@
text
@d2 5
d11 1
a11 1
    * Update the keyring at ftp.ggug.de
@


1.75
log
@Some bug fixes of the last release
@
text
@d2 8
a9 1
    * Update the keyring on ftp.ggug.de
a93 1
    * use "passphrase" instead of "pass phrase"
@


1.74
log
@ready to release 0.4.3
@
text
@d2 7
d10 1
a16 8
    *
     Well, there was one thing extra I needed to do.  While configure found the
     gdbm library, it didn't add the path the the include file list.  I had to
     re-run configure with CPPFLAGS set:

     env CPPFLAGS='-I/usr/local/include' configure ...


d20 1
a20 1
    * Fix ;) revocation and expire stuff.
a27 3

    * prefer a type 16 subkey for encryption because pgp cannot handle
      type 20?
@


1.73
log
@(Does not compile yet)
@
text
@a1 4
    * rmove assert in random.c:160 4096 bit keys need more random.

    * list all matching user ids

d5 3
a7 4
#define USE_DYNAMIC_LINKING
#define HAVE_DL_DLOPEN

and the ld option -export-dynamic.
d10 3
a12 3
Well, there was one thing extra I needed to do.  While configure found the
gdbm library, it didn't add the path the the include file list.  I had to
re-run configure with CPPFLAGS set:
d14 1
a14 1
    env CPPFLAGS='-I/usr/local/include' configure ...
@


1.72
log
@some random changes
@
text
@d2 23
a36 2
    * calculation of marginals never yields a completely trusted key.

a39 2
    * Exportable Certification Flag is ignored

d79 9
@


1.71
log
@Epxerimenta support for GDBM keyings.
@
text
@d4 2
@


1.70
log
@Snapshot release 0.4.2
@
text
@a1 2
    * There is a new memory leak in update-trustdb :-(

@


1.69
log
@last local commit
@
text
@a0 18
    * change ringedit:
	- avoid all copy operations
	- delete for update by changing the packet type to a
	  special unused packet. (export most know about this)
	- do an append instead of an update or insert
	- export may be used to compress a keyring.
	- keep track of all offset in the trustbd and index them
	  by keyid.
	- If the lookup does not find a public key block at the
	  stored offset disable this keyid.
	- If the keyid was not found or is disabled, walk thru
	  the pubring.
	- use ftruncate to recover from keyring errors.
	   maybe a new option to do this or simply mark the
	   wrong part as unused.
      This makes signature checks and imports much faster; only keys
      given by a userid or a fingerprint (RSA only) have to walk tru
      the ring.
d2 3
a4 1
    * There is a new memory leak in update-trustdb
a8 2
    * use dld if we don't have dlopen.

d12 1
a12 1
      type 20.
d21 5
a59 2

    * OpenBSD has sometimes problems reading from /dev/random.
@


1.68
log
@backup
@
text
@d1 23
d25 1
a25 1
    * calculation of marginals never yields a completely trusted key.
d27 1
a27 1
    * list-keys:  change valid-days to key expiration date
d29 2
a30 1
    * disable comments but those in secret keyrings.
d32 1
a32 5
    * abgelaufene secret keys verhinder ein korrektes initialisieren der
      Trustdb.

    * import should skip all ascii armored messages headers which are
      not keys (some folks are mailing signed public keyblocks :-)
a36 2
    * Read more records at once in tdbio.c and provide a lazy write cache.

a38 7
    * Why does OpenPGP say: The algorithm byte is included in the
      checksum of an encoded key, but the actual implementaion does
      not do this but works - According to Hal Finney, this is a bug
      in the specs.

    * fix armor problems (see mails by Brian Moore).

a46 4
    * if --libdir is used, the extensions are put in a wrong place.
      How does GNOME handle this or make a new option for this directory.
      Hmmm, I don like to pass ot as a commandline option to cc.

d71 2
a72 2
    * add an option to re-create a public key from a secret key. Think about
      a backup system of only the secret part of the secret key.
@


1.67
log
@a new release
@
text
@d2 12
@


1.66
log
@windoze version works again
@
text
@a1 5
    * check for working mmap()

    * after creating a new uid, the preferences in the trustdb are not updated.
      We should always sync the trustdb in such cases.

d5 2
d59 1
a59 1
    * Is it okay to use gettext for the help system???
@


1.65
log
@*** empty log message ***
@
text
@d2 2
@


1.64
log
@*** empty log message ***
@
text
@d12 4
a15 1
      not do this but works??
@


1.63
log
@*** empty log message ***
@
text
@d5 9
@


1.62
log
@.
@
text
@d2 11
d15 1
a15 5

    * Should we use the ElGamal subkey if the DSA keyid is given?
      What about an option --loose-keyid-match?

    * salted and iterated S2Ks don't work (see passphrase.c).
a51 2
    * check for "expect" before running test genkey1024

a53 3

    * armor.c cannot handle concatenated armored messages.
      at least it should be possible to do this for "KEY BLOCK"
@


1.61
log
@.
@
text
@a1 2
    * localize asctime()

a13 2
    * fix the expire stuff for v4 packets.

d51 1
@


1.60
log
@New release
@
text
@d2 5
@


1.59
log
@*** empty log message ***
@
text
@d2 2
a3 7
    * cleanup for SHM einbauen (non-linux)

    * shared memory access funktioniert nicht wenn seuid installiert.

    * ElGamal key benutzen wenn die DSA keyid angegeben ist??

    * Apply Paul D. Smith's sugestions for building in another direcory.
a12 3
    * Fix Oscaris problems with the trustdb.
    * invalid packets (Marco)  und Markus Gruber

a15 2
    * what about the CR,LF in cleartext singatures?

a40 4

    * configure checks two times for gcc

    * update gettext
@


1.58
log
@bug fix release
@
text
@d2 8
a17 5
    * check whether it is valid to pack the signature stuff (onepass, data,
      sig) into a compressed packet - or should we only compress the data?
      what does pgp 5 do, what does OpenPGP say=
      ==> I think it is okay, should be tested against pgp5

a45 2
    * replace getkey.c#enum_secret_keys

d57 7
@


1.57
log
@rel 0.3.3
@
text
@a28 3
    * add usage arguments to get_key_byname or return a PKC_LIST with
      all keys and add a selection.

d51 5
a55 1
    * There are still problems with old v3 keys after passphrase change.
@


1.56
log
@ready for a new release
@
text
@d54 2
@


1.55
log
@chnages done at the train
@
text
@d1 2
a2 1
    * Fix Oscaris problems with the trustdb.
d15 1
d52 1
@


1.54
log
@intermediate check in
@
text
@d12 1
@


1.53
log
@started with shm coprocesses
@
text
@d3 2
d13 1
a13 1
    * invalid packets (Marco)
d16 1
a16 1
    the minimal requirements are met (?)
d20 3
a22 1
    * make preferences work
a31 2
    * enable a SIGSEGV handler while using zlib functions

d44 5
@


1.52
log
@edit-key is now complete
@
text
@a0 4
    * Change the internal represenation of keyid into a struct which
      can also hold the localid and extend the localid to hold information
      of the subkey number because two subkeys may have the same keyid.

a17 4
    * add option --import-ownertrust

    * add a way to delete subkeys (in edit-keys?)

a24 2
    * add readline support. Must enhance libreadline - Anyone?

d33 4
@


1.51
log
@changed trustdb design
@
text
@d5 10
d22 1
a22 3
    * add option --restore-ownertrust

    * always put key signatures before the first subkey.
a42 2

    * add an option to create a new user id.
@


1.50
log
@sync
@
text
@a35 6
    * bug: g10/trustdb.c#build_sigrecs called to often by do_list_path
      and remove the bad kludge. Maybe we should put all sigs into the trustdb
      and mark them as valid/invalid/nopubkey, and how do we check, that
      we have a self-signature -> put this stuff into a kind of directory
      record, as it does not belong to the pubkey record?

@


1.49
log
@sync
@
text
@d7 3
@


1.48
log
@fixed severe exploit
@
text
@d1 3
d5 1
d7 1
a7 4
    * clearsig of zero length files does not work

    * Change the inernal represenation of keyid into a struct which
      can also hold the localid
a12 3
    * Change the formatting of log_xxxx to GNU standards
      ("name:filename:line: text")

a18 2
    * add field to PKT_user_id to hold the hash context

a26 1

d29 1
a29 5
    * improve iobuf by reading more than one byte at once,
      this shoud espceially done for the buffer in the chain.
      Change the buffering to a mbuf like scheme? Need it for PSST anyway.
    * add a way to distinguish between errors and eof in the underflow/flush
      function of iobuf.
a43 4
    * add fingerprint/keyid hashing. We need a new field in PKC to
      flag that we may have a cached signature for this (and use the address
      of PKC to lookup the hash).

a44 1

@


1.47
log
@fixed clearsig stuff
@
text
@d2 6
@


1.46
log
@intermediate release
@
text
@d4 1
a4 1
    * add options: --default-signature-user, --default-encryption-user
@


1.45
log
@partly added creation of OP partial length headers
@
text
@d2 1
a2 2
    * add writing of partial headers conforming to OpenPGP
      util/iobuf.c:block_filter
d6 5
d22 3
a24 1
    * Burn the buffers used by fopen(), or use read(2).
@


1.44
log
@textual changes
@
text
@d2 3
@


1.43
log
@nearly ready for 0.3.0
@
text
@d2 2
a40 3

    * change the misleading usage of "public key certificate" to
      "public key data" or something like this.
@


1.42
log
@Sicherung
@
text
@d2 4
a10 3
    * add expiration date and other stuff from v4 sigs to the trust
      checking.

a24 1

a31 5
      Make it possible to change the signature class of the self-signatures,
      which can then be used to change the displayed order of user-ids:
      Put the user-id with a self-signature of class 0x13 always on top
      of the displayed list (needs changes in the user-id-from-keyid
      functions).
@


1.41
log
@*** empty log message ***
@
text
@d2 2
a36 5

    * enhance --sign-key, so that multiple-user-ids can be signed
      (use the new classes 0x14..17), partly implemented, but I think we
      should better make use of notation data - for now we allow only one
      user id.
@


1.40
log
@add-key works
@
text
@d5 3
@


1.39
log
@new release
@
text
@d2 2
a3 1
    * make --add-key work (to add an ElGamal key to a DSA key).
@


1.38
log
@can create v4 signatures
@
text
@d2 8
a17 5
    * enable a SIGSEGV handler while using zlib functions

    * key generation for dsa and subpacket support.

    * Burn the buffers used by fopen(), or use read(2).
d44 2
a45 5
    * change the misleading usage of public key certificate to public key data
      or something like this.

    * fix the problems with "\v" in gettext.  Add nice formatting stuff to
      argparse.c
a48 1
    * add readline support (Must enhance libreadline)
@


1.37
log
@add DSA key generation
@
text
@d23 2
a24 2
      Make it possible to chnage the signature class of the self-signatures,
      which can then be used to chnage the displayed order of user-ids:
d30 3
a32 3
      (use the new classes 0x14..17)

    * support these multi-user-id-sigs in trustdb.
d44 2
a45 1
    * fix the problems with "\v" in gettext
d49 1
a49 3
    * add readline support (but how can we allcoate it in secure memory?)

    * add a testcase for --print-mds
@


1.36
log
@new release
@
text
@d50 2
@


1.35
log
@fixed last passphrase bug
@
text
@a49 2
    * add multi-user-id-sigs handling to import.c

@


1.34
log
@Aenderungen in der Eifel
@
text
@a51 2
    * add tag 3 packet support to "-c"

@


1.33
log
@changes from laptop
@
text
@d52 2
@


1.32
log
@vor muenchen
@
text
@d22 11
a32 10
    * add an option to create a new user id and to reorder the sequence of
      them, so that the preferred emal address comes first.  We need to
      add some logic, which guarantees, that only one user-id can be signed by
      others.  This prevents extensive growing of the public key certificate
      due to the bad usage of signing every user id.  You get no extra
      security by key signatures for every user id.  I consider this
      behaviour of PGP a bug, introduced, becaus PGP does't require a
      self-signature. New user ids will only have your self signature to bind
      them to your key and because the user id which is signed by others has
      also be signed by you, all user-ids are bound together.
d48 3
a50 1
    * add readline support.
@


1.31
log
@new release
@
text
@d47 2
@


1.30
log
@test release
@
text
@a11 2
    * complete cipher/cast.c -- have to use the PGP CFBug

d33 2
a34 5
    * add an option to re-create a public key from a secret key

    * cleanup mainproc.c, much stuff is duplicated.

    * remove key management stuff from sign.c.
a42 2
    * seckey_cert.c: merge all the check funtions into one.

a45 2


@


1.29
log
@cipher reorganisiert
@
text
@d52 1
a52 6
    * calculation of cechksums for secret keys is wrong. We used a
      the complete chunk length instead of the real number of bits.
      The problme ist that it is how to stay compatible to old
      keys? - Do wee need a kludge to calculate both versions of
      checksums???? (keygen.c, seckey-cert.c)

@


1.28
log
@release 0.2.14
@
text
@d52 9
@


1.27
log
@some cleanups
@
text
@d5 1
a5 1
    * add a way to difference between errors and eof in the underflow/flush
d41 1
a41 1
    * add fingerprint/keyid hashing. We need a new filed in PKC to
d44 7
@


1.26
log
@partial DSA support
@
text
@d9 1
a9 2
    * speed up the RIPE-MD-160
    * add signal handling
d12 3
a14 2
    * complete cipher/cast.c
    * complete cipher/dsa.c
a36 2
    * should we have a simple menu for all the key management options?

d40 4
@


1.25
log
@release 0.2.9
@
text
@d16 1
a16 3
    * add g10 stuff to Mutt's pgpinvoke.c

    * Burn the buffers used by fopen().
d35 7
@


1.24
log
@Renamed to GNUPG
@
text
@d4 1
@


1.23
log
@some import functionality
@
text
@a35 2
    * create directory .g10

@


1.22
log
@added option export
@
text
@a6 1
    * look for a way to reuse RSA signatures
d35 2
@


1.21
log
@bug fixes
@
text
@d26 11
@


1.20
log
@a couple of changes; but some parts are now broken
@
text
@a1 1
    * add assembler support for more CPUs. (work, but easy)
a5 1
    * check that all output is filtered when displayed.
@


1.19
log
@armor rewritten, but still buggy
@
text
@a17 2
    * armor has now some problems.

a26 3

    * Have no prototype for stpcpy() when using glibc 2; must switch on
      the GNU extensions or see how configure can fix it.
@


1.18
log
@changed structure of trustdb
@
text
@d30 4
@


1.17
log
@ version 0.2.1
@
text
@a14 8
    * PGP writes the signature and then the file, this is not
      a good idea, we can't write such files if we take input from stdin.
      So the solution will: accept such packet, but write
      signature the corret way: first the data and then the signature[s]
      this is much easier to check, also we must read the entire data
      before we can check wether we have the pubkey or not.  The one-pass
      signature packets should be implemented to avoid this.

@


1.16
log
@added initial i18n stuff
@
text
@a7 1
    * add trust stuff
a8 1
    * add real secure memory
@


1.15
log
@Ready to test version 0.2.0
@
text
@a27 8
    * define a standard way to specify keyid/userid and other stuff
      to identify a user.  We could look at the first character and
      say: If it's a digit, a keyid follows (need to add a zero in
      case the keyid starts with A..F); if it is a left angle bracket,
      this is a email address and should be used, all others are substrings
      of the userid.
      [can be handles in get_pubkey_by_name()]

d34 1
a34 1
    * bug: g10/trustdb.c#build_sigrecs caled to often by do_list_path
@


1.14
log
@started with trust stuff
@
text
@d42 5
@


1.13
log
@patchlevel 2
@
text
@d40 2
@


1.12
log
@added more stuff
@
text
@d38 3
@


1.11
log
@Sylvester Version
@
text
@a24 1
    * compress does not work always!
d35 2
@


1.10
log
@very first release
@
text
@a8 2
    * make ttyio.c work (hide passwords etc..)
    * use correct ASN values for DEK encoding
@


1.9
log
@added some stuff for signing keys
@
text
@a7 1
    * keyring editing
@


1.8
log
@added option file handling
@
text
@a10 1
    * add option file handling.
a14 3
    * find a way to remove the armor filter after it
      has detected, that the data is not armored.
    * Use the Chinese Remainder Theorem to speed up RSA calculations.
d31 8
@


1.7
log
@fingerprints and self signatures added
@
text
@d33 2
@


1.6
log
@Sicherung
@
text
@d7 1
a7 1
    * filter all output read from the input when displaying it to the user.
a10 1
    * add detached signatures
a13 1
    * fix the memory stuff (secure memory)
d25 1
a25 1
      a good idea, we can't write such files if we take input rom stdin.
d31 2
@


1.5
log
@List and check sigs works
@
text
@a8 1
    * remove some debugging stuff (e.g. the listing mode in mainproc)
d25 8
@


1.4
log
@Improved prime number test
@
text
@a8 1
    * improve the prime number generator
d21 1
a21 1
    * Use the Chines Remainder Theorem to speed up RSA calculations.
@


1.3
log
@IDEA removed, signing works
@
text
@d2 1
a2 1
    * write the assembler function for mpihelp ....
a19 1
    * add ElGamal and make it the default one.
a23 1
    * add credits for the MPI lib.
@


1.2
log
@compress stuff implemented
@
text
@a7 1
    * remove idea.
d13 1
a13 2
    * add signal handling
    * add writing of signatures and checking of detached signatures.
d21 1
a21 1
    * find a way to remove the arnor filter after it
d27 1
@


1.1
log
@Armor works now
@
text
@a17 1
    * add compress handling
d29 1
@
