📅 Original date posted:2015-02-23
📝 Original message:On 02/23/2015 11:58 AM, Mike Hearn wrote:
> You're right that just sending the session key is simpler. I
> originally suggested doing ECDHE to set up an encrypted channel
> for the following reasons: [...]
I read from your answer that even if we use ECDHE, we can't use it for
every situation. So in any case we need the simple bootstrap via a
session key parameter. My suggestion is defer ECDHE for now but keep it
in mind. We can add it later I think.
> These discussions keep coming up. I think the next step is for someone
> to upgrade Andreas' wallet to support encrypted connections and the
> TBIPs, to see what happens.
I happily step up and do the implementation work on the app side. A
first step could be:
- If there is an "s" parameter present wrap the Bluetooth connections
with AES. Sounds good?
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:31:06
in reply to nevent1q…x6f3
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:31:06Event JSON
{
"id": "c78e2c386d8f4529bd11dd8dfdbed9b01ae97ecbbbef45f7b6c45b530bb2163e",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686151866,
"kind": 1,
"tags": [
[
"e",
"dfefe04b212481eb3fe073238ab7d32774988526d8b8bf7f8fff0d7249ebe09f",
"",
"root"
],
[
"e",
"bcfa9cd937575e169cd53e0f7e95522b01875548a10b990854e9247542534b20",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2015-02-23\n📝 Original message:On 02/23/2015 11:58 AM, Mike Hearn wrote:\n\n\u003e You're right that just sending the session key is simpler. I\n\u003e originally suggested doing ECDHE to set up an encrypted channel\n\u003e for the following reasons: [...]\n\nI read from your answer that even if we use ECDHE, we can't use it for\nevery situation. So in any case we need the simple bootstrap via a\nsession key parameter. My suggestion is defer ECDHE for now but keep it\nin mind. We can add it later I think.\n\n\u003e These discussions keep coming up. I think the next step is for someone\n\u003e to upgrade Andreas' wallet to support encrypted connections and the\n\u003e TBIPs, to see what happens.\n\nI happily step up and do the implementation work on the app side. A\nfirst step could be:\n\n- If there is an \"s\" parameter present wrap the Bluetooth connections\nwith AES. Sounds good?",
"sig": "e7808749c7c270991e7cc4c4718e04232e01960d5b9e499eb996809404035d22dc2002830152002ec58927080b4c78a497915a524809e13c6cc2e5b1a773a447"
}