Updated the expiration date:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFnwjvgBEAC+8AKn/9nO+Vcw5aS1z2UPqKTR+jT4uT4jJgu/hmbyOwdLZIRO fZXtp28DRp0l0aDmFijdq756xk3MylTtT5FjaKSssa8wYziBkIHdG1COG2Tb14MN lONc6jEf0DQlDPjwHvoTWcNmSnbKDL8rdNX24GxVYFEhzx/dOyUdhOLQEW2mgLY9
Updated the expiration date:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFnwjvgBEAC+8AKn/9nO+Vcw5aS1z2UPqKTR+jT4uT4jJgu/hmbyOwdLZIRO
fZXtp28DRp0l0aDmFijdq756xk3MylTtT5FjaKSssa8wYziBkIHdG1COG2Tb14MN
lONc6jEf0DQlDPjwHvoTWcNmSnbKDL8rdNX24GxVYFEhzx/dOyUdhOLQEW2mgLY9
Seemed to go well,
H:\DOWNLOADS\OpenXP\FILES>gpg --import wvv.asc
gpg: key 3BB37DA84A97932B: 7 signatures not checked due to missing keys gpg: key 3BB37DA84A97932B: "Wilfred van Velzen <w*******@gmail.com>"
3 new signatures
gpg: Total number processed: 1
gpg: new signatures: 3
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 3 signed: 2 trust: 0-, 0q, 0n, 0m, 0f, 3u
gpg: depth: 1 valid: 2 signed: 0 trust: 2-, 0q, 0n, 0m, 0f, 0u
Are you going to sign my key? ;-)
Btw:
pub 2048R/0A245A40 2020-01-04 [expired: 2021-01-03]
uid [ expired] August Abolins <a*****@****co.ca>
Is this one supposed to be expired?
(Your other key is ok: pub 2048R/5789589B 2020-01-02 [expires: 2024-12-31])
Are you going to sign my key? ;-)
How can I be sure that I'm conversing with the real WvV?
Btw:
pub 2048R/0A245A40 2020-01-04 [expired: 2021-01-03]
uid [ expired] August Abolins <a*****@****co.ca>
Is this one supposed to be expired?
Looks like it. Hmm.. I guess I need to do some housekeeping
myself. I've never played with the expiry/extension feature.
Maybe I could!
Looks like it. Hmm.. I guess I need to do some housekeeping
myself. I've never played with the expiry/extension feature.
Maybe I could!
It's fairly easy
key 0
expireNeed the secret key to do this.
Looks like it. Hmm.. I guess I need to do some housekeeping
myself. I've never played with the expiry/extension feature.
Maybe I could!
It's fairly easy
Looks like I'm in trouble, or the gpg system is broken:
H:\gpg --edit-key E2561F8AFCCE1B68C6A94ACE499B276C0A245A4
0
gpg (GnuPG) 2.2.19; Copyright (C) 2019 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa2048/499B276C0A245A40
created: 2020-01-04 expired: 2021-01-03 usage: SC
trust: unknown validity: expired
sub rsa2048/429056BDC7E74799
created: 2020-01-04 expired: 2021-01-03 usage: E
[ expired] (1). August Abolins <august@kolico.ca>
key 0
pub rsa2048/499B276C0A245A40
created: 2020-01-04 expired: 2021-01-03 usage: SC
trust: unknown validity: expired
sub rsa2048/429056BDC7E74799
created: 2020-01-04 expired: 2021-01-03 usage: E
[ expired] (1). August Abolins <august@kolico.ca>
expireNeed the secret key to do this.
expire
Need the secret key to do this.
You don't have the secret key? Maybe it's on another system?
expire
Need the secret key to do this.
You don't have the secret key? Maybe it's on another system?
That is happening on the system where I first installed gpg. I
don't understand why it can't find what it needs.
The same problem is happening on another pc were have most
certainly installed my pvt/pub pairs there too.
The same problem is happening on another pc were have most
certainly installed my pvt/pub pairs there too.
Strange... Look for your secring.gpg file...
gpg --list-secret-keysC:/Documents and Settings/User/Application Data/gnupg/pubring.kbx -----------------------------------------------------------------
When I invoke secret keys..
gpg --list-secret-keysC:/Documents and Settings/User/Application Data/gnupg/pubring.kbx -----------------------------------------------------------------
..why does it just produce the public "pubring" result?
So, I really don't know what to look for, except that I learned
the missing secret key was residing on another (and remote) pc.
I updated the expired key there, and will just copy it over to
my other systems. Later, I'll look to see if I can export the
pvt part of it.
Just use:
# gpg --export-secret-keys --armor
-----BEGIN PGP PRIVATE KEY BLOCK-----
...
And import the result on your other machine(s).
Just use:
# gpg --export-secret-keys --armor
-----BEGIN PGP PRIVATE KEY BLOCK-----
...
And import the result on your other machine(s).
Cool. Worked rather well. I remoted in to the source pc (with
the valid secret key that I need) and transferred the resultant
-o file.
Updated the expiration date:
Hi All,
On 2022-12-28 13:23:27, I wrote to you:
Updated the expiration date:
It expired again, so here's the update:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFnwjvgBEAC+8AKn/9nO+Vcw5aS1z2UPqKTR+jT4uT4jJgu/hmbyOwdLZIRO fZXtp28DRp0l0aDmFijdq756xk3MylTtT5FjaKSssa8wYziBkIHdG1COG2Tb14MN
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFnwjvgBEAC+8AKn/9nO+Vcw5aS1z2UPqKTR+jT4uT4jJgu/hmbyOwdLZIRO
fZXtp28DRp0l0aDmFijdq756xk3MylTtT5FjaKSssa8wYziBkIHdG1COG2Tb14MN
[...]
Looks like something worked:
H:\DOWNLOADS\OpenXP\FILES>gpg --import wvv.asc
gpg: key 3BB37DA84A97932B: 7 signatures not checked due to missing keys gpg: key 3BB37DA84A97932B: "Wilfred van Velzen <*gmail.com>" 3
new
signa tures
gpg: Total number processed: 1
gpg: new signatures: 3
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 4 signed: 3 trust: 0-, 0q, 0n, 0m, 0f, 4u
gpg: depth: 1 valid: 3 signed: 0 trust: 3-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2024-12-31
H:\DOWNLOADS\OpenXP\FILES>gpg --list-keys wilfred
pub rsa4096 2017-10-25 [SC] [expires: 2026-01-11]
D50ECD4F514B75DC0A064F893BB37DA84A97932B
uid [ unknown] Wilfred van Velzen <*@gmail.com>
uid [ unknown] Wilfred van Velzen <*>
uid [ unknown] [jpeg image of size 5943]
sub rsa4096 2017-10-25 [E]
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 606 |
Nodes: | 10 (1 / 9) |
Uptime: | 17:13:44 |
Calls: | 9,658 |
Calls today: | 6 |
Files: | 16,074 |
Messages: | 1,065,700 |
Posted today: | 4 |