"Of the 146.6 million individuals affected by the breach: 145.5 million had Social Security numbers exposed. 99 million had address information exposed. 27.3 million had gender information exposed. 20.3 million had phone numbers exposed. 17.6 million had driver's license numbers exposed. 1.8 million had email addresses exposed. 209,000 had credit card numbers exposed. 97,500 had Tax Identification numbers exposed. 27,000 had the state of their driver's license exposed."
I got an e-mail from Mozilla to put pressure on Amazon to say what they do with the data they collect from children.
How about educating parents as to why the original Dot is a bad idea, and why this is even worse. These children are defenseless in a #surveillance society without the help of their guardians---having every aspect of their being dissected and analyzed before they even know what is happening or that they should care. By the time they have grown and maybe _do_ care, it is already far too late; they are already compromised. Most of the things learned about children won't change into adulthood. And further, Amazon will help to shape what these children become based on how they interact with Alexa, whether they intend to or not.
When the cwd is a Git repository, rather than typing `git commit -m foo`, you'd just type `c -m foo`. `git commit --amend` would be `ca`. `git rebase --interactive` would be `Ri`. `git pull` and `git push` are `P` and `p` respectively. And so on. Simply typing `?` will list all of the commands. And tab-completion works as expected with all of these, as if you were using the long Git commands.
This helps my fingers keep up with my mind and makes CLI work with Git much more enjoyable. Hopefully others can enjoy it as well.
I don't have time to re-learn 3d modelling with Blender, so we just modified textures of existing dragons of one of the mods during the day (in #GIMP), which they had fun with. I did some hacking during the day, but I needed to do too much research, so it was hard to keep them engaged with a combination of Lua scripting and web browsing.
So they'll be excited in the morning. I added other small features they won't be expecting and learned (from code) some gameplay features we were unaware of. Maybe they'll get interested in hacking it themselves if I show them how easy it is to make certain tweaks, and if factor any new code I write in such a way as well.
@cwebber I'm really excited to hear how things go for you, my fellow guinea pi---er, hacker. I'm not switching laptops yet, but I certainly won't until I can be confident it runs GuixSD without critical issues.
Did you end up getting a USB-C dock? And how's the fan noise compared to the X200?
I'll rate-limit my questions to you to give you time to play around with it for a few weeks/months. :)
Mike Gerwitz (mikegerwitz@social.mikegerwitz.com)'s status on Tuesday, 17-Apr-2018 23:41:14 EDT
Mike GerwitzI have hosted my own mailserver (Dovecot, Postfix) for the past 15 years or so, but my mail has always been on a remote server that I also used as my webserver. That sucks because it makes it virtually impossible for me to audit who has accessed it (hopefully only me!). I also have my GNU mail merged with that mailbox using fetchmail on my remote webserver.
I've had my own local IMAP server (Dovecot) at home for some time and use offlineimap to keep them in sync, mostly for performance. So it was a pretty easy switch to install Postfix locally without a remote relay, enable POP3 on my remote mailserver, and use fetchmail on my local server to pull messages from my remote mailserver over POP3. I kept all bounce (redirect/reject) Sieve rules on the remote box and moved all other rules to my local box. I moved the GNU fetchmail config to my local box. Finally, I disabled IMAP on the remote mailserver and stopped offlineimap.
@cwebber I have seen symmetric ciphers with random, ephemeral keys used for producing pseudorandomness for wiping drives (and have done so myself)...perhaps this is just a lazy/familiar way of doing the same thing from the perspective of whoever authored that? openssl is often used instead.
dd with /dev/urandom is most often avoided not because it's a bad idea, but because it's relatively slow compared to e.g. using openssl for the aforementioned purpose.
Translation: "Everyone else does it too, so it's okay."
And trying to lead the user to believe that they really do need all of this stuff. Do they "need" it to provide those services? Perhaps. Do they "need" to provide these services to millions of people that don't want, have never asked for, or are completely unaware of them? I think not.
@randomdamage I agree. The nice thing about hardware switches is that almost anyone could open up their device and observe that there is a physical disconnect and rest assured that no software update or malware could ever change that---physical access to the device is needed.
Of course, that wouldn't prevent hardware issues from wear or defects. Maybe the hardware switch becomes a bit floppy over time and slides without physical force, or wears inside and shorts.
We'll need to only trust simple, clearly built switches that do nothing fancy or creative and are built out of quality materials.
@randomdamage This is why a hardware switch (like the Purism Librem 5) is ideal.
It's possible to measure whether or not a phone is attempting a connection (emitting radio waves), so someone can determine whether the phone is lying to do if you put it in e.g. airplane mode. Manufacturers have incentive to have airplane mode do what it claims to do since there are FAA regulations that customers have to adhere to when on certain flights. Another option is to place your phone in a bag that acts as a Faraday cage; I have one (though I haven't used it in some time).
This doesn't prevent malware, malicious OS's, or targeted attacks from modifying phone software, though. But for your average phone user concerned about privacy with a modest threat model, something like airplane mode may be good enough.
If your threat model is higher, you probably know what more you should be doing.