key-generator dones't work anymore #542
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#542
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Jan-Benedict Glaw noticed that the key-generator no longer works:
Looks like the .tac file is being created with an obsolete key-length
argument, which is being interpreted as a basedir.
Do we need it? If we don't, then let's remove it rather than leave it there, broken, so that its presence won't waste the time of people like Jan-Benedict.
Yes, we do. We don't have DSA keys yet, and we haven't done anything to speed
up RSA key generation for a long time. As best I can tell, the prodnet key
generator was using 10-20% of a core in september (before the number dropped
to zero, possible because it was somehow broken, or not started), which is
time that would have to be spent (blocking) in the webapi node if there were
no helper.
It would be nice to be able to provide a more objective argument. We don't
have any automated client-experience instrumentation: if we did, we could
turn the helper on and off and then watch how long a typical user must wait
to create a directory with and without it, and then say "to save each user an
average of 1.5 seconds per directory creation, it is worth having this code
in place, and fixing it". As it stands, I can only claim that it is likely to
save each user an average of 700ms (the SSK-creation time as measured by
http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_SSK_creation.html),
and therefore is worth having this code in place and fixing it.
Note that the prodnet key generator is still working because its .tac file
was created before this bug was introduced.
When we get DSA dirnodes, I'll be happy to rip out the key-generator.
Fixed, in changeset:71c62f8fcb823eb5.