Everyday Guidebooks
Cover of Computer Basic Topics

More Books

Computer Basic Topics: Passwords and Passkeys

A Plain-English Guide to Safer Sign-Ins, Password Managers, Verification Codes, and Account Recovery

by Todd Michael

Available now

Signing in should not feel like solving a puzzle—or like gambling with your personal information. If you are searching for computer basic topics, this plain-English guide will help you understand the credentials and checks that protect your everyday accounts.

Todd Michael explains how to create strong, unique passwords, choose and use a password manager, and understand when a passkey can make signing in simpler. You will also learn what verification codes do, how to prepare recovery options before you need them, and how to spot suspicious requests that try to trick you into approving a sign-in or sharing a code.

Work through relatable examples, decision guides, and practical checklists at your own pace. Whether you are protecting your email, shopping accounts, or other personal services, you will finish with a clearer picture of how the pieces fit together and a manageable plan for putting them to work.

Contents
  1. 1. The Everyday Sign-In
  2. 2. What Passwords Protect—and Where They Fail
  3. 3. Creating Strong, Unique Credentials
  4. 4. How Password Managers Work
  5. 5. Setting Up and Using Your Vault
  6. 6. Maintaining Passwords Without the Overwhelm
  7. 7. Passkeys in Plain English
  8. 8. Creating and Using Passkeys
  9. 9. Verification Codes and Extra Checks
  10. 10. Choosing Verification for Important Accounts
  11. 11. Recovery Before You Need It
  12. 12. Lost Devices and Locked Accounts
  13. 13. Recognizing Suspicious Sign-In Requests
  14. 14. Your Personal Sign-In Plan
  15. Other Books by Todd Michael

Read a sample: 1. The Everyday Sign-In

You open your email on a new computer. The screen asks for your email address, then your password. After you enter both, another message appears: enter the code sent to your phone.

You have signed in before, but this time there are several questions. Why does the service need a code if you already supplied the password? What happens if your phone is unavailable? And if you cannot remember the password, where does the reset message go?

These questions are not signs that you are bad with technology. They are part of the ordinary puzzle of online access. Most people collect accounts over many years, on different devices, under different circumstances. A familiar routine can keep working for so long that there is little reason to examine it—until a new device, a forgotten password, or an unexpected message interrupts the routine.

This book will help you understand those interruptions and prepare for them. You do not need to master technical language or change every account today. The goal is to build a sign-in routine that is safer and still workable for you.

Let’s begin by following one ordinary sign-in from start to finish.

Imagine that Maya wants to check her email from a computer she has not used before. She opens her email provider’s website and selects Sign in. The first field asks for an email address.

Maya’s address tells the service which account she wants to access. It is an identifier: a name or label used to find an account. Depending on the service, an identifier might be an email address, a username, a phone number, or a membership number.

An identifier is not usually a secret. Maya may give her email address to friends, shops, and doctors. A person who knows it can address a message to her, but that knowledge alone should not give them access to her inbox.

This distinction is useful because sign-in screens often place the identifier and password next to each other. They serve different purposes. The identifier says, in effect, “This is the account I mean.” The credential supplies evidence that the person signing in is entitled to use it.

Some services use the same email address as the identifier for many separate accounts. Maya might use her email address to sign in to a library account, a shopping account, and a utility account. Those accounts are still separate, even though the identifier is the same. Ideally, their passwords will be different.

After Maya enters her email address, the service asks for her password. A password is one kind of credential: something used to help establish that a sign-in attempt is authorized.

Maya types it carefully. She does not need to understand every step taking place behind the screen to use it, but one principle matters: the service checks what she supplies against information it has for her account. We will look more closely at that process, and at what can go wrong, in the next chapter.

A password is useful because it is supposed to be known only to the people authorized to use it. Its usefulness is reduced if it is easy to guess, copied from another account, or given to someone pretending to be the service.

A familiar password can feel like a key you carry in your head. The comparison is helpful, with one important difference: a copied password can be used without taking the original away from you. Maya might still be able to sign in even if someone else has learned her password. Being able to open the door does not, by itself, prove that no one else has a key.

Passwords are not the only way to sign in. Some accounts offer passkeys, which let you use a device and its usual unlock method as part of the sign-in process. For example, Maya might be able to approve access with a fingerprint, face recognition, or device PIN. Passkeys work differently from passwords, and we will give them proper attention later. For now, it is enough to recognize that “credential” is the broader term: a password is one kind, and a passkey is another.

Maya enters the correct password, but the email service does not immediately open her inbox. It asks for a code sent to her phone.

This is an additional verification step. The service is looking for another piece of evidence before allowing the sign-in. You may hear this called two-step verification or multi-factor authentication. The labels vary, and the available methods vary too. The practical idea is that a password alone may not be enough to complete a sign-in.

The extra check might involve a code received by text message, a code shown in an authenticator app, a prompt on a device, or a separate security key. Some services offer several choices; others offer fewer. Each choice brings its own conveniences and limitations.

In Maya’s case, the code arrives by text. She enters it into the sign-in page she opened herself, and her inbox appears.

That code deserves care. A person who calls or messages Maya and asks for it may be trying to complete a sign-in as her. The fact that someone knows her name, account address, or even a recent code request does not establish that the person is legitimate. If a request is unexpected, Maya can pause and go directly to the service through an app or website she trusts…

More More Books

Cover of Dog Breeds for Real LifeDog Breeds for Real LifeAvailable nowCover of How to Find the Right Dog Breed for Your HouseholdHow to Find the Right Dog Breed for Your HouseholdAvailable nowCover of Digital Nomad Ideas for Accessible Remote WorkDigital Nomad Ideas for Accessible Remote WorkAvailable nowCover of The Bathhouse Keeper's Day OffThe Bathhouse Keeper's Day OffAvailable nowCover of A Hurricane Guide for CaregiversA Hurricane Guide for CaregiversAvailable nowThe Fountain Pen FamiliarComing soon

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.