From 2afb0dd66332136f47d08f2ee4de292eb73c8779 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Wed, 27 May 2015 08:52:01 +0100 Subject: Do not directly enable emailauth by default, only indirectly via openid This avoids nasty surprises on upgrade if a site is using httpauth, or passwordauth with an account_creation_password, and relying on only a select group of users being able to edit the site. We can revisit this for ikiwiki 4. --- doc/plugins/emailauth.mdwn | 5 +++-- doc/todo/emailauth.mdwn | 2 +- doc/todo/separate_authentication_from_authorization.mdwn | 5 +++++ 3 files changed, 9 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/plugins/emailauth.mdwn b/doc/plugins/emailauth.mdwn index 74097d2cc..463666535 100644 --- a/doc/plugins/emailauth.mdwn +++ b/doc/plugins/emailauth.mdwn @@ -5,8 +5,9 @@ This plugin lets users log into ikiwiki using any email address. To complete the login, a one-time-use link is emailed to the user, and they can simply open that link in their browser. -It is enabled by default, but can be turned off if you want to only use -some other form of authentication, such as [[passwordauth]] or [[openid]]. +It is (indirectly) enabled by default, but can be turned off if you want to +only use some other form of authentication, such as [[passwordauth]] or +[[openid]]. Users who have logged in using emailauth will have their email address used as their username. In places where the username is displayed, like the diff --git a/doc/todo/emailauth.mdwn b/doc/todo/emailauth.mdwn index 4683bbad2..ec7b4b96d 100644 --- a/doc/todo/emailauth.mdwn +++ b/doc/todo/emailauth.mdwn @@ -127,7 +127,7 @@ Thoughts anyone? --[[Joey]] >>> >>> Another way to do it would be to hash the email address, >>> so the commit appears to come from ->>> `smcv ` instead of +>>> `smcv ` instead of >>> from `smcv ` - if the hash is of `mailto:whatever` >>> (like my example one) then it's compatible with >>> [FOAF](http://xmlns.com/foaf/spec/#term_mbox_sha1sum). diff --git a/doc/todo/separate_authentication_from_authorization.mdwn b/doc/todo/separate_authentication_from_authorization.mdwn index 389f014c9..1eca0dced 100644 --- a/doc/todo/separate_authentication_from_authorization.mdwn +++ b/doc/todo/separate_authentication_from_authorization.mdwn @@ -12,6 +12,11 @@ owner (and maybe their outsourced service providers), but not available to random third parties. The principle of least astonishment would suggest that we should do the same here. +> This part is now addressed by cloaking email addresses: +> `smcv@debian.org` → `smcv@02f3eecb59311fc89970578832b63d57a071579e` +> (that's the sha1sum of `mailto:smcv@debian.org`, as used in FOAF). +> --[[smcv]] + (The expectation of privacy for direct git commits is rather different: I think we can expect direct git committers to know that they should either set a plausible non-email-address in their git identity, -- cgit v1.2.3