Brooooooklyn / Brooooooklyn/keyring-node

Generic failure - Attribute 'password encoded as UTF-16' is longer than platform limit of 2560 chars

Open
#99 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
100
Forks
8
Avg merge
20h 41m
Merged PRs (30d)
4

Description

Hello, i have a weird bug that i cant make sense out of it, hoping you could help me clear it out.

I am saving a jwt access token that is around 1300 characters long, using the setPassword method. The token itself is simple utf-8 characters. But i always get the error that i am going over the limit of chars for my Windows platform.

I don't understand why key ring fails to save the password when its clearly less than the limit. Any help would be appreciated!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing setPassword on Windows with the reported 1300-character token and inspect the platform-specific password-length and UTF-16 handling. The issue is done when the cause of the 2560-character limit error is established and the behavior is corrected or clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, rust
Domain
backend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.