Gnus development mailing list
 help / color / mirror / Atom feed
From: Matthias Andree <ma+gnus@dt.e-technik.uni-dortmund.de>
Subject: GNUS "PGP Sign" bug (CVS Gnus)
Date: Sun, 28 Dec 2003 22:58:45 +0100	[thread overview]
Message-ID: <m34qvkppt6.fsf@merlin.emma.line.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 440 bytes --]

Hi,

it seems that GNUS' non-MIME "PGP Sign" (<#secure method=pgp mode=sign>)
is a bit overzealous with MIME encoding, it trashes the boundaries by
encoding the "-" in the leftmost column to "=2D". It should leave
the ----- boundaries alone - these need to be encoded BEFORE signing,
NOT AFTER signing.

See below what it has produced for my mail to ports@freebsd.org:

-- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95

[-- Attachment #2: Type: message/rfc822, Size: 4305 bytes --]

From: Matthias Andree <matthias.andree@gmx.de>
To: freebsd-ports@freebsd.org
Subject: TESTERS WANTED: e2fsprogs port update
Date: Sun, 28 Dec 2003 22:50:59 +0100
Message-ID: <m3brpspq64.fsf@merlin.emma.line.org>

=2D----BEGIN PGP SIGNED MESSAGE-----

Hello,

the e2fsprogs port has not been looked after in a long time, and so it
does not know about ext3fs, making it impossible to mount ext3fs file
systems under FreeBSD that need journal recovery without booting Linux.

I have updated the port to the current BK state of e2fsprogs, hacked the
BK version of e2fsprogs to support FreeBSD and tested it a bit (e2fsck
=2D -f on my ext2 and ext3 file systems), successfully, on FreeBSD 5-CURRENT
and 4-STABLE, either one checked out after 2003-12-27.

I need testers of the new port, particularly from FreeBSD versions that
are not bleeding edge and from non-i386 architectures.

The port is available at http://mandree.home.pages.de/freebsd/e2fsprogs/
installation instructions are also at that page.

You'll have 5 kB of direct download for the shar files and 3.2 MB of
indirect downloads (when typing "make fetch" from the new port
directory) for the tarball and patch.

I have sent off the patches to the upstream maintainer, Theodore Y. Ts'o,
but no current upstream release with usable FreeBSD exists at the time
of this writing.

Your feedback will be needed to convince the upstream maintainer to take
the FreeBSD patches.

Reference: the e2fsprogs home pages is at http://e2fsprogs.sourceforge.net/

Thanks in advance for your help.

=2D --=20
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUBP+9QQydEoB0mv1ypAQGdWgP/WqsAd5tgQPFywKLLQTVFG+3ko23O2fde
H894CddpP0BADCI5Un8xZKD+b/VuII1fU6+8X3okI1Dr96MmWVsVtLE6+nClbgei
W8SNnrZJBF958YkbbkeO+r/EhK0GobsSWhIFiryZUU68YxPjzQ6vbI/XD6W9aZ85
uXvmMSgiUPo=3D
=3DIas4
=2D----END PGP SIGNATURE-----
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"

             reply	other threads:[~2003-12-28 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28 21:58 Matthias Andree [this message]
2003-12-28 22:49 ` Jeremy Maitin-Shepard
2003-12-28 22:55 ` Jesper Harder
2003-12-29  0:52   ` Matthias Andree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m34qvkppt6.fsf@merlin.emma.line.org \
    --to=ma+gnus@dt.e-technik.uni-dortmund.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).