From: Kristian Fiskerstrand <k_f@gentoo.org>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] New project: Crypto
Date: Mon, 28 Dec 2015 16:07:33 +0100 [thread overview]
Message-ID: <9AB9A178-B4A1-4493-A3A4-0B3A855E603F@gentoo.org> (raw)
In-Reply-To: <20151228145813.40343a43@symphony.aura-online.co.uk>
[Sent from my iPad, as it is not a secured device there are no cryptographic keys on this device, meaning this message is sent without an OpenPGP signature. In general you should *not* rely on any information sent over such an unsecure channel, if you find any information controversial or un-expected send a response and request a signed confirmation]
> On 28 Dec 2015, at 15:58, James Le Cuirot <chewi@gentoo.org> wrote:
>
> On Mon, 28 Dec 2015 09:42:40 -0500
> Rich Freeman <rich0@gentoo.org> wrote:
>>
..
>> And this would be why I don't bother to sign my emails any longer.
>> The FOSS world is still stuck in the days when people ran X11-based
>> MUAs and stored their mail in conventional folders. I've yet to see a
>> decent browser-based MUA or Android client which does signing.
>> Squirrelmail does, but it is really lacking compared to something like
>> Gmail.
>
> I haven't tried the feature myself but K9 Mail, which is highly
> regarded, does it via APG on Android.
iirc k9 doesnt support PGP/MIME (RFC3156), but some interesting things happening with OpenKeychain (https://www.openkeychain.org/k-9/ ) in that regard. We actually discussed it a bit during last OpenPGP summit in zurich.
The main issue is key storage, though. For signatures you can use a dedicated signing subkey, however you get in problem with encrypted emails as mobile devices are not really secure devices and should never have cryptographic material. What could work in this case is a NFC (or for that matter bluetooth, although it needs to be properly paired etc etc) channel with a separate device with a separate keychain and display so you can verify the request, and never actually expose private key material to the cellphone.
In the mean time I just include the notice whenever I don't sign, at least some people notice it and gives it another thought.
next prev parent reply other threads:[~2015-12-28 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:12 [gentoo-dev] [RFC] New project: Crypto Kristian Fiskerstrand
2015-11-25 19:20 ` Daniel Campbell
2015-11-25 20:21 ` Kristian Fiskerstrand
2015-12-27 22:49 ` Andrew Savchenko
2015-12-28 13:11 ` Kristian Fiskerstrand
2015-12-28 14:42 ` Rich Freeman
2015-12-28 14:58 ` James Le Cuirot
2015-12-28 15:07 ` Kristian Fiskerstrand [this message]
2015-12-28 15:15 ` Kristian Fiskerstrand
2015-12-28 18:35 ` Rich Freeman
2015-12-29 13:58 ` Kristian Fiskerstrand
2015-12-29 14:27 ` Rich Freeman
2015-12-29 16:59 ` [gentoo-dev] " Duncan
2015-12-29 15:02 ` [gentoo-dev] " Yury German
2015-12-28 16:35 ` Andrew Savchenko
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=9AB9A178-B4A1-4493-A3A4-0B3A855E603F@gentoo.org \
--to=k_f@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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