Thomas Voegtlin [ARCHIVE] on Nostr: ๐
Original date posted:2014-03-16 ๐ Original message:Thanks again for having a ...
๐
Original date posted:2014-03-16
๐ Original message:Thanks again for having a look.
Given these problems, I have decided to remove
the encryption methods from the current release.
I retagged 1.9.8 and updated the packages.
Thomas
Le 16/03/2014 15:39, Gregory Maxwell a รฉcrit :
> On Sun, Mar 16, 2014 at 7:31 AM, Thomas Voegtlin <thomasv1 at gmx.de> wrote:
>> thanks for your feedback!
>>
>> I was not aware that that implementation was flawed.
>> I will see how I can fix that code and get back to you.
> It also leaks on the order of 7 bits of data about the message per
> message chunk. I'm also think it's likely that there are some
> messages which are just incorrectly decrypted. ... it's really
> screwy and suspect.
Published at
2023-06-07 15:15:48Event JSON
{
"id": "1c1e7fa6f1594391be173cf18d800df0ad49dd9863b0461f1ba10fffb0039214",
"pubkey": "7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05",
"created_at": 1686150948,
"kind": 1,
"tags": [
[
"e",
"af00beff456b08069ca61bc26e24a501ff89f447fc579a1aa96fc66edda13389",
"",
"root"
],
[
"e",
"170afe9bbe1030908192b94b2185f0d175db7867caaa3cbee1428f7afa764e25",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "๐
Original date posted:2014-03-16\n๐ Original message:Thanks again for having a look.\n\nGiven these problems, I have decided to remove\nthe encryption methods from the current release.\nI retagged 1.9.8 and updated the packages.\n\nThomas\n\n\n\nLe 16/03/2014 15:39, Gregory Maxwell a รฉcrit :\n\u003e On Sun, Mar 16, 2014 at 7:31 AM, Thomas Voegtlin \u003cthomasv1 at gmx.de\u003e wrote:\n\u003e\u003e thanks for your feedback!\n\u003e\u003e\n\u003e\u003e I was not aware that that implementation was flawed.\n\u003e\u003e I will see how I can fix that code and get back to you.\n\u003e It also leaks on the order of 7 bits of data about the message per\n\u003e message chunk. I'm also think it's likely that there are some\n\u003e messages which are just incorrectly decrypted. ... it's really\n\u003e screwy and suspect.",
"sig": "858d9f75914f9a9da95ee7c9771a07287c799a873e9f530913c807381f736322e6e4f1c114222713075e101bc49159a616e8cd217fec95b0ba993b16aa75e4fa"
}