From 5722f3ce688ce4f71a7f3a4a3aa3d070c3e47014 Mon Sep 17 00:00:00 2001 From: Micah Anderson Date: Sun, 26 Oct 2008 12:09:22 -0400 Subject: add some documentation to the user section about establishing trust --- website/getting-started-user.mdwn | 54 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) (limited to 'website/getting-started-user.mdwn') diff --git a/website/getting-started-user.mdwn b/website/getting-started-user.mdwn index 947c2da..2260256 100644 --- a/website/getting-started-user.mdwn +++ b/website/getting-started-user.mdwn @@ -104,6 +104,60 @@ subkey to your ssh agent by running: FIXME: using the key with a single ssh connection? +Establish trust +--------------- + +Now that you have the above setup, you will need to establish an +acceptable trust path to the admin(s) of a monkeysphere-enabled server +that you will be connecting to. You need to do this because the admin +is certifying the host, and you need a mechanism to validate that +certification. The only way to do that is by indicating who you trust +to certify hosts. This is a two step process: first you must sign the +key, and then you have to indicate a trust level. + +The process of signing another key is outside the scope of this +document, however the gnupg README details the signing process and you +can find good [documentation +](http://www.debian.org/events/keysigning) online detailing this +process. + +If you have signed your admins' key, you need to denote some kind of +trust to that key. To do this you should edit the key and use the +'trust' command. For the Monkeysphere to trust the assertions that are +made about a host, you need full calculated validity to the host +certifiers. This can be done either by giving full trust to one +host-certifying key, or by giving marginal trust to three different +host-certifiers. In the following we demonstrate how to add full trust +validity to a host-certifying key: + + $ gpg --edit-key + Command> trust + pub 2048R/3B757F8C created: 2008-06-19 expires: 2008-11-16 usage: CA + trust: unknown validity: full + [ unknown ] (1). ssh://monkeysphere.info + [ unknown ] (2) ssh://george.riseup.net + + Please decide how far you trust this user to correctly verify other users' keys + (by looking at passports, checking fingerprints from different sources, etc.) + + 1 = I don't know or won't say + 2 = I do NOT trust + 3 = I trust marginally + 4 = I trust fully + 5 = I trust ultimately + m = back to the main menu + + Your decision? 4 + +Note: Due to a limitation with gnupg, it is not currently possible to +limit the domain scope properly, which means that if you fully trust +an admin, this admin can currently assert host verification for any +hosts. + +Because the Monkeysphre relies on GPG's definition of the OpenPGP web +of trust, it is important to understand [how GPG calculates User ID +validity for a key](/trust-models). + Miscellaneous ------------- -- cgit v1.2.3 From b5d43f9d49d0b1e60c3f3019a2d15728d526e881 Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Sun, 26 Oct 2008 19:42:15 -0400 Subject: included the full GPG transcript of granting trust in the User QuickStart guide. --- website/getting-started-user.mdwn | 68 ++++++++++++++++++++++++++------------- 1 file changed, 45 insertions(+), 23 deletions(-) (limited to 'website/getting-started-user.mdwn') diff --git a/website/getting-started-user.mdwn b/website/getting-started-user.mdwn index 2260256..5241667 100644 --- a/website/getting-started-user.mdwn +++ b/website/getting-started-user.mdwn @@ -116,8 +116,9 @@ to certify hosts. This is a two step process: first you must sign the key, and then you have to indicate a trust level. The process of signing another key is outside the scope of this -document, however the gnupg README details the signing process and you -can find good [documentation +document, however the [gnupg +README](http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/branches/STABLE-BRANCH-1-4/README?root=GnuPG&view=markup) +details the signing process and you can find good [documentation ](http://www.debian.org/events/keysigning) online detailing this process. @@ -129,30 +130,51 @@ certifiers. This can be done either by giving full trust to one host-certifying key, or by giving marginal trust to three different host-certifiers. In the following we demonstrate how to add full trust validity to a host-certifying key: - - $ gpg --edit-key - Command> trust - pub 2048R/3B757F8C created: 2008-06-19 expires: 2008-11-16 usage: CA - trust: unknown validity: full - [ unknown ] (1). ssh://monkeysphere.info - [ unknown ] (2) ssh://george.riseup.net - - Please decide how far you trust this user to correctly verify other users' keys - (by looking at passports, checking fingerprints from different sources, etc.) - - 1 = I don't know or won't say - 2 = I do NOT trust - 3 = I trust marginally - 4 = I trust fully - 5 = I trust ultimately - m = back to the main menu - - Your decision? 4 + + + $ gpg --edit-key 'Jane Admin' + gpg (GnuPG) 1.4.9; Copyright (C) 2008 Free Software Foundation, Inc. + This is free software: you are free to change and redistribute it. + There is NO WARRANTY, to the extent permitted by law. + + + pub 4096R/ABCD123A created: 2007-06-02 expires: 2012-05-31 usage: SC + trust: unknown validity: full + sub 2048R/01DECAF7 created: 2007-06-02 expires: 2012-05-31 usage: E + [ full ] (1). Jane Admin + + Command> trust + pub 4096R/ABCD123A created: 2007-06-02 expires: 2012-05-31 usage: SC + trust: unknown validity: full + sub 2048R/01DECAF7 created: 2007-06-02 expires: 2012-05-31 usage: E + [ full ] (1). Jane Admin + + Please decide how far you trust this user to correctly verify other users' keys + (by looking at passports, checking fingerprints from different sources, etc.) + + 1 = I don't know or won't say + 2 = I do NOT trust + 3 = I trust marginally + 4 = I trust fully + 5 = I trust ultimately + m = back to the main menu + + Your decision? 4 + + pub 4096R/ABCD123A created: 2007-06-02 expires: 2012-05-31 usage: SC + trust: full validity: full + sub 2048R/01DECAF7 created: 2007-06-02 expires: 2012-05-31 usage: E + [ full ] (1). Jane Admin + Please note that the shown key validity is not necessarily correct + unless you restart the program. + + Command> save + Key not changed so no update needed. + $ Note: Due to a limitation with gnupg, it is not currently possible to limit the domain scope properly, which means that if you fully trust -an admin, this admin can currently assert host verification for any -hosts. +an admin, you'll trust all their certifications. Because the Monkeysphre relies on GPG's definition of the OpenPGP web of trust, it is important to understand [how GPG calculates User ID -- cgit v1.2.3 From 12dfa2eccb5489021507bf40447c4495decd9fd0 Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Sun, 26 Oct 2008 20:17:13 -0400 Subject: Removed the gnutls component from our APT repo, since gnutls 2.6 is now in debian/unstable. Documented the changes, and changed the warning message that monkeysphere emits too. --- repo/conf/distributions | 8 ++++---- src/monkeysphere | 2 +- website/getting-started-user.mdwn | 19 +++++++------------ website/news/gnutls-2.6-enables-monkeysphere.mdwn | 19 +++++++++++++++++++ website/news/modified-gnutls-2.4.x-available.mdwn | 10 ++++++++++ 5 files changed, 41 insertions(+), 17 deletions(-) create mode 100644 website/news/gnutls-2.6-enables-monkeysphere.mdwn (limited to 'website/getting-started-user.mdwn') diff --git a/repo/conf/distributions b/repo/conf/distributions index 5ed1ab7..c97310e 100644 --- a/repo/conf/distributions +++ b/repo/conf/distributions @@ -1,10 +1,10 @@ -Origin: The MonkeySphere Project -Label: MonkeySphere/Debian +Origin: The Monkeysphere Project +Label: Monkeysphere/Debian Suite: experimental Codename: experimental Architectures: i386 powerpc amd64 arm source -Components: monkeysphere gnutls -Description: Packages implementing the monkeysphere for debian +Components: monkeysphere +Description: Packages implementing the Monkeysphere for debian SignWith: 2E8DD26C53F1197DDF403E6118E667F1EB8AF314 DscIndices: Sources Release . .gz DebIndices: Packages Release . .gz diff --git a/src/monkeysphere b/src/monkeysphere index 1db4f20..dd689b5 100755 --- a/src/monkeysphere +++ b/src/monkeysphere @@ -172,7 +172,7 @@ function subkey_to_ssh_agent() { if ! test_gnu_dummy_s2k_extension ; then failure "Your version of GnuTLS does not seem capable of using with gpg's exported subkeys. -You may want to consider patching or upgrading. +You may want to consider patching or upgrading to GnuTLS 2.6 or later. For more details, see: http://lists.gnu.org/archive/html/gnutls-devel/2008-08/msg00005.html" diff --git a/website/getting-started-user.mdwn b/website/getting-started-user.mdwn index 5241667..e0a2dab 100644 --- a/website/getting-started-user.mdwn +++ b/website/getting-started-user.mdwn @@ -87,21 +87,16 @@ Using your OpenPGP authentication key for SSH Once you have created an OpenPGP authentication subkey, you will need to feed it to your ssh agent. -Currently (2008-08-23), gnutls does not support this operation. In order -to take this step, you will need to upgrade to a patched version of -gnutls. You can easily upgrade a Debian system by adding the following -to `/etc/apt/sources.list.d/monkeysphere.list`: - - deb http://archive.monkeysphere.info/debian experimental gnutls - deb-src http://archive.monkeysphere.info/debian experimental gnutls - -Next, run `aptitude update; aptitude install libgnutls26`. - -With the patched gnutls installed, you can feed your authentication -subkey to your ssh agent by running: +The GnuTLS library supports this operation as of version 2.6, but +earlier versions do not. With a recent version of GnuTLS installed, +you can feed your authentication subkey to your ssh agent by running: $ monkeysphere subkey-to-ssh-agent +If you can't (or don't want to) upgrade to GnuTLS 2.6 or later, there +are patches for GnuTLS 2.4 available in [the Monkeysphere git +repo](/community). + FIXME: using the key with a single ssh connection? Establish trust diff --git a/website/news/gnutls-2.6-enables-monkeysphere.mdwn b/website/news/gnutls-2.6-enables-monkeysphere.mdwn new file mode 100644 index 0000000..b7894c5 --- /dev/null +++ b/website/news/gnutls-2.6-enables-monkeysphere.mdwn @@ -0,0 +1,19 @@ +[[meta title="GnuTLS 2.6.x enables Monkeysphere to read authentication subkeys"]] + +We [announced earlier](/news/modified-gnutls-2.4.x-available) that the +Monkeysphere project was providing patched versions of GnuTLS to +support one piece of Monkeysphere functionality. Fortunately, those +patches are no longer needed, because as of [version +2.6](http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/3135), +GnuTLS contains the necessary functionality natively. + +Therefore, our project will no longer provide patched copies of +GnuTLS, though we will continue to keep the patch alive in in [our git +repository](/community) until GnuTLS 2.6 has been more widely adopted. + +If you were pulling patched versions of GnuTLS 2.4 from the +Monkeysphere archive, you may prefer to pull GnuTLS 2.6 from [debian's +experimental archive](http://wiki.debian.org/DebianExperimental) (at +least until it GnuTLS 2.6 drops into unstable, which should happen +shortly after the release of +[lenny](http://wiki.debian.org/DebianLenny). diff --git a/website/news/modified-gnutls-2.4.x-available.mdwn b/website/news/modified-gnutls-2.4.x-available.mdwn index 44e08d0..36cfbfc 100644 --- a/website/news/modified-gnutls-2.4.x-available.mdwn +++ b/website/news/modified-gnutls-2.4.x-available.mdwn @@ -1,5 +1,15 @@ [[meta title="Modified GnuTLS 2.4.x available"]] +----- + +**2008-10-25 UPDATE:** [GnuTLS 2.6 has been released, and it contains the +functionality we needed](/news/gnutls-2.6-enables-monkeysphere). +Please upgrade to GnuTLS 2.6 if you need Monkeysphere to deal with +passphrase-protected authentication subkeys. The information on this +page is now of historical interest only. + +----- + The MonkeySphere project is now making available a patched version of [GnuTLS](http://gnutls.org/) version 2.4.x, which enhances the utility of the `monkeysphere` package by enabling it to read authentication -- cgit v1.2.3