1 pushing [[this|todo/httpauth feature parity with passwordauth]] and [[this|todo/htpasswd mirror of the userdb]] further (although rather in the [[wishlist]] priority): would it make sense for users to have a `$USER/creditentials` page that is by default locked to the user and admins, where the user can state one or more of the below?
4 * ssh public key (would require an additional mechanism for writing this to a `authorized_keys` file with appropriate environment variables or prefix that makes sure the commit is checked against the right user and that the user names agree)
5 * gpg public key (once there is a mechanism that relies on gpg for authentication))
6 * https certificate hash (don't know details; afair the creation of such certificates is typically initiated server-side)
7 * password hash (this is generally considered a valuable secret; is this still true with good hashes and proper salting?)
9 such a page could have a form as described in [[todo/structured page data]] and could even serve as a way of managing users. --[[chrysn]]
projects / ikiwiki / blob