nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0mwq9c623ujjzpql7r4fk090yxrf458sz2egzprw0zn0ca669q9q8tvdjy (nprofile…vdjy) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq335uzuwqaxw3gte9n2fdlzdxzz5xm7vatn89kztc3x4gs06ktjfsegpvj7 (nprofile…pvj7) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqxlqyczsy7e9ye3vqpw4cg05qtp5uy2y445wffyr3ynk5puylw9nqa97gap (nprofile…7gap) That 10+ year-old blog post and other page from the author have been widely cited in critiques of DNSSEC. While there may be much to criticize and dislike, the underlying message is probably weaker than you might imagine. Or at least, there have been a lot of reasonable criticisms of those criticisms.
Implementation and deployment experience of the challenges, strengths, weaknesses, and risks are usually more nuanced than what appears in most blog posts
John Kristoff
npub1dc…yuqsf
2024-11-17 01:53:15 UTC
in reply to nevent1q…4v8n
Author Public Key
npub1dchukf749tudw9rry3nwhpg7uddg8xqf0frkw9pwzaytcn5v7c7q8yuqsfSeen on
wss://relay.mostr.pubPublished at
2024-11-17 01:53:15 UTCEvent JSON
{
"id": "e632e9f74890e09fbabd8c4fde355a7d99f1cb14e7ebc2f64596f376cb1617c9",
"pubkey": "6e2fcb27d52af8d714632466eb851ee35a8398097a4767142e1748bc4e8cf63c",
"created_at": 1731808395,
"kind": 1,
"tags": [
[
"p",
"7edc02e34a8f2521041ff0ea9b3caf21869ad0f012b281046e78a6fc775a280a",
"wss://relay.mostr.pub"
],
[
"p",
"8c69c171c0e99d142f259a92df89a610a86df99d5cce5b097889aa883f565c93",
"wss://relay.mostr.pub"
],
[
"p",
"37c04c0a04f64a4cc5800bab843e805869c22895ad1c94907124ed40f09f7166",
"wss://relay.mostr.pub"
],
[
"p",
"f708981a134a11a6a01d17d326290dfaa34d81ede20ae06ad20166815f416933",
"wss://relay.mostr.pub"
],
[
"p",
"52deb52762d41320fa5a2fdcf7464b859b5044e02b2b71a96ed9be1f3a5d5cc7",
"wss://relay.mostr.pub"
],
[
"p",
"d56a806cb6467250472989a2e77d523b4c166d6a884eae9470edf84c4b2ae4ed",
"wss://relay.mostr.pub"
],
[
"e",
"893193c90d239fa31acc1ff4704d38a661f0f91b5568e4684b496dddee983ea7",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/jtk/statuses/113495795035914459",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq0mwq9c623ujjzpql7r4fk090yxrf458sz2egzprw0zn0ca669q9q8tvdjy nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq335uzuwqaxw3gte9n2fdlzdxzz5xm7vatn89kztc3x4gs06ktjfsegpvj7 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqxlqyczsy7e9ye3vqpw4cg05qtp5uy2y445wffyr3ynk5puylw9nqa97gap That 10+ year-old blog post and other page from the author have been widely cited in critiques of DNSSEC. While there may be much to criticize and dislike, the underlying message is probably weaker than you might imagine. Or at least, there have been a lot of reasonable criticisms of those criticisms. \n\nImplementation and deployment experience of the challenges, strengths, weaknesses, and risks are usually more nuanced than what appears in most blog posts",
"sig": "29bbf86374ea58e693c34b243787f8500a7b1dbae797ae2366eea28a288c522288f30aa529cc69b989ee26e8fbc4495ffe918047d802770eb67166247032304e"
}