RE: RE: Security Incident @v4vapp: KeepSats Transfer via Authentication Flaw — Now Resolved
You are viewing a single comment's thread from:

RE: Security Incident @v4vapp: KeepSats Transfer via Authentication Flaw — Now Resolved

databaron(62)
Published in
Value 4 Value
Words
43
Reading
1 min
6d

Letting a refresh mint a token for any username while keeping active scope is a scary gap, so stopping it at 40,000 sats is a relief. Will refreshes now need a fresh signature, or a check that the username matches the original login?

leofinance
via leothreads
This post was published via leothreads. Ecency is not the originator or editor of this content and displays it for discovery purposes only.
3
@databaron: Letting a refresh | Ecency