keybase / keybase/keybase-issues
Signing a message via the website adds extra dashes in edge case
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I just signed a message via the website that contained a variation of the following:
```
-----BEGIN X509 CRL-----
00000000000000000000
00000000000000000000
00000000000000000000
00000000000000000000
-----END X509 CRL-----
```
After I signed the message, I saw this:
```
- -----BEGIN X509 CRL-----
00000000000000000000
00000000000000000000
00000000000000000000
00000000000000000000
- -----END X509 CRL-----
```
Notice the extra dash and space on the BEGIN / END line. That addition essentially breaks the format that OpenSSL is expecting. I didn't see any of these added anywhere else in the message.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the issue in the website's message-signing flow with the X509 CRL example shown in the report, then compare the signed output with the original delimiters. Done means the BEGIN and END lines retain their original dashes and spacing, so the resulting format remains acceptable to OpenSSL.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100