The Librem 14 has great battery life and in this post we put it through its paces from low-power idle tests all the way to a torture test that pegs all 12 threads at 100%. Check out this post and video for all of our tests and results: https://puri.sm/posts/librem-14-runtime-and-charging/
Ran into some trouble with my initial Qubes install on the Librem 14, as apparently changing any options in the disk partitioning unchecks the encryption box and renders it uncheckable. This is clearly a Qubes problem, and not a Purism problem, but it led me down a fun path of reinstalling a dozen times or so. That said, now I’m very well acquainted with PureBoot, my TPM, and my Librem Key.
I’ll work on A Rust Site Engine a bit on the Librem 14 today and see how I like it for Rust development.
Got my hands on my @purism Librem 14 shortly after I got back to the US. Then I went out for tacos while Qubes downloads. Internet here is so slow. And expensive.
And thus begins my month long vacation. Not bringing either laptops with me. If it breaks my team will have to fix it without me, though I left ample documentation behind. Since I’m pretty sure my AD password expires during my vacation I went ahead and changed it to kick that can down the bad password policy road another 90d.
Looking forward to just chilling for a month. Practicing my violin again. Tacos.
In honor of #WorldPasswordDay2021 here's my favorite talk I've given on password policy: Sex, Secret and God: A Brief History of Bad Passwords in a 10-minute Ignite-style talk: https://opensource.com/article/18/5/brief-history-bad-passwords and the full-length talk I gave at BSidesLV 2017: https://infocondb.org/con/security-bsides/bsideslv-2017/sex-secret-and-god-a-brief-history-of-bad-passwords
Last week I figured out how to use the Nitrokey HSM2 for some critical tasks in my team from my Qubes system, and this week I figured out how to accomplish the same from my corporate laptop using PowerShell and git bash.
Today, I will try to hammer out some #Rust to remove the dependency on git bash.
Question for the system programming folks: I have a program that needs to subprocess some tasks to OS built-ins, and would like to have tests validating they work. So far I’ve only managed to take the function in question out and run it stand-alone in a ephemeral VM. Not the most easily automated task unfortunately. I’ve considered perhaps a test harness leveraging a tempdir and chroot, but I’m not sure how sane (or insane) that approach might be. Any suggestions on how to proceed?
2/2 - As a brown man from a state with legendary levels of racist hypocrisy, I understand the response and reaction of the other man. The attendant however appeared to be upholding the standards posted in several languages. In any event, I offered an apology of my own for creating a situation where even the appearance of racial discrimination was possible. This was met with a threat of violence so I broke contact. Battle drill 3 saves the day again, >13 years after my last day of combat...
Just had an interesting experience as one of two individuals exhibiting similar behavior in a public space. I was not corrected - my lack of a face covering was for the ongoing act of drinking water. Another man was approached by the station attendant and told to put a mask on while recording some kind of media on his phone. His response was to loudly insist the same standard be applied to everyone, the implication being racism was why he was asked and I was not. 1/2
Any @purism Librem 14 owners have a USB-C dock recommendation?
I like to work with my hands. That may mean hammering out solutions to complex problems in #Python or #Rust, building things in my shop, or spinning yarn to knit something warm. You’ll likely see some of all of that here. By day (and sometimes night) I keep >13k nodes and services alive in the Electric Vehicle sector.
PGP: FCBF 31FD B34C 8555 027A D1AF 0AD2 E852 9F5D 85E1