Riccardo Spagni [ARCHIVE] on Nostr: 📅 Original date posted:2015-07-14 📝 Original message:Hi Mike, FYI there is a ...
📅 Original date posted:2015-07-14
📝 Original message:Hi Mike,
FYI there is a company called Netki is also working on a kind of DNSSEC
> integration with BIP70, there's a thread here about their efforts:
>
>
>
>
https://groups.google.com/forum/#!searchin/bitcoinj/dnssec/bitcoinj/QFAH1F2dEwE/36oWDwREEV4J>
> If you would like to work on this, perhaps it's worth teaming up with them?
> Obviously they plan to have an open spec and open source implementation.
>
Netki's solution is incredibly limited, it's a single return value and no
metadata (where OA encapsulates metadata in KV pairs). This does not lend
itself well to handling BIP70-style communication.
As an aside, they also seem to have a complete disregard for lookup
privacy, which we address in OpenAlias by means of DNSCrypt encrypted
lookups. To that end we have even written the first independent DNSCrypt
implementation (ie. over-and-above dnscrypt-proxy) which provides a full
Python implementation that uses libsodium / nacl if available, but falls
back to a 100% Python slownacl implementation:
https://github.com/openalias/dnscrypt-pythonRiccardo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150714/625dd0fb/attachment.html>
Published at
2023-06-07 15:42:09Event JSON
{
"id": "3a2da675110ddbd9a11538771f474654bff9c0cb6bf7271e3329978fb3937a63",
"pubkey": "fada22460acfa5561480a4bf88a43b3c166bb0cbbda01f3099de15f2290f26fa",
"created_at": 1686152529,
"kind": 1,
"tags": [
[
"e",
"2b792280c7c77e1a9146c50dbbc2a8f3336e57397d73b26f225d7fe35c48cd85",
"",
"root"
],
[
"e",
"21f648f338e38d160e0ccddcfacd7903c11302388e34d2b3c5cd7e925ec20091",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2015-07-14\n📝 Original message:Hi Mike,\n\nFYI there is a company called Netki is also working on a kind of DNSSEC\n\u003e integration with BIP70, there's a thread here about their efforts:\n\u003e\n\u003e\n\u003e\n\u003e https://groups.google.com/forum/#!searchin/bitcoinj/dnssec/bitcoinj/QFAH1F2dEwE/36oWDwREEV4J\n\u003e\n\u003e If you would like to work on this, perhaps it's worth teaming up with them?\n\u003e Obviously they plan to have an open spec and open source implementation.\n\u003e\n\nNetki's solution is incredibly limited, it's a single return value and no\nmetadata (where OA encapsulates metadata in KV pairs). This does not lend\nitself well to handling BIP70-style communication.\n\nAs an aside, they also seem to have a complete disregard for lookup\nprivacy, which we address in OpenAlias by means of DNSCrypt encrypted\nlookups. To that end we have even written the first independent DNSCrypt\nimplementation (ie. over-and-above dnscrypt-proxy) which provides a full\nPython implementation that uses libsodium / nacl if available, but falls\nback to a 100% Python slownacl implementation:\nhttps://github.com/openalias/dnscrypt-python\n\nRiccardo\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150714/625dd0fb/attachment.html\u003e",
"sig": "1b9a2e20b480d0e8a5dd70feed454975b1a7f9aaa951e81273cd7cb4de37fd51be2ecc43c2ad21eb7052dfab9815f870310af1060fffc610945047d75985cbc5"
}