pgpenvelope-users Mailing List for pgpenvelope (Page 4)

Brought to you by: ftobin

pgpenvelope-users — general pgpenvelope users discussion

You can subscribe to this list here.

2000	_Jan (1)	_Feb (22)	_Mar (11)	_Apr (9)	_May (1)	_Jun (9)	_Jul (28)	_Aug (9)	_Sep (10)	_Oct (26)	_Nov	_Dec
2001	_Jan (8)	_Feb (2)	_Mar	_Apr (2)	_May (6)	_Jun	_Jul (4)	_Aug (8)	_Sep (9)	_Oct	_Nov (2)	_Dec (8)
2002	_Jan (1)	_Feb	_Mar (1)	_Apr	_May	_Jun	_Jul (1)	_Aug	_Sep (3)	_Oct	_Nov	_Dec
2003	_Jan	_Feb	_Mar	_Apr	_May	_Jun (2)	_Jul (2)	_Aug (2)	_Sep	_Oct	_Nov	_Dec

Flat | Threaded

<< < 1 2 3 4 5 6 .. 8 > >> (Page 4 of 8)

patch for autodetecting the signing key

From: Friedhelm B. <bue...@ma...> - 2000-10-03 18:43:01

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


-----BEGIN PGP SIGNATURE-----
Comment: Das Briefgeheimnis sowie das Post- und
Comment: Fernmeldegeheimnis sind unverletzlich.
Comment: Grundgesetz, Artikel 10, Abs 1.

iD8DBQE52icrexQgz1uRM98RAuj9AKC5qZMCGhtdVSWTkS06i5PBPvw+OgCgn5G+
A3dJIZHcTEsGtWsKczhQZIA=
=4Qo2
-----END PGP SIGNATURE-----

Re: [PATCH] anti-forgery

From: Frank T. <ft...@ui...> - 2000-10-03 18:19:01

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Billy Donahue, at 07:14 -0400 on Tue, 3 Oct 2000, wrote:

> Well, it did mangle my patch...  Here's an unmangled^Wunsigned version.

Actually, could you post it to the Patch Manger for pgpenvelope on SF?  I
can handle it cleanly there.

https://sourceforge.net/patch/?group_id=1628

> By the way, I forgot to mention that to detect forged pgpenvelope borders,
> the .procmailrc recipe has to run on EVERY message, not just those which
> match /^-----PGP BEGIN/.  I took the 'a' option out of the second
> recipe in the pgpenvelope `manpage' so that this would be done.
> I wish procmail's egrep could do the approximate match required for
> forgery detection, but it can't.

Right, good idea.

- -- 
Frank Tobin		http://www.uiuc.edu/~ftobin/



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (FreeBSD)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjnaIwUACgkQVv/RCiYMT6Ns6wCdH8iM3xOpoXp91XwkN/1JZC2R
1PsAni+P93/KOsTh+Oxze3ax/qEhged3
=vns2
-----END PGP SIGNATURE-----

forgery patch tests(fwd)

From: Billy D. <bi...@da...> - 2000-10-03 11:36:25

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Here's a test message after passing through the forgery filter.
My actual pgpenvelope borders are set to be:

> ---===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
> ---===[END PGPENVELOPE INFORMATION]===---
> ---===[BEGIN PGPENVELOPE INFORMATION]===---
(but without the '> ', of course).

Let's see which of these test strings is close
enough to set off the bullshit alarm...


 ---===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
> ---===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
> > ---===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
WARNING:---===[BEGIN PGPENVELOP PROCESSED MESSAGE]===---
WARNING:---===[BEGIN PGPENVELOP PROCESED MESSAGE]===---
- ---===[BEGIN PGPENVELOP PROCESED MASSAGE]===---
- ---===[begin pgpenvelope procesed massage]===---
- ---==[begin pgpenvelope procesed massage]==---
 --===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===--
WARNING:--===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===--
WARNING:---===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
WARNING:=--===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
 --===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
  -===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---
   ===[BEGIN PGPENVELOPE PROCESSED MESSAGE]===---

WARNING:---===[BEGIN PGPENVELOPE INFORMATION]===---
.--===[BEGIN PGPENVELOPE INFORMATION]===---
 --===[BEGIN PGPENVELOPE INFORMATION]===---
 ---===[BEGIN PGPENVELOPE INFORMATION]===---

WARNING:---===[END PGPENVELOPE INFORMATION]===---
 --===[END PGPENVELOPE INFORMATION]===---
.--===[END PGPENVELOPE INFORMATION]===---
 ---===[END PGPENVELOPE INFORMATION]===---


A `WARNING:' was prepended to all lines which were close enough to cause
an approximate string match at column 0 with a pgpenvelope border.

- --
"The Funk, the whole Funk, and nothing but the Funk."
Linux barcode software mirror: http://dadadada.net/cuecat
Billy Donahue <mailto:bi...@da...>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iD8DBQE52cS1+2VvpwIZdF0RArSwAJwMoI54WSUV5Iv0N3Kk3F2JQSN1uACdFCwO
oKqKCGiXbsxHXTHN8rrXf+8=
=JEvA
-----END PGP SIGNATURE-----

Re: [PATCH] anti-forgery

From: Billy D. <bi...@da...> - 2000-10-03 11:14:44

On Tue, 3 Oct 2000, Billy Donahue wrote:

> Here's a patch to do forgery checks.  They are enabled by default.
> You'll need to get String::Approx from CPAN for this to work.
> I've been testing it out and it's working really well.
> I hope GPG doesn't mangle my patch..

Well, it did mangle my patch...  Here's an unmangled^Wunsigned version.
By the way, I forgot to mention that to detect forged pgpenvelope borders,
the .procmailrc recipe has to run on EVERY message, not just those which
match /^-----PGP BEGIN/.  I took the 'a' option out of the second
recipe in the pgpenvelope `manpage' so that this would be done.
I wish procmail's egrep could do the approximate match required for
forgery detection, but it can't.


diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/Makefile.PL pgpenvelope/Makefile.PL
--- pgpenvelope.orig/Makefile.PL	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/Makefile.PL	Tue Oct  3 06:30:53 2000
@@ -14,6 +14,7 @@
 		       'Term::ReadLine::Gnu' => 1.01,
 		       'GnuPG::Interface'    => 0.10,
 		       'Class::MethodMaker'  => 0.96,
+		       'String::Approx'      => 3.13,
 		      };

 print
diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/lib/PGPEnvelope/Config.pm pgpenvelope/lib/PGPEnvelope/Config.pm
--- pgpenvelope.orig/lib/PGPEnvelope/Config.pm	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/lib/PGPEnvelope/Config.pm	Tue Oct  3 06:21:56 2000
@@ -171,6 +171,16 @@
        'signing-key'
        => PGPEnvelope::Config::Definition->new
        ( ARGCOUNT => 1 ),
+
+       'forgery-warning'
+       => PGPEnvelope::Config::Definition->new
+       ( ARGCOUNT => 1,
+         DEFAULT => '[WARNING:not from pgpenvelope]',
+       ),
+
+       'do-forgery-check'
+       => PGPEnvelope::Config::Definition->new
+       ( DEFAULT => 1 ),

       );

@@ -321,6 +331,17 @@
 #top-border          = $defs{'top-border'}->{DEFAULT}
 #info-top-border     = $defs{'info-top-border'}->{DEFAULT}
 #info-bottom-Border  = $defs{'info-bottom-border'}->{DEFAULT}
+
+# An attacker could try to send you a forged message that looks as
+# though it had been passed through pgpenvelope_decrypt
+# and been verified.
+# If pgpenvelope_decrypt detects an input line matching any of your
+# pgpenvelope message borders, it will prepend a warning message
+# to those lines to warn you of a possible forgery unless you disable
+# the forgery-warning option by setting do-forgery-check to 0.
+
+#forgery-warning = $defs{'forgery-warning'}->{DEFAULT}
+#do-forgery-check = $defs{'do-forgery-check'}->{DEFAULT}

 # This specifies if you only want to see the first uid and
 # subkey information for keys to encrypt to when encrypting
diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/pgpenvelope pgpenvelope/pgpenvelope
--- pgpenvelope.orig/pgpenvelope	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/pgpenvelope	Tue Oct  3 06:51:35 2000
@@ -121,7 +121,7 @@
     * ^-----BEGIN PGP
     pgpenvelope-backup

-    :0 abfw
+    :0 bfw
     | (path_to)/pgpenvelope_decrypt --filter


diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/pgpenvelope_decrypt pgpenvelope/pgpenvelope_decrypt
--- pgpenvelope.orig/pgpenvelope_decrypt	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/pgpenvelope_decrypt	Tue Oct  3 06:22:46 2000
@@ -32,6 +32,8 @@
 use IO::File;
 use IO::Seekable;
 use FindBin;
+use String::Approx qw( aindex );
+
 use sigtrap 'handler' => 'die_signal_handler', 'normal-signals';

 use GnuPG::Interface 0.10;
@@ -96,8 +98,14 @@
 $gnupg->options->meta_interactive( not $is_filter );
 $gnupg->gnupg_call( $program_call );

+my $do_forgery_check = $config->get('do-forgery-check');
+
 PGP_MESSAGE: while ( <STDIN> )
 {
+    if($do_forgery_check and &detect_forged_borders($_)){
+        $_ = $config->get('forgery-warning').$_;
+    }
+
     unless ( /^-----BEGIN PGP / )
     {
 	print STDOUT $_;
@@ -301,4 +309,30 @@
     {
 	print $fh $zeros;
     }
+}
+
+#
+#  Detect forged pgpenvelope borders.
+#
+# Check a line of data.
+# Perform an approximate match against the pgpenvelope border messages.
+# If the match is not flush against the left side, then there is no
+# cause for alarm, and a 0 is returned
+#
+# return 1 if any lines were within a 10% margin. (User should be warned).
+#            This means that up to 9 characters in 10 correctly matched
+#            his border string without any edits.
+# return 0 if everything is okay.
+#
+sub detect_forged_borders
+{
+        my ($line) = @_;
+        my @bordernames = qw( top-border info-top-border info-bottom-border);
+        my @borders = map { $config->get($_) } @bordernames;
+
+        for my $b (@borders) {
+                return 1 if aindex($b, $line) == 0;
+        }
+        return 0;
 }
+

--
"The Funk, the whole Funk, and nothing but the Funk."
Linux barcode software mirror: http://dadadada.net/cuecat
Billy Donahue <mailto:bi...@da...>

[PATCH] anti-forgery

From: Billy D. <bi...@da...> - 2000-10-03 10:57:24

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Here's a patch to do forgery checks.  They are enabled by default.
You'll need to get String::Approx from CPAN for this to work.
I've been testing it out and it's working really well.
I hope GPG doesn't mangle my patch..


diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/Makefile.PL pgpenvelope/Makefile.PL
- --- pgpenvelope.orig/Makefile.PL	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/Makefile.PL	Tue Oct  3 06:30:53 2000
@@ -14,6 +14,7 @@
 		       'Term::ReadLine::Gnu' => 1.01,
 		       'GnuPG::Interface'    => 0.10,
 		       'Class::MethodMaker'  => 0.96,
+		       'String::Approx'      => 3.13,
 		      };
 
 print
diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/lib/PGPEnvelope/Config.pm pgpenvelope/lib/PGPEnvelope/Config.pm
- --- pgpenvelope.orig/lib/PGPEnvelope/Config.pm	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/lib/PGPEnvelope/Config.pm	Tue Oct  3 06:21:56 2000
@@ -171,6 +171,16 @@
        'signing-key'
        => PGPEnvelope::Config::Definition->new
        ( ARGCOUNT => 1 ),
+
+       'forgery-warning'
+       => PGPEnvelope::Config::Definition->new
+       ( ARGCOUNT => 1,
+         DEFAULT => '[WARNING:not from pgpenvelope]',
+       ),
+
+       'do-forgery-check'
+       => PGPEnvelope::Config::Definition->new
+       ( DEFAULT => 1 ),
        
       );
     
@@ -321,6 +331,17 @@
 #top-border          = $defs{'top-border'}->{DEFAULT}
 #info-top-border     = $defs{'info-top-border'}->{DEFAULT}
 #info-bottom-Border  = $defs{'info-bottom-border'}->{DEFAULT}
+
+# An attacker could try to send you a forged message that looks as
+# though it had been passed through pgpenvelope_decrypt
+# and been verified.
+# If pgpenvelope_decrypt detects an input line matching any of your
+# pgpenvelope message borders, it will prepend a warning message
+# to those lines to warn you of a possible forgery unless you disable 
+# the forgery-warning option by setting do-forgery-check to 0.
+
+#forgery-warning = $defs{'forgery-warning'}->{DEFAULT}
+#do-forgery-check = $defs{'do-forgery-check'}->{DEFAULT}
 
 # This specifies if you only want to see the first uid and
 # subkey information for keys to encrypt to when encrypting
diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/pgpenvelope pgpenvelope/pgpenvelope
- --- pgpenvelope.orig/pgpenvelope	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/pgpenvelope	Tue Oct  3 06:51:35 2000
@@ -121,7 +121,7 @@
     * ^-----BEGIN PGP
     pgpenvelope-backup
      
- -    :0 abfw
+    :0 bfw
     | (path_to)/pgpenvelope_decrypt --filter
 
 
diff --exclude Makefile --exclude blib --exclude CVS -ru pgpenvelope.orig/pgpenvelope_decrypt pgpenvelope/pgpenvelope_decrypt
- --- pgpenvelope.orig/pgpenvelope_decrypt	Tue Oct  3 06:32:54 2000
+++ pgpenvelope/pgpenvelope_decrypt	Tue Oct  3 06:22:46 2000
@@ -32,6 +32,8 @@
 use IO::File;
 use IO::Seekable;
 use FindBin;
+use String::Approx qw( aindex );
+
 use sigtrap 'handler' => 'die_signal_handler', 'normal-signals';
 
 use GnuPG::Interface 0.10;
@@ -96,8 +98,14 @@
 $gnupg->options->meta_interactive( not $is_filter );
 $gnupg->gnupg_call( $program_call );
 
+my $do_forgery_check = $config->get('do-forgery-check');
+
 PGP_MESSAGE: while ( <STDIN> )
 {
+    if($do_forgery_check and &detect_forged_borders($_)){
+        $_ = $config->get('forgery-warning').$_;
+    }
+
     unless ( /^-----BEGIN PGP / )
     {
 	print STDOUT $_;
@@ -301,4 +309,30 @@
     {
 	print $fh $zeros;
     }
+} 
+
+#
+#  Detect forged pgpenvelope borders.
+#
+# Check a line of data.
+# Perform an approximate match against the pgpenvelope border messages.
+# If the match is not flush against the left side, then there is no
+# cause for alarm, and a 0 is returned
+#
+# return 1 if any lines were within a 10% margin. (User should be warned).
+#            This means that up to 9 characters in 10 correctly matched
+#            his border string without any edits.
+# return 0 if everything is okay.
+#
+sub detect_forged_borders
+{
+        my ($line) = @_;
+        my @bordernames = qw( top-border info-top-border info-bottom-border);
+        my @borders = map { $config->get($_) } @bordernames;
+
+        for my $b (@borders) {
+                return 1 if aindex($b, $line) == 0;
+        }
+        return 0;
 }
+

- --
"The Funk, the whole Funk, and nothing but the Funk."
Linux barcode software mirror: http://dadadada.net/cuecat
Billy Donahue <mailto:bi...@da...>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iD8DBQE52buP+2VvpwIZdF0RAgckAKCB0YJDGhsXVE1Q0MFT12np8TsKJQCeOlYW
F29jKTHJiy4ST98SzEsBQ7Q=
=s1Hg
-----END PGP SIGNATURE-----