Re: Change to forum software? (was TDE Matrix.org room?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Anno domini 2021 Fri, 8 Oct 20:20:45 -0500
 Michael scripsit:
> On Friday 08 October 2021 05:25:21 pm Edward wrote:
[...]
> AFAIK it should be possible to make one key pair and share both keys with the 
> whole list, just for use with this list.  Everyone sends on the public key 
> and everyone decodes on the private key.  Yes, it technically violates the 
> concept of key pairs, but we're just trying to keep the list’s content from 
> being easily [data collected] and [censored] by [automated data collecting] 
> mail providers(/entities).
> 
> I’m going to presume that any list encryption is pointless if someone installs 
> the key pair on anything except a local mail client.  E.g if someone installs 
> the key pair on their google web mail interface…  (I didn’t think of this 
> until later.)
> 
> That presumption is why I suggested a forum type of replacement for the user 
> lists.  I’m not that up on current ‘stuff’ so pretty much anything that 
> eliminates [automated data collecting] being easily tied to a particular 
> person and/or an entity being able to [censor] participation works for me.
> 
> I don’t think there is any sort of perfect solution (maybe a tor onion site, 
> but ugh, that wouldn’t be user friendly at all.).

The header is not encrypted, it's just the message body. So all metadata analysis is still possible with an encrypted mailinglist. If everybody uses kmail that's easy to fix with a filter - if you look at my filter that I posted some days ago: if the mail is encrypted and comes from e.g. "users-encrypted@xxxxxxxxxxxxxxxxxx", then replace it with the decrypted body. That body vcontains (violating the standard) the whole message including headers. On the sending side (mailinglist), just replace the header with a minimal version and random subject (e.g. date+timestamp).

Making a shared private/public keypair for the list is used the othe way round is no problem, as changing the private part will have no effect. It's also convenient, as all users can use the public key to send encrypted mail to the list. Again, kmail can handle this this transparent for the user.

Oh, anybody needs a tutorial?

Nik


> 
> Best,
> Michael
> 
> PS: I’m using [] around concepts, interchange with any type of ‘bad’ activity 
> you want.
> ____________________________________________________
> tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
> Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx



-- 
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx




[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux