Re: [BUG][FIX] Re: NEWSCARD * Publish and fetch permanent named records via Network News

Byrl Raze Buckbriar wrote:
> 
> The git repo now has a bug fix commit:
> https://codeberg.org/OCTADE/newscard.

Thanks!

> > Secondly, I have to use for each posting a different password, which
> > I do not want to do.
> 
> This is mandatory, and is the entire point of the scheme. It is a unique, NAMED record. You publish the record with the unique key. Then anyone else you reveal the key to can pull the record. If you use a large, random key, the record cannot be decrypted by anyone without that knowledge. If you reveal the key, anyone can fetch and decrypt the record.
> 
> I initially conceived the scheme as a way of having a large signature without including it in news articles. Instead the signature line would have just the newscard key. Then anyone could pull it and see the encrypted file decoded to plaintext. As an example, try to pull newscard 'octade'.
> 
> The key or passphrase is run through a chain hash stream to generate the message-id That will be used in the NNTP article, which is how the record is retrieved. Every NNTP server I have ever tested honors this convention. I have zombie code placeholders for the eventuality of that yowie. Then I will implement a check to ensure the NNTP server has stored the article with the given message-id.

Ok. I can fix this by using my nora program, which generates deterministic
nonces, which can be used as passwords, so that Alice and Bob can generate
for each day a lot of them and they don't need to exchange them, while
using a share secret.

https://github.com/706f6c6c7578/nora

Regards
Stefan

-- 
Onion Courier Home Server Mon-Fri 15:00-21:00 UTC Sat-Sun 11:00-21:00 UTC
ohpmsq5ypuw5nagt2jidfyq72jvgw3fdvq37txhnm5rfbhwuosftzuyd.onion:8080 inbox
 age1yubikey1qv5z678j0apqhd4ng7p22g4da8vxy3q5uvthg6su76yj0y8v7wp5kvhstum