Skip to content

docs(ed2k): say that aMule enables SUI by default - #208

Merged
got3nks merged 1 commit into
amule-org:mainfrom
got3nks:docs/sui-enabled-by-default
Sep 7, 2026
Merged

got3nks merged 1 commit into
amule-org:mainfrom
got3nks:docs/sui-enabled-by-default

Conversation

@got3nks

@got3nks got3nks commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Fixes the wording that prompted amule-org/amule#1308.

The page presented SUI as opt-in: the intro said it "can be enabled in Preferences → Security", and a closing Enabling SUI section walked the reader through switching it on. Neither said it is already on, so a reader reasonably concluded aMule ships with it off and asked for it to be made the default.

It has been the default since 2007. Cfg_Bool("/ExternalConnect/UseSecIdent", s_SecIdent, true) in src/Preferences.cpp, the Preferences checkbox is created ticked in src/muuli_wdr.cpp, and there is no build-time switch. Verified on a fresh profile with current master rather than from the code alone: an empty config directory gets UseSecIdent=1 in amule.conf, the log line No 'cryptkey.dat' file found, creating., and a 365-byte cryptkey.dat.

Two changes:

  • The intro now says aMule enables SUI by default and that the key is generated on first start.
  • Enabling SUI becomes Checking that SUI is active: the key file and the log line that announces it, and the Verified - OK identification line in the Client Details dialog. Plus the two things a user actually needs to know, neither of which the page said before - keep cryptkey.dat, because deleting it creates a new identity that no peer has credited, and turning the option off stops peers crediting your uploads.

The wording for the identification state is taken from the source (ClientRef.cpp renders Verified - OK / Failed / Not complete / Bad Guy) rather than from memory of the UI.

This page has no i18n/ mirrors yet, so only the English source changes and no translation files are touched.

The page read as if Secure User Identification were opt-in: the intro
said it "can be enabled in Preferences -> Security" and a closing
section walked the reader through switching it on. Neither mentioned
that it is already on, which led to amule-org/amule#1308 asking for it
to be made the default.

It has been the default since 2007: the preference is registered with a
true default and the Preferences checkbox is created ticked, so a fresh
profile writes UseSecIdent=1 and generates cryptkey.dat on first start.

Say that up front, and replace the enabling walkthrough with how to
check it is working (the key file and the log line that announces it,
the Verified - OK state in Client Details), plus the two things worth
knowing: keep cryptkey.dat, because losing it means losing the identity
peers credited, and turning the option off stops peers crediting your
uploads.
@got3nks
got3nks merged commit 4f12edc into amule-org:main Sep 7, 2026
2 checks passed
@got3nks
got3nks deleted the docs/sui-enabled-by-default branch September 7, 2026 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant