Dark Shadow Hunter, on Apr 26 2010, 02:08 PM, said:
WW I will have to look into this. It would suck if something happens to me and I no one can get into my home field's web site.
There is a very important point there, it's not just a matter of getting your passwords etc to someone when you die. If its a 'business' website you need a contingency in place for you being unavailable.
e.g. Whereever posible eahc individual should have their own user & password but that will not be the case for standard hosted services. Tell someone the login details anyway, have a password sequence that you change to, or store it somewhere.
Each option has it's benefits and problems. If people have full rights at all times then they can do unauthorised changes at any time as opposed to just acces in emergencies, if you tell someone the password then you breach any auditing and they can make changes whenever (plus they can change your password and block you out), a password sequence has the risk that when someone tries to work out which one to use they fail too many times and lock out plus people are lazy so a password sequence for one account may give away your secrets to other accounts such as your private email, if you store the password anyone who manages to access the stored locatio can get the password. (If you seal it in an envelope you can see that someone has opened it but you don't necessarily know who did)
Things like deathswitch have other benefits such as legal rights of access in the case of your death. It can be difficult to get hold of access if you have to call and state someone has died and they may require you to get powers of attourney etc.