Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: <#secure method=pgp mode=sign> is broken for koi8-r
Date: Sat, 25 Jan 2003 20:42:24 +0100	[thread overview]
Message-ID: <ilulm19584f.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3znpq6yka.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 24 Jan 2003 22:13:41 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> deskpot@myrealbox.com (Vasily Korytov) writes:
>
>>  VK> Attached is the message, signed with method=pgp in just updated from CVS
>>  VK> Gnus, containing only one Cyrillic word: ``тест'' (transliteration for
>>  VK> ``test''). Note, that I didn't forward it from Gnus, but copied it
>>  VK> directly from my mailbox.
>>
>> Sorry, Gnus had tweaked it, while sending so I'll paste it again -- this
>> time, inline. Here it goes:
>
> I'm not all that familiar with the PGP code -- could someone more
> familiar take a peek at this problem?

Supporting MIME and non-MIME aware OpenPGP at the same time is tricky.
I installed the following, which is based on the assumption that users
don't want to clear-sign non-textual material.

The non-MIME aware OpenPGP support in Gnus should be revisited
somewhat IMHO, right it works for textual data (unless there are more
problems similar to this one), but it would be nice to support more.
I.e., attaching files and marking that part with "sign=pgp" should
encode it as a normal, non-clearsigned, OpenPGP message with the MIME
headers left unchanged (this would make it interoperate with various
Outlook plugins).

--- mm-encode.el.~6.12.~	Sun Dec  1 16:53:21 2002
+++ mm-encode.el	Sat Jan 25 20:32:54 2003
@@ -164,6 +164,9 @@
 	(pop rules)))))
 
 (defun mm-qp-or-base64 ()
+  (if (equal mm-use-ultra-safe-encoding '(sign . "pgp"))
+      ;; perhaps not always accurate?
+      'quoted-printable
   (save-excursion
     (let ((limit (min (point-max) (+ 2000 (point-min))))
 	  (n8bit 0))
@@ -178,7 +181,7 @@
 	      ;; non-ASCII char when splitting parts by charset.
 	      (= n8bit 1))
 	  'quoted-printable
-	'base64))))
+	  'base64)))))
 
 (provide 'mm-encode)
 




  reply	other threads:[~2003-01-25 19:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 17:44 Vasily Korytov
2003-01-21 17:50 ` Vasily Korytov
2003-01-24 21:13   ` Lars Magne Ingebrigtsen
2003-01-25 19:42     ` Simon Josefsson [this message]
2003-01-26 17:31       ` Vasily Korytov
2003-01-21 19:07 ` please comment on my setup dave-mlist
2003-01-21 21:33   ` Andreas Fuchs
2003-01-21 23:06     ` dave-mlist
2003-01-22  0:06     ` Gmane (was Re: please comment on my setup) dave-mlist
2003-01-22  8:17       ` Gmane Frank Schmitt
2003-01-22  8:19       ` Gmane Andreas Fuchs
2003-01-22  7:07   ` please comment on my setup Kai Großjohann

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=ilulm19584f.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /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).