Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] PGP INLINE - can't make it work
Date: Mon, 08 Mar 2010 11:41:18 +0100	[thread overview]
Message-ID: <1268044772-sup-4188@midna.zekjur.net> (raw)
In-Reply-To: <201003081129.47648.piotr.kempa@wp.eu>

Hi Piotr,

Excerpts from piotr.kempa's message of Mo Mär 08 11:29:47 +0100 2010:
> Okay, I found the patch here: http://www.mail-archive.com/sup-
> talk@rubyforge.org/msg02770.html
> 
> And it is included in 0.11, I just checked in the code. 
You are mistaken, this is a different patch (not for inline gpg).

> So in order to decide about encrypted content you actually have to look inside 
> the body of the message, not just at the header. At least I couldn't find any 
> indication in the headers :(
This is actually the very intention of inline gpg -- to work with existing
standards/mailclients which do not support different headers.

Unfortunately I did not yet have time to rework the patch, but I hope to do
so in the next few days.

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2010-03-08 10:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 17:08 kosmici-atakuja
2010-02-26 17:43 ` Sven Schober
2010-03-02 10:49   ` piotr.kempa
2010-03-02 13:59     ` Michael Stapelberg
2010-03-02 14:19       ` piotr.kempa
2010-03-08 10:18         ` piotr.kempa
2010-03-08 10:29           ` piotr.kempa
2010-03-08 10:41             ` Michael Stapelberg [this message]
2010-03-08 10:50             ` Sven Moritz Hallberg
2010-03-08 11:20               ` piotr.kempa
2010-03-09 17:06                 ` Michael Stapelberg
2010-03-10 10:53                   ` Piotr Kempa
2010-03-10 11:14                     ` Michael Stapelberg
2010-03-10 14:41                       ` Piotr Kempa
2010-03-10 21:21                         ` Michael Stapelberg
2010-03-02 14:12     ` Sam Hall

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=1268044772-sup-4188@midna.zekjur.net \
    --to=michael+sup@stapelberg.de \
    --cc=sup-talk@rubyforge.org \
    /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