User Details
- User Since
- Aug 28 2021, 11:57 AM (222 w, 1 d)
- Availability
- Available
Sun, Nov 23
git checkout gnupg-2.5.14, reverted the commits 46f4cb66125ee34e87e592cc02d38daead3427af and 0cc7759ed5a3890b4e28563a6b5e97f3aa551530, recompiled, and the error message gpg: keydb_search_first failed: SQL error no longer appeared. Also, in /root/.gnupg/public-keys.d/, the two files pubring.db.lock and .#lk0x0000... are present.
Fri, Nov 21
Additionally, in the /root/.gnupg/public-keys.d/ directory, the two files .#lk0x00007fdcb40043b0.b02bef684bbe.5108 and pubring.db.lock are missing.
Thu, Nov 20
gpg was compiled with the latest version of SQLite3 at the time as its own private library, without linking against the system's libsqlite3.so.
The sqlite3 CLI is the version that comes pre-installed with Ubuntu 22.04.5.
keyboxd (GnuPG) 2.5.13
listening on socket '/root/.gnupg/S.keyboxd' keyboxd (GnuPG) 2.5.13 started handler 0x7f2eba314640 for fd 9 started connection from process 4361 (0:0) (SQL: PRAGMA foreign_keys = ON) (SQL: CREATE TABLE IF NOT EXISTS config (name TEXT NOT NULL UNIQUE,value TEXT NOT NULL )) database version: 1 database created: 2025-11-20 06:11:12 (SQL: CREATE TABLE IF NOT EXISTS pubkey (ubid BLOB NOT NULL PRIMARY KEY,type INTEGER NOT NULL,ephemeral INTEGER NOT NULL DEFAULT 0,revoked INTEGER NOT NULL DEFAULT 0,keyblob BLOB NOT NULL)) (SQL: CREATE TABLE IF NOT EXISTS fingerprint (fpr BLOB NOT NULL PRIMARY KEY,kid BLOB NOT NULL,keygrip BLOB NOT NULL,subkey INTEGER NOT NULL,ubid BLOB NOT NULL REFERENCES pubkey)) (SQL: CREATE INDEX IF NOT EXISTS fingerprintidx0 on fingerprint (ubid)) (SQL: CREATE INDEX IF NOT EXISTS fingerprintidx1 on fingerprint (fpr)) (SQL: CREATE INDEX IF NOT EXISTS fingerprintidx2 on fingerprint (keygrip)) (SQL: CREATE TABLE IF NOT EXISTS userid (uid TEXT NOT NULL,addrspec TEXT,type INTEGER NOT NULL,uidno INTEGER NOT NULL,ubid BLOB NOT NULL REFERENCES pubkey)) (SQL: CREATE INDEX IF NOT EXISTS userididx0 on userid (ubid)) (SQL: CREATE INDEX IF NOT EXISTS userididx1 on userid (uid)) (SQL: CREATE INDEX IF NOT EXISTS userididx3 on userid (addrspec)) (SQL: CREATE TABLE IF NOT EXISTS issuer (sn TEXT NOT NULL,dn TEXT NOT NULL,ubid BLOB NOT NULL REFERENCES pubkey)) (SQL: CREATE INDEX IF NOT EXISTS issueridx1 on issuer (dn)) database '/root/.gnupg/public-keys.d/pubring.db' created (SQL: SELECT ubid, type, ephemeral, revoked, keyblob FROM pubkey as p WHERE p.type = 1 ORDER by ubid) (SQL: SELECT ubid, type, ephemeral, revoked, keyblob FROM pubkey as p WHERE p.type = 1 ORDER by ubid) command 'NEXT' failed: Not found handler 0x7f2eba314640 for fd 9 terminated
Sep 19 2025
Aug 28 2025
Hi
I have some questions about the "auto-key-upload: If an LDAP keyserver is configured (in dirmngr), upload a newly created key directly to that server" feature:
- If an LDAP keyserver is configured, will every newly created key be uploaded? Is this upload behavior enabled by default?
- Even with an LDAP keyserver configured, what if we don’t want to upload by default? If we prefer manual approval or want to upload only a specific subkey, how should we handle that?
- What about keys created for testing, temporary use, or personal privacy-sensitive purposes that we don’t want others to discover?
People who use GPG tend to care deeply about privacy and don’t want to upload or expose unnecessary information.
