arjenstens on Nostr: In the current implementation the proxy is 100% a man-in-the-middle. That's why i'm ...
In the current implementation the proxy is 100% a man-in-the-middle. That's why i'm putting in effort to get pubkey addressing in because that allows us to encrypt traffic to that pubkey. That will require some kind of handshake which i haven't gotten to yet. I think we can even ditch domain names + SSL certificates when that is implemented.
Then a proxy will only know the source ip + what the next hop is, but not the contents.
Published at
2024-11-20 17:10:11Event JSON
{
"id": "572b065e3f87f55c9c77c7f8ac76fe031708b2136e06e6a4fc3057c2d4575c09",
"pubkey": "bbb5dda0e15567979f0543407bdc2033d6f0bbb30f72512a981cfdb2f09e2747",
"created_at": 1732122611,
"kind": 1,
"tags": [
[
"e",
"facd3c989ddd9a10990a30714166f36944030792a586e4891b6bac11e5d68308",
"",
"root"
],
[
"p",
"bbb5dda0e15567979f0543407bdc2033d6f0bbb30f72512a981cfdb2f09e2747"
],
[
"p",
"a372829d236a92cfe48008845daacf63ab87bd3f09dea86e4f13e9b89275ce5b"
]
],
"content": "In the current implementation the proxy is 100% a man-in-the-middle. That's why i'm putting in effort to get pubkey addressing in because that allows us to encrypt traffic to that pubkey. That will require some kind of handshake which i haven't gotten to yet. I think we can even ditch domain names + SSL certificates when that is implemented.\n\nThen a proxy will only know the source ip + what the next hop is, but not the contents. ",
"sig": "1a39e62a289ab5448dd7dd6cdf44440bc5dae8e14c2abf24e284caf0febcf66bddf7be8c8619d94b4ec1a39cd12e9ba642f4e8b574ec8765647997606d949ed8"
}
