tahoe-lafs/trac-2024-07-25

Clean up code terminology: "SSK" vs "slot", etc #306

New issue

Open

opened 2008-02-08 03:29:39 +00:00 by warner · 2 comments

warner commented

2008-02-08 03:29:39 +00:00

Owner

split out from #207:

code terminology: share vs slot vs container, "SSK" vs mutable file vs slot. We need to nail down the meanings of some of these and clean up the code to match. Zooko thinks that the name "SSK" -- "Sub-Space Key" -- is not directly applicable to our mutable file URIs.

Some of these terms are embedded in hash tags, and may be difficult to change. It may be easiest to change them when we switch to DSA keys (#217).

split out from #207: code terminology: share vs slot vs container, "SSK" vs mutable file vs slot. We need to nail down the meanings of some of these and clean up the code to match. Zooko thinks that the name "SSK" -- "Sub-Space Key" -- is not directly applicable to our mutable file URIs. Some of these terms are embedded in hash tags, and may be difficult to change. It may be easiest to change them when we switch to DSA keys (#217).

tahoe-lafs added the

labels 2008-02-08 03:29:39 +00:00

tahoe-lafs added this to the eventually milestone 2008-02-08 03:29:39 +00:00

tahoe-lafs added

and removed

labels 2008-04-24 23:44:42 +00:00

tahoe-lafs modified the milestone from eventually to undecided

2008-06-01 20:57:31 +00:00

davidsarah commented

2009-10-28 03:30:42 +00:00

Author

Owner

Tagging issues relevant to new cap protocol design.

Tagging issues relevant to new cap protocol design.

davidsarah commented

2009-11-03 00:33:53 +00:00

Author

Owner

The immutable terminology needs clearing up as well. For example, CHKs are not really content-hash-keys: Tahoe uses "CHK" to refer to caps for both convergent and non-convergent immutable files (and directories when #607 is done); also, convergent encryption uses a secret to avoid guessing attacks, which is sufficiently different from Freenet CHKs that it should be called something else.

The immutable terminology needs clearing up as well. For example, CHKs are not really content-hash-keys: Tahoe uses "CHK" to refer to caps for both convergent and non-convergent immutable files (and directories when #607 is done); also, convergent encryption uses a secret to avoid guessing attacks, which is sufficiently different from Freenet CHKs that it should be called something else.

tahoe-lafs added

and removed

labels 2009-11-03 00:33:53 +00:00

tahoe-lafs changed title from ~~clean up mutable-file code terminology: "SSK" vs "slot", etc~~ to Clean up code terminology: "SSK" vs "slot", etc

2009-11-03 00:33:53 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#306

No description provided.