It's National Library Week. We still care about your privacy at the library. The Library Freedom Project has a great set of resources to help you do things like:

- strip AI from your Gmail
- avoid digital scams
- understand Big Data
- reduce harm from doxxing
- using Signal as safely as possible

They're written in plain English and try to help you do things better acknowledging that there's no such thing as perfect privacy.

https://libraryfreedom.org/resources/

Product Warning: do *not* buy #ebikes with #bosch motors/controllers. they are locked-down by some #evil #proprietary shit and try to #vendorlockin you into their shitty products. the motors are good, but the apps, the navigation, are horrible, and #interoperability with devices and apps of other vendors is actively hindered.

learn from my mistake, don't repeat it.

pls discuss products/vendors that are open and interoperable in comments below.

I reported an insecure DKIM key to Deutsche Telekom / T-Systems. They first asked me to further explain things (not sure why 'Here's your DKIM private key' needs more explanation, but whatever...). Then they told me it's out of scope for their bugbounty.

I guess then there's really no reason not to tell you: They have a 384 bit RSA DKIM key configured at: dkim._domainkey.t-systems.nl

384 bit RSA is... how shall I put it? I think 512 bit is the lowest RSA key size that was ever really used. 384 bit RSA is crackable in a few hours on a modern PC (using cado-nfs). The private key is:
-----BEGIN RSA PRIVATE KEY-----
MIHxAgEAAjEAtTliQYV2Xvx1OGkDyOL799BTFEuobY2dn2AgtiKCQgrh78NVK1JK
j0yRXgNnPpGBAgMBAAECMF0t+TBZUCi8xATSMij7VLTxv5Xi5OIXesNiXOKtYIRP
LkpYfR5PggaMScfbmqSssQIZAMwOhm9d7Y7Qi7I2j1AlYbiqdtqO54T7FQIZAONa
9dJFkC6lM3EPXR+0SZ4dqwwpiM0nvQIYYgz8thi5JK264ohq9sTvnu9yKvUN9I09
AhgfgMYZKcxtujRjkSZtMzUUNLYzzDmJe90CGDKwqcBI0v9ChaR8WHht+/chMdxj
7ez94w==
-----END RSA PRIVATE KEY-----