From: Dmitry Bely <dbely@mail.ru>
Subject: Re: gpg.el
Date: Fri, 26 Apr 2002 20:02:44 +0400 [thread overview]
Message-ID: <k7quwiqj.fsf@mail.ru> (raw)
In-Reply-To: <87wuuupjhi.fsf@deneb.enyo.de>
Florian Weimer <fw@deneb.enyo.de> writes:
> Dmitry Bely <dbely@mail.ru> writes:
>
>> What is the preferable method to submit gpg.el bug reports? Should I post
>> them here or contact the authors directly?
>
> Better post them here, so others can help (I don't run XEmacs).
And neither you run Windows 2000 nor use a non-english charset :-)
Fortunately, the problem seems to have nothing to do with XEmacs. It
happens when I try to sign a message with an encoding different from
us-ascii (encryption is working fine as well as the us-ascii messages
signing). Here is an example:
(1) Non-signed message would be
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
(koi8-r is Cyrillic 8-bit encoding like European cp1250. Everything else is
not interesting)
(2) Signed message created by gpg.el
[---cut---]
X-From-Line: nobody Fri Apr 26 13:34:15 2002
X-Draft-From: ("nnfolder+archive:archive" "")
To: dbely@mail.ru
Subject: signature test
From: Dmitry Bely <dbely@mail.ru>
Date: Fri, 26 Apr 2002 13:33:55 +0400
Message-ID: <d6wm248s.fsf@mail.ru>
User-Agent: Gnus/5.090005 (Oort Gnus v0.05) XEmacs/21.4 (Civil Service (Windows), i586-pc-win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: base64
Lines: 13
Xref: BELY archive:1273
X-Gnus-Article-Number: 1273 Fri Apr 26 13:34:15 2002
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
8M8t0tXT08vJDQoNCkhvcGUgdG8gaGVhciBmcm9tIHlvdSBzb29uLA0KRG1pdHJ5DQo
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6-2 (MingW32)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjzJHxYACgkQytFTynJIfm+LkgCg6Xa4XWbM24zBHl1WA/N8H/MU
x1YAoIxtzJL7u2C+OLwvd0Z/hpBlKQNh
=3Drc3D
=2D----END PGP SIGNATURE-----
[---cut---]
As you see, Content-Transfer-Encoding is incorrect: original koi8-r text is
really base64-encoded, but everything else is quoted-printable. So we have
the broken message...
Hope to hear from you soon,
Dmitry
next prev parent reply other threads:[~2002-04-26 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 12:08 gpg.el Dmitry Bely
2002-04-26 15:28 ` gpg.el Florian Weimer
2002-04-26 16:02 ` Dmitry Bely [this message]
2002-04-29 17:45 ` mml1991.el patch (was gpg.el) Dmitry Bely
2002-05-01 10:37 ` Florian Weimer
2002-05-01 15:33 ` Dmitry Bely
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=k7quwiqj.fsf@mail.ru \
--to=dbely@mail.ru \
/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).