Login Page - login with pubkey hex #144
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sigit/sigit.io#144
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Nostr login page allows us to login with pubkey hex value (not explicitly written in the label). The app proceeds but the npub shown for the profile after the login doesn't match the values seen in online converts (nostrcheck.me, https://nostrtool.com/)
Hex string is being treated as private key, see
If its confusing we can disable hex input.
Logging in with public key should definitely be disabled, there's no use case where we should allow anyone to attempt to see other people's sigits (it's impossible anyway)
After
nostr-login
package update #217, the private key login is now only available with?nsec=
search param for local development only (preferably with dummy accounts). We've kept the hex key form option as well.