Commit Graph

19 Commits

Author SHA1 Message Date
55d4d23671
.well-known/nostr.json: add delta in case anyone looks for it 2023-03-07 22:17:09 +02:00
29c9625a35
.well-known/nostr.json: run through damus.io/key 2023-03-07 22:12:07 +02:00
f79964c5c8
.well-known: add nostr.json 2023-03-07 22:04:01 +02:00
24b9bfd69a
.well-known/security.txt: actually update the domain 2022-04-11 18:00:33 +03:00
9869b8a516
.well-known/security.txt: add comment mentioning OpenSSH signature 2022-04-11 17:58:08 +03:00
b5d69a2e07
.well-known: update security.txt, sign with SSH
TODO: Ask security.txt people how is signing with SSH supposed to be handled or are alternatives to OpenPGP OK?
2022-04-11 17:54:43 +03:00
6363d73460
update WKD again
I revoked mysurname and made it again with new calling name, so this
might have raised errors
2021-12-23 01:00:02 +02:00
9e51070a8c
WKD: update 69FF 455A 869F 9031 A691 E0F1 9939 2F62 BAE3 0723 2021-12-22 23:46:25 +02:00
74ecb5fcbe
WKD: add digitalents academy key 2021-11-12 12:37:50 +02:00
4f93fe8f4f
PGP&WKD: bumb key expiry 2021-06-24 16:49:14 +03:00
afaed41a09
0x99392F62BAE30723: add UID for surname at firstname dot info 2021-02-22 20:18:47 +02:00
e5ab378c39
mostly delist PrivacyTools & Pixelfed.dk 2020-04-19 16:59:50 +03:00
6a12678701
.well-known: add a security.txt
I guess there is no harm in adding it and I am hosting some services
that can be seen publicly while they may be password proteccted or
similar.

Ref: https://securitytxt.org/
2020-04-12 21:32:29 +03:00
1d0846a644
PGP/WKD: update key with the new authentication subkey 2020-02-18 16:59:34 +02:00
53d04a8f12
wkd: update with minimal keys
(tests also whether revoked keys are included)
2020-02-16 18:02:13 +02:00
b807a58005
update WKD keys 2019-12-06 20:59:10 +02:00
c44077a044
add two UIDs to 69FF 455A 869F 9031 A691 E0F1 9939 2F62 BAE3 0723 2019-12-01 20:52:10 +02:00
de3fa74926
PGP/WKD: move policy to the correct directory 2019-11-30 22:15:01 +02:00
e6eb02048b
enable GPG WKD 2019-11-30 22:07:29 +02:00