Hi,
On Sat, 7 Jul 2012, Andy Smith wrote:
Today a customer popped up on IRC saying that they had
broken their
VPS and couldn't remember their account details in order to use the
console / rescue VM.
[…]
As some others have replied, I'd be unhappy with the use of utility
bills.
An interface to upload allowed OpenPGP keys seems the best option so
far (multiple keys as a possibility).
On Sun, 8 Jul 2012, Mathew Newton wrote:
My e-mail is hosted on my VPS so if it's down then
the e-mail password
reset function would be no good to me anyway.
Same for me. But I could use a random other email account and sign using
a pre-arranged crypto key.
On Sun, 8 Jul 2012, Nigel Rantor wrote:
Given that I think it is reasonable to expect people
who turn it off to
perform some extra work to ensure they can be authenticated if the worst
happens and they lose private keys, forget pass-phrases etc.
Ultimately, it is possible to lose access to most credentials (e.g., lost
VPS, normal email out of action, lost private keys / passphrases).
Re-identification is hard, and I guess the question is really one of how
much is required, or if the user is willing for it to happen at all.
I do like the idea of asking the customer to send you
a set amount using the
account they last used to pay for the service itself.
But only if they haven't moved accounts (okay, it's been some years since
I moved banks, but I know some who change every year or two).
On Sun, 8 Jul 2012, Gavin Westwood wrote:
I like this idea and second the not using stock
questions. The number
of websites where I have had to put my mother's maiden name and name of
[...]
I can never remember what I wrote for most of these question-answer
combinations… I find them relatively useless as a recovery mechanism.
On Sun, 8 Jul 2012, Andy Parkins wrote:
In short: paranoia. Disabling password reset implies
a level of security
that should be maintained. It's saying "I take full responsibility for the
password to this VPS, and if I lose it, I accept that I may never get access
again".
Perhaps the control panel could offer a range of options covering
different tastes/tolerances from indifferent to very paranoid. But
that makes it all very complicated.
So my end suggestion is:
- Hold a list of OpenPGP keys that are authorised for
resets/recovery, via the panel.
- As well as the "Allow password reset" switch, add two more, one for
reset via OpenPGP keys, and a final one so that the user can state
that they never want any other mechanism using (i.e., if they lose
their password, etc they "accept that I may never get access
again"). Probably need to make that last one jump through some
confirmation hoops....
For those who are prepared to accept other reidentification, a
combination of government ID combined with fresh photos plus some form
of bank transaction would be reasonable. Stick it on the policy page
and link it against that last switch.
(Aside: Has Bitfolk had any instances of customers being
incapacitated (or dying) and relatives needing to recover access to
the VPS? E.g., if it's used for domestic email?)
Cheers,
Phil.
--
Phil Brooke OpenPGP key: 0x2F0EC78A