Re: [openpgp] OpenPGP private certification
Christoph Anton Mitterer <calestyo@scientia.net> Wed, 08 April 2015 18:54 UTC
Return-Path: <calestyo@scientia.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB6E01B34FD for <openpgp@ietfa.amsl.com>; Wed, 8 Apr 2015 11:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8w_f6mvDjdgp for <openpgp@ietfa.amsl.com>; Wed, 8 Apr 2015 11:54:47 -0700 (PDT)
Received: from mailgw02.dd24.net (mailgw-02.dd24.net [193.46.215.43]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1EFF1B34FA for <openpgp@ietf.org>; Wed, 8 Apr 2015 11:54:46 -0700 (PDT)
Received: from mailpolicy-01.live.igb.homer.key-systems.net (mailpolicy-02.live.igb.homer.key-systems.net [192.168.1.27]) by mailgw02.dd24.net (Postfix) with ESMTP id 95C235FB58; Wed, 8 Apr 2015 18:54:45 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at mailpolicy-02.live.igb.homer.key-systems.net
Received: from mailgw02.dd24.net ([192.168.1.36]) by mailpolicy-01.live.igb.homer.key-systems.net (mailpolicy-02.live.igb.homer.key-systems.net [192.168.1.25]) (amavisd-new, port 10236) with ESMTP id 0bUD3MNbCw0g; Wed, 8 Apr 2015 18:54:43 +0000 (UTC)
Received: from heisenberg.fritz.box (ppp-188-174-180-118.dynamic.mnet-online.de [188.174.180.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailgw02.dd24.net (Postfix) with ESMTPSA; Wed, 8 Apr 2015 18:54:43 +0000 (UTC)
Message-ID: <1428519282.5137.78.camel@scientia.net>
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 08 Apr 2015 20:54:42 +0200
In-Reply-To: <CAMm+Lwjyt9+u8zL_UpSFK8P55-b751PnijLjKXSvSQ+EWz7XvQ@mail.gmail.com>
References: <CAA7UWsUz65C0GAQo8Yf7ZOeT9BYy+NLV5pbbPg+Ok0-72ca1eA@mail.gmail.com> <1426721882.4249.72.camel@scientia.net> <5510578A.80304@iang.org> <1427140788.10191.75.camel@scientia.net> <5510B7CF.8060308@iang.org> <1427168189.10191.241.camel@scientia.net> <5511FE82.6010807@iang.org> <1427243451.10191.375.camel@scientia.net> <5512F137.80702@iang.org> <CAHBU6isgirHnx+gHP+OiHuvhzD+1OTCShCHEkhWcqEmUn9qnzQ@mail.gmail.com> <CAMm+LwiXKf1DvgbHaZoJnKdCVbak-jderv6Z8KDs9xPEbUuYQQ@mail.gmail.com> <1427343948.23692.14.camel@scientia.net> <CAMm+Lwi5bVTujuazTXw7oRty7n5RtsObEfNrJzmbtPiOb-X25g@mail.gmail.com> <m27fu3fsom.fsf@usma1mc-0csx92.kendall.corp.akamai.com> <CAMm+LwjBuZfP4NwRCy23_d9eRtcfUiLKdyZOu+jYT72HfB0g9g@mail.gmail.com> <87vbhlt8tg.fsf@alice.fifthhorseman.net> <CAMm+Lwjo5eyCHNahqWcwUBoaevCw2s3WAeq-2=maW=JEpCFWxA@mail.gmail.com> <sjmvbheioxv.fsf@securerf.ihtfp.org> <CAMm+Lwi4zsnQoX0R0CRbmDceLKi8B3ipHnBvSqNgo8FA8UYh3w@mail.gmail.com> <87mw2i28nr.fsf@vigenere.g10code.de> <CAMm+Lwief440=CdrQrjma1qrFHJYKTZAM5gZ1N9mMVikFvDzSw@mail.gmail.com> <87vbh6zqsy.fsf@vigenere.g10code.de> <CAMm+Lwiq71ToxKwPgLPKhGvPCC5QRjeVeV+V8yOiG+e91JYmhQ@mail.gmail.com> <1428516305.5137.36.camel@scientia.net> <CAMm+Lwjyt9+u8zL_UpSFK8P55-b751PnijLjKXSvSQ+EWz7XvQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="sha-512"; protocol="application/x-pkcs7-signature"; boundary="=-OCHuRd0yvrfiZiZ2jFIX"
X-Mailer: Evolution 3.12.9-1+b1
Mime-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/SPgsbkNmEa0HY9uruw-Tz0ez9Ps>
Cc: IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] OpenPGP private certification
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2015 18:54:49 -0000
On Wed, 2015-04-08 at 14:29 -0400, Phillip Hallam-Baker wrote: > > Why should it give you any security? > Same reason that backing up your files is the number one security > priority: security means being able to assess and control risks to > your assets. Confidentiality is only one concern and one that is > fairly low down. Integrity is almost always more important. I don't think that either you or me can decide which of the aspects of "data security" is most important to a user. It completely depends on the usage scenario and for some integrity may be actually less important. But in terms of our discussions here we probably mostly deal with confidentiality, integrity and authenticity. And I can't see how a own domain name helps here. > If I invest in hallam@gmail.com then I am making myself vulnerable to > a change of policy. I have little choice but to pay if they decide to > start charging $50/month. Sure, but it doesn't improve your confidentiality, integrity and authenticity. Just make a new UID with another address, publish it, bon. > >> I have a huge part of my > >> brand invested in hallam@gmail.com which I don't own. Which is why I > >> switched to phill@hallambaker.com for ietf work. But I have yet to win > >> that argument. > > It only gives you that some company cannot easily take away your mail > > address, but OTOH it's probably an illusion to believe that your own > > domain name protects you much more from this. > > > > See cases like the German person called "Shell", who had shell.de and > > guess who has it now. > > Which is one reason I don't trust ICANN's vision of DNSSEC. Well but that has happened before DNSSEC, it's more a problem of DNS itself or rather of courts being able to rule about the cyberspace. > > Sure, it has similar problems like the X.509 PKI, just on a less extreme > > scale. > If trades one set of problems for another. Which problems would it have that X.509 PKI wouldn't have? > So example.com.<fingerprint> becomes an assertion 'the names in > example.com as controlled by a valid, current security policy signed > by a key matching <fingerprint>. Uhm that probably only works when you chain als signatures of the respective domain (i.e. NSEC instead of NSEC3), right? But to me this isn't a integration of DNS into OpenPGP, like in the sense of using DNS to implement a certain trust model (yes Werner, trust models are not part of OpenPGP ;-P) It's vice versa an integration of OpenPGP into DNS,... which is IMHO again totally fine (at least per se and form the OpenPGP PoV). > Now that is an approach I can tie servers to in admin files. AFAIU, you basically just tried to secure your zones via DNSSEC and OpenPGP, right? I think that approach is unnecessarily complex, since AFAIU it requires to fully walk through the zone. Why don't you just use the openpgp key to sign the DNSKEY RRs (+put the result in some special RR) and validate that in your resolver before making any further use of DNSSEC? Of course, for that being really secure, you'd need to tell your resolver which domains he should expect to be signed that way, just relying on the presence of the RR that holds the signature is obviously not enough (blocking attacks)... and relying on DNSSEC for that obviously defeats the purpose. Signatures must obviously also use expiration times. Also, the method of just adding the fingerprint as an indicator smells very strong like "replay and downgrade attacks". Cheers, Chris.
- Re: [openpgp] New encryption formats for messaging Christoph Anton Mitterer
- Re: [openpgp] New encryption formats for messaging ianG
- Re: [openpgp] New encryption formats for messaging Christoph Anton Mitterer
- Re: [openpgp] New encryption formats for messaging ianG
- Re: [openpgp] New encryption formats for messaging Christoph Anton Mitterer
- [openpgp] Manifesto - who is the new OpenPGP for? ianG
- Re: [openpgp] Manifesto - who is the new OpenPGP … Christoph Anton Mitterer
- Re: [openpgp] Manifesto - who is the new OpenPGP … Phillip Hallam-Baker
- Re: [openpgp] Manifesto - who is the new OpenPGP … Falcon Darkstar Momot
- Re: [openpgp] Manifesto - who is the new OpenPGP … Werner Koch
- Re: [openpgp] Manifesto - who is the new OpenPGP … Stephen Paul Weber
- Re: [openpgp] Manifesto - who is the new OpenPGP … Stephen Paul Weber
- Re: [openpgp] Manifesto - who is the new OpenPGP … Wyllys Ingersoll
- Re: [openpgp] Manifesto - who is the new OpenPGP … Clint Adams
- Re: [openpgp] Manifesto - who is the new OpenPGP … Phillip Hallam-Baker
- Re: [openpgp] Manifesto - who is the new OpenPGP … ianG
- Re: [openpgp] Manifesto - who is the new OpenPGP … ianG
- Re: [openpgp] Manifesto - who is the new OpenPGP … Tim Bray
- Re: [openpgp] Manifesto - who is the new OpenPGP … Phillip Hallam-Baker
- Re: [openpgp] Manifesto - who is the new OpenPGP … Christoph Anton Mitterer
- Re: [openpgp] Manifesto - who is the new OpenPGP … John Kreznar
- Re: [openpgp] Manifesto - who is the new OpenPGP … Werner Koch
- Re: [openpgp] Manifesto - who is the new OpenPGP … Phillip Hallam-Baker
- Re: [openpgp] Manifesto - who is the new OpenPGP … Brian Sniffen
- Re: [openpgp] Manifesto - who is the new OpenPGP … Bill Frantz
- Re: [openpgp] Manifesto - who is the new OpenPGP … Phillip Hallam-Baker
- Re: [openpgp] Manifesto - who is the new OpenPGP … Christoph Anton Mitterer
- Re: [openpgp] Manifesto - who is the new OpenPGP … Christoph Anton Mitterer
- [openpgp] OpenPGP private certification [was: Re:… Daniel Kahn Gillmor
- Re: [openpgp] OpenPGP private certification [was:… Phillip Hallam-Baker
- Re: [openpgp] OpenPGP private certification [was:… Daniel Kahn Gillmor
- Re: [openpgp] OpenPGP private certification [was:… Phillip Hallam-Baker
- [openpgp] public logging of e-mail certificates [… Daniel Kahn Gillmor
- Re: [openpgp] public logging of e-mail certificat… Phillip Hallam-Baker
- Re: [openpgp] public logging of e-mail certificat… Daniel Kahn Gillmor
- Re: [openpgp] public logging of e-mail certificat… Phillip Hallam-Baker
- Re: [openpgp] OpenPGP private certification [was:… Derek Atkins
- Re: [openpgp] public logging of e-mail certificat… Brian Sniffen
- Re: [openpgp] OpenPGP private certification [was:… Phillip Hallam-Baker
- Re: [openpgp] public logging of e-mail certificat… Phillip Hallam-Baker
- Re: [openpgp] Manifesto - who is the new OpenPGP … ianG
- Re: [openpgp] OpenPGP private certification Werner Koch
- Re: [openpgp] OpenPGP private certification Phillip Hallam-Baker
- Re: [openpgp] OpenPGP private certification Christoph Anton Mitterer
- Re: [openpgp] OpenPGP private certification Phillip Hallam-Baker
- Re: [openpgp] OpenPGP private certification Christoph Anton Mitterer
- Re: [openpgp] OpenPGP private certification Werner Koch
- Re: [openpgp] OpenPGP private certification Derek Atkins
- Re: [openpgp] OpenPGP private certification Phillip Hallam-Baker
- Re: [openpgp] OpenPGP private certification Phillip Hallam-Baker
- Re: [openpgp] OpenPGP private certification Christoph Anton Mitterer
- Re: [openpgp] OpenPGP private certification Christoph Anton Mitterer
- Re: [openpgp] OpenPGP private certification Phillip Hallam-Baker
- Re: [openpgp] OpenPGP private certification Christoph Anton Mitterer
- Re: [openpgp] OpenPGP private certification Werner Koch
- Re: [openpgp] OpenPGP private certification ianG
- Re: [openpgp] OpenPGP private certification [was:… ianG
- Re: [openpgp] public logging of e-mail certificat… Phillip Hallam-Baker
- Re: [openpgp] public logging of e-mail certificat… ianG
- [openpgp] New encryption formats for messaging David Leon Gil
- Re: [openpgp] OpenPGP private certification Ben McGinnes