Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decode error messages #606

Open
jaraco opened this issue Nov 11, 2022 · 1 comment
Open

Decode error messages #606

jaraco opened this issue Nov 11, 2022 · 1 comment
Labels
enhancement good-first-issue help wanted macOS

Comments

@jaraco
Copy link
Owner

jaraco commented Nov 11, 2022

Currently, the macOS Keyring backend hard-codes a few error codes to messages. Better would be to use the API to resolve error codes to human-readable message strings.

I started looking into how to do it. I imagine it goes something like:

>> api._sec.SecCopyErrorMessageString(-25244)
-1797030505

But probably something needs to translate that integer response into a CFString object and convert that object to a Python string.

Maybe someone would be interested in determining how to do that?
@abastola0
Copy link

Hi @jaraco. Can you please assign me to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement good-first-issue help wanted macOS
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jaraco @abastola0