Dino: Dino 0.3 Release
Dino is a secure and privacy-friendly messaging application. It uses the XMPP (Jabber) protocol for decentralized communication. We aim to provide an intuitive, clean and modern user interface.

Image

Image

The 0.3 release is all about calls. Dino now supports calls between two or more people!

Calls are end-to-end encrypted and use a direct connection between … ⌘ Read more

It’s the (roughly) bi-annual platform convention. I think the new platform does a good job of holding to progressive values (even if I wish it went farther in places). I got an amendment in to improve our stance on encryption-related issues, which was nice.

@lyse@lyse.isobeef.org there was an old tool for encrypted volumes that you could use random files as the unlock keys. And you could havemultiple hidden volumes that would unlock depending on the files supplied

@fastidious@arrakis.netbros.com Yeah.. mine is all server side.. so it doesn’t make much sense to be encrypt/decrypting anything. :D

@prologic@twtxt.net
BEGIN SALTPACK ENCRYPTED MESSAGE. kiNJamlTJ29ZvW4 RHAOg9hm6h0OwKt iMGN9pY3oc5peJE UcRA8ysyQ7e8co9 shMfScCFgmQgU5Q 6w6XD2FT6szO1i1 N8qWqFRwJcHliqp hlaSvsTNhuwe1Fs KESywjL8ZvxNeyb ro0RVcRIip4Itpv NKvFZ822RoDR6pb hVvSqgubr3IanFT 6VAGQe2mYvErE7i G0O284HNvj0tcbC qzY0uB3ZFePu2fp l8nHOeEm9QLkH4Y PNKY2bXjqtblDGq 7pNiNHXtNJDjrpG nUoEXK9CaB6DGe7 oaF1P9sTz7fFrUo qwIgzw4Z1yqULQW 6dcFgsGwQEMc6bV mXuJHkrDWbfw35o 2Lpevp4PAVw884t 5Jf4cDLAe3QfRjG 4y6uwJg8BwIr2Lb 2pCX23ffwJ0yjGs Ptyzuaq2Alfl3QX AcMNGFzTNHjHfqY cvsoTrSMbyE3ssS A0k0zeRJQLoGOK4 DGkdltMXaQyXq9d zzbueCXCsIM1vYG vcy85vKuqM0ikoG caUNUuIVCc6FMs5 2JtadCtbVKyG8Wx Z4R672Fd71eDjCc lEtCdJlEAmEJePw ThkxVJutJt2R2Ce lKp9tEKmrx1jMWW V8hJNTaQGAfFDEB Unh8YasaV24NqAi GKSnstFWk3DYCxC lvws9js2jJ9OKeq 2mMgFmzEmCr99RW 2CrxZStPpB1iEDU d0Un7W7bnyo2KpV xqe8rCeHA6CUwVs 0XMmxPvU1Q0wp9A 0Jwxo5CY9QF5EJl yVwaXiVP2CKw2aH tqEE5yTp9OmpNF0 jFqgr8vHOjosPyL c3nke0S9QFjAxjt Dr6xwYpnASDr1l1 N96G3FB5iVYLFaz FkXGm7oQNTaDY8e OtHXQiXRhQY3PCi VIYYVhc9RExVnfX fvzgfgc5uSxUynD sPp4eq2rJXkX5. END SALTPACK ENCRYPTED MESSAGE.

Let’s see how resilient this is, or if it breaks.

Sometimes I am a perfectionist. Having previously made my private diary blog available via a Tailscale sidecar container in my Tailnet, I have now integrated Tailscale directly into GoBlog. Both Tailscale and Tailscale’s Let’s Encrypt certificates can be configured directly in GoBlog. No sidecar container is needed anymore. A much simpler solution! (And Tailscale rocks!) ⌘ Read more

How to Generate the Free Let’s Encrypt SSL Certificate on Your Own (Windows) Computer ⌘ Read more…

https://wiki.archlinux.org/index.php/Dm-crypt/Swap_encryption cryptsetup swap

https://we.riseup.net/debian/encrypted-swap crypt debian devuan swap

https://techblog.jeppson.org/2017/04/centos7-nginx-reverse-proxy-lets-encrypt/ centos nginx

@felixp7@twtxt.net “Yo, crypto-heads. Encrypted communication doesn’t protect your privacy. Laws …” I guess crypto-heads are often happy with acknowledging this, but also arguing that e.g. deniable crypto is a useful way out here (and, of course, just doing illegal stuff if it gets really rough).

Kaidan: Kaidan will receive a grant for end-to-end encryption ⌘ Read more…

@prologic@twtxt.net

-----BEGIN CRYPTUTIL ENCRYPTED MESSAGE-----
l0GwFAQpx3ed+bZlcQ+pexbynFzZOm8EI/FivGbWQ16whyTkToVv8S2GSAjrsJoT
37MdaBDpoitli/f/aP130b6O6SnK/LdHHJ1DTvWgxB14sq9b4mRtk7HvYzA=
-----END CRYPTUTIL ENCRYPTED MESSAGE-----

@prologic@twtxt.net Ok.. so using NaCL boxes. yeah its just a combo of using secretbox with a generated key/nonce. and then using the pubkey box to encrypt the key/nonce for each device.

@prologic@twtxt.net sender generates an AES key encrypts message. gets the device list for user and encrypts key for each device. sends the encryptedkeys+cypertext.

@prologic@twtxt.net for encryption. we can have browser/app generate ec25519 keypair. store the private on device and add pub to list of devices for the user on pod.

Snikket: Sponsoring Group Chat Encryption in Siskin ⌘ https://snikket.org/blog/sponsoring-group-omemo-in-siskin/

Opportunistic Encryption on the IP Layer ⌘ https://hack.org/mc/blog/ipsec-dns.html

Cryptee | Private, Secure, Encrypted Photos and Encrypted Documents ⌘ https://crypt.ee/

@lucidiot@tilde.town @kas@enotty.dk There’s also Keybase as good GPG tool. They offer a lot of encrypted services as well :)

Even though noone send me GPG encrypted messages, I renewed my expiration date to one more year :)

@freemor@freemor.homelinux.net I also always try to have a few ssh servers with several ports available for me to use. My favorite port is 443. Once had a firewall that wouldn’t allow SSH on 22 but 443 was acceptable because it expected encryption on it.

Alex Schroeder: 2018-01-10 Encrypted Gopher https://alexschroeder.ch/wiki/2018-01-10_Encrypted_Gopher

How to keep your ISP’s nose out of your browser history with encrypted DNS | Ars Technica https://arstechnica.com/information-technology/2018/04/how-to-keep-your-isps-nose-out-of-your-browser-history-with-encrypted-dns/

@freemor@freemor.homelinux.net I think we already discussed encrypted tweets some time ago, but no encryption seemed short enough. GPG ist just too big. Any ideas?

You Can Encrypt Your Face – The New Inquiry https://thenewinquiry.com/you-can-encrypt-your-face/

@kas@enotty.dk Is #starttls-everywhere just to ease configuration or is there any reason why #lets-encrypt certs won’t work on mail servers?

@kas@enotty.dk That’s what i’m using. But shouldn’t i be able to generate keys to communicate with other users? How could i encrypt a message for you?

Wow, a third of all ssl certificates on twtxt are from Let’s Encrypt. Incredible.