gpg: Signature made Wed Jan 27 20:57:43 2010 UTC using DSA key ID BF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>"
gpg: aka "Andrew James Smith <andy@strugglers.net>"
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>"
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>"
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>"
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>"
Hello,
On Sun, Jan 24, 2010 at 01:42:00PM +0000, Andy Smith wrote:
> The most common support request is to reset BitFolk account
> password. I have therefore implemented a password reset feature to
> the web panel at https://panle.bitfolk.com/.
[...]
> I will put the feature live on Wednesday 27th January, so if you
> don't like the idea of the above being possible please go to
> https://panel.bitfolk.com/account/security/ and disable it.
It's live now.
So, from this point on we will have to be a lot more thorough for
the edge cases where people still need to ask support for a password reset, and this will introduce delays.
I would imagine the most common scenario will be:
+ VPS dead
+ owner away from home or otherwise without access to their password
store
+ No SSH keys configured, or not at a machine with the configured
keys available
+ Account password forgotten
+ Email address hosted solely on VPS that is dead, so password reset
not an option
Strictly speaking the above set of failures are going to be mostly
in customer hands so there is an argument that I need do nothing
more, however, two workarounds spring to mind.
One is allowing people to configure multiple email addresses
(perhaps multiple roles, each with one or more addresses). Another
is to implement management of console SSH keys into the console and
web panel, so that people have an easier time getting in.
Which would you prefer I tackled first?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"Whoever is responsible for this stunning design failure deserves continuous
cockpunches." -- jwz
