keybase / keybase/keybase-issues
Suggest in the documentation to limit subkey to 2048 for the web interface.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I think the documentation should suggest to limit signing subkey to 2048 when they are stored on the server. I tried with a 4096... It take too long.
-----BEGIN PGP SIGNATURE-----
Version: Keybase OpenPGP v1.1.3
Comment: https://keybase.io/crypto
wsBcBAABCgAGBQJUVp5UAAoJEEFssX1w8RVPf70H/2mIE5NYQ2KGaaayGVzzdhga
+wvM00JJVybFmmrFB60s+E/RwksD9j5wOH/R7mJfF/XGubYqMMSgnHDJjmxWS6hy
QJu9Ylbpkyu3reePjXbM5buK9viEOnLHbQ9figwVKo0g3PRVtVys8u9tdNTgUEfp
annleaI2Mx9gn7TvmOlEHnxdW70pi93cfvfeNPjofg/MS7vdlYlWWviokjwdCMuT
NpNJN4Phqm3Ewf2ljAWYSS5pfjP57O3+KCdxzTCAdMg/p5xrEc1RAEZLNFa9yHsZ
sGKxULGTTcO9UA5iZ4NiI8N9cUGucqmJlidrJ29WPKl6TkpgAuepcrjw8CIQ8o4=
=NvtY
-----END PGP SIGNATURE-----
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the documentation for signing subkeys stored on the server and the web interface guidance. Check how key sizes are currently described, then add a recommendation to limit the signing subkey to 2048 where appropriate. Done means the relevant documentation clearly includes this recommendation and its motivation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100