GitHub

I Almost Hashed a Document Number That Needed to Be Read Again (opens in new tab)

Discussed on DEV

What building KYC verification taught me about the difference between encryption and hashing - and why getting that choice wrong would have broken the entire feature VaultPay is a wallet microservice I built on top of AuthShield. Previous parts: Part 1 is here: Part 2 is here: Part 3 is here: Part 4 is here: When I started designing KYC verification for VaultPay, my first instinct was to hash the document number before storing it. Hashing felt like the secure choice. It's what you do with pas...

Read the original article
Sign in to keep reading the full article.

Keyboard Shortcuts

Navigation

Next / previous post
j/k
Open post
oorEnter
Preview post
v

Post Actions

Love post
a
Like post
l
Dislike post
d
Undo reaction
u
Save / unsave
s

Recommendations

Add interest / feed
Enter
Not interested
x

Go to

Home
gh
Interests
gi
Feeds
gf
Likes
gl
History
gy
Changelog
gc
Settings
gs
Discover
gb
Search
/

General

Show this help
?
Submit feedback
!
Close modal / unfocus
Esc

Press ? anytime to show this help