Testing PGP on List

[Gregory Nowak]

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

Hi Thomas.

I've just tried out your .muttrc additions as well as the gpgfilter.sh
script. However, I get the following when opening a signed message:

Invoking PGP...sed: -e expression #1, char 38: Invalid range end
                                                                sed:
                                                                -e
                                                                expression
                                                                #1,
                                                                char
                                                                22:
                                                                Invalid
                                                                range
                                                                end
                                                                                                                 Press any key to continue...

Since I'm not familiar with sed, and since regular expressions are not
something I'm good at, could you or someone else please enlighten me
as to what the problem is? Thanks.

Greg


On Thu, Mar 25, 2004 at 10:21:30AM -0600, Thomas Stivers wrote:
> On 03/25/04  7:25 AM -0700, Steve Holmes wrote:
> 
> > have to be verified manually where Mutt automatically verifies the
> > others sent from Greg Nowak, Alex Snow, myself, and a couple others.
> > As far as I know, they are choosing the inline approach to make it
> > onto this list.  When I receive your messages, I need to do a <esc> P
> > from Mutt to do the verification.  At that point, verification is
> > successful and then looks like the others.  That Mutt command "looks
> > for traditional signatures".  Any way, glad the learning curve is
> > through pretty much and I can begin finding practical uses for it:).
> 
> When mutt sends inline signatures it adds an "x-action=pgp-signed"
> section to the content-type header. Some other mailers don't do this,
> and therefore mutt doesn't know from the headers that the message is
> signed. You can probably make a procmail/maildrop/whatever rule to
> modify the content-type header so these messages can be automatically
> verified, but I haven't tried that. I believe only 1.5.x versions of mut
> support this by default though so it may not work for everybody.
> 
> As a side note I have used the display_filter setting in mutt to
> eliminate some of the verbose gpg output for signed messages. I made
> macros to switch the filter on and off so I can see the details for
> messages that do not verify for example. 
> To set this up I have in my .muttrc:
> 
> set display_filter=~/.mutt/gpgfilter.sh
> macro pager <F5> <enter-command>set\ display_filter=.mutt/gpgfilter.sh<enter><exit><display-message> "strip pgp output"
> macro pager <F6> <enter-command>unset\ display_filter<enter><exit><display-message> "show pgp output
> 
> And the gpgfilter.sh script looks like the following:
> 
> #!/bin/sh
> 
> sed '/^.*\[-- PGP output follows --\]$/,/\[-- End of PGP output --]/d' |\
> sed '/^.*\[-- .* --\]$/d'
> 
> This script actually removes all the informational lines from the top of
> messages, but it can be changed as needed.
> 
> HTH
> 
> -- 
> Clarke's Corollary:
> Any technology distinguishable from magic is insufficiently advanced.
> Thomas Stivers	e-mail: stivers_t at tomass.dyndns.org
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
Free domains: http://www.eu.org/ or mail dns-manager at EU.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAYyHR7s9z/XlyUyARAgg4AKCWgIkEhgwgRUnQ2Z8KCb35a/ppHACcDjOV
KRJmIRVAEeskI4qYhvnydp0=
=marH
-----END PGP SIGNATURE-----