calimac: (puzzle)
[personal profile] calimac
1. Go to an online vendor you've used before. Fill up your shopping cart.

2. Hit "checkout". The system will tell you to log into your account.

3. Curse quietly. All your old account information and passwords were lost when your computer crashed a year ago, and you haven't ordered with this vendor since then.

4. Try a few user names and passwords that you frequently use for low-security accounts. They don't work.

5. Since you think you know the username, click the "Reset password" button.

6. Now it asks you for the answers to your security questions. Discover that you don't remember the answers to your security questions.

7. But not to worry! It says that if you don't remember the answers to your security questions, you'll have to create a new account.

8. Go to the new account page.

8.1. By this time you've already spent more time trying to check out than you spent shopping.

9. Fill out everything on the account page.

10. The button doesn't work. Enable JavaScript.

11. This erases everything you've entered on the page. Fill it all out again.

11.1. By this time you've spent twice as much time trying to check out as you spent shopping.

12. Hit the button. Get an error message saying it's matched up your information and you appear to already have an account. Duh. So it won't let you create a new one. Double-duh.

13. Curse again, more loudly this time. Go back to the login page and try again to remember your password and/or security questions. Fail.

14. Go back to the create-account page. Since you don't have another address, try changing your e-mail contact to a different account and your phone number to your cell phone.

15. It works! Go to the payment page.

16. Go the other room where your wallet is, because you can't remember your credit card number. You used to remember it, because of the frequency with which you order online, but the company reissued the credit card with a new number a few months ago. Note the part of the number you've forgotten, and return to the computer.

17. Go back to the wallet and look up the credit card's 3-digit security code.

18. Go back to the wallet and look up the credit card's expiration date.

18.1. You could have done all these at once, of course, or have just brought the card to the computer, but each time you forgot you'd need more information further down the page.

18.2. By this time you've spent four times as much time trying to check out as you spent shopping.

19. Success at last.

20 (later). Get an e-mail at the address you used for the original account warning you that someone has been trying to break into your account, and it's been locked.

Date: 2017-01-06 07:50 pm (UTC)
From: [identity profile] cmcmck.livejournal.com
And they call it high speed technomonology.............

Date: 2017-01-07 02:27 am (UTC)
From: [identity profile] athenais.livejournal.com
Oh, for pete's sake, what a gigantic hassle!

Date: 2017-01-07 06:50 pm (UTC)
From: [identity profile] whswhs.livejournal.com
Last year, my bank entered into an arrangement where they would manage my credit cards directly, rather than having First Bankcard do it for them. So they issued me new credit cards. Unfortunately, that was right when we were moving, and despite our having made forwarding arrangements, the new credit cards didn't get to me. So I went to my bank's Web site, looked up the number for problems with credit cards, and called it—and found that the first thing they asked for was to have the number of the credit card entered! Since I hadn't received the credit cards, I obviously had no way of knowing what this was, which meant I couldn't be cleared to talk to anyone in the credit card department.

Whoever set up that voice mail tree had clearly not thought through all the reasons someone might need to call them.

"This sort of thing has cropped up before, and it has always been due to human error."

Date: 2017-01-08 07:03 am (UTC)
From: [identity profile] kalimac.livejournal.com
I've had that sort of problem when trying to inform agencies by phone that the person they're sending mail to does not live at this address. When it works, it's less trouble than sending the mail back, but it doesn't always work. (When sending it back, I always pack it into a larger envelope: I never just write "Not at this address - return to sender" on it and hand it in at the PO counter, as I've learned the hard way that what the PO does with such material is trash it.

Date: 2017-01-08 05:56 am (UTC)
From: [identity profile] irontongue.livejournal.com
Oh, man, sorry!

Security guy Bruce Schneier believes in writing down credentials and hiding them. The more secure version of this is to write down site and login on one side of a paper and passwords on the other, then cut the page down the center and hide them separately.

I have a password safe on my phone and multiple backups of the encrypted file, in different locations. With 95 sets of credentials....

Date: 2017-01-08 06:59 am (UTC)
From: [identity profile] kalimac.livejournal.com
Ugh, what a nuisance. (As I recall, security guy Bruce Schneier also has a few critical words about security procedures that are more trouble than they're worth.) I can't possibly reasonably expect that I'll keep such a list up to date, merely on the rare chance that my computer will crash irretrievably again some day. Not that I even knew, before the crash happened, that passwords couldn't be retrieved while the rest of my files could.

Date: 2017-01-08 07:23 am (UTC)
From: [identity profile] irontongue.livejournal.com
Why couldn't they be retrieved? In an encrypted file?

The password safe is super-convenient. I always have my phone with me; if I open a new account of any type, I put in the new credentials immediately. And sometimes I let the safe generate passwords for me because that's an easy way to get a strong password.

Date: 2017-01-08 07:44 am (UTC)
From: [identity profile] kalimac.livejournal.com
Why couldn't they be retrieved? Ask Mozilla.

Remembering to, and then bothering to, put down new credentials somewhere else, especially when the computer is already saving them for me automatically, is exactly what I meant by "Ugh, what a nuisance."

Date: 2017-01-08 07:46 am (UTC)
From: [identity profile] irontongue.livejournal.com
Oh, the browser was saving the passwords, I see. I have some, but not all, passwords saved by my browser, depending on sensitivity.

Date: 2017-01-08 08:19 am (UTC)
From: [identity profile] kalimac.livejournal.com
The browser was saving the passwords, yes. Don't browsers do that? I don't use Chrome or IE any more, but both Firefox and Opera do it. What made you think that was not so?

Date: 2017-01-08 03:58 pm (UTC)
From: [identity profile] irontongue.livejournal.com
Most people I've talked with this about are using services such as LastPass or a phone-based password safe, mostly including myself.

Date: 2017-01-08 03:59 pm (UTC)
From: [identity profile] irontongue.livejournal.com
And the fact that your browser-saved passwords weren't recoverable after a crash isn't an encouragement for that to be my primary means.
Page generated Dec. 28th, 2025 03:16 pm
Powered by Dreamwidth Studios