Production Engineer/SRE. #FOSS developer and advocate. Obsessive Metallica Fan. Biker. Metal head. #BLM. (Formerly "Facebook Phil")

San Francisco, CA
Joined April 2011
Gah, @PrimeVideo why does prime video skip to the next season of a show, every time I'm 5 episodes from the end of the last season. Not. Cool.
30
SugarJar 2.0.2 is out! `bclean` improvements, new `sync` cmd for keeping different workstations in sync, new cmds for remote branch cleanup & bugfixes. Available on rubygems. New pkgs already submitted to Fedora and Homebrew and other distros coming. github.com/jaymzh/sugarjar
1
26
oss-stats 0.0.1 released! I've released the very first version of oss-stats! It's actually been in use for months now, but it's now more ready for public consumption. Measure and report on the health of F/OSS projects! github.com/jaymzh/oss-stats
2
43
Hey @buildkite - Can public pipelines please be accessible via the API even if you're not a member of the org? They're public, and I don't want to scrape the webUI just to get build stats. That'd be super helpful to the F/OSS community. <3
1
1
83
It turns out that this works with GraphQL (but not REST), so there is a way! Thanks @keithpitt !
1
52
I'm really excited to finally have this revamped version of our annual diversity report published. Thanks to everyone who helped!
The Scale Divcersity team is pleased to publish an updated diversity report. socallinuxexpo.org/blog/scal…
1
36
For #VeteransDay...help us SHARE THIS positive veteran story. Inspired by a true story. By a US Army vet filmmaker. About vets. Starring vets 🫡 @RottenTomatoes @morgan_freeman
9
58
15
95
3,017
.@FedExHelp your system doesn't recognize the doortag number you left, but your phone automation won't transfer to a human without a valid one. WTF.
2
66
The SCALE 22X CFP closes at the end of the month! Don't forget to submit your proposal!
FLOSS fanatics, time is running out, this is your moment! SCaLE 22x is looking for presenters with passion. Submit your talk by Nov 1st and leave your mark on the open-source world: socallinuxexpo.org/scale/22x… #SCaLE22x
1
72
Phil Dibowitz retweeted
Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated. This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses. The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines". The 2024 version is 800-63-4. Here: pages.nist.gov/800-63-4/ The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org. The previous update was in2020. The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead: 1. After a breach/compromise 2. User request 2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords. This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this. Most frameworks, however, have moved away from arbitrary password resets and complexity rules. **We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them. Using complexity rules gets you the user psychology of: Password1 Password2 and so on Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies. I'm so excited for the new changes! Ok I'm off my soapbox. Share the love! Thank you!
183
1,762
202
5,416
646,734
Everyone should read this thread. Long but worth it. If you have children, extra make sure you get to the end.
You may have heard the term “Project 2025” floating around, and you may even have cracked open the 900+ page document yourself, only to see a lot of kind of bland, policy-wonk text. So let me crack through the policy-speak and tell you WTF is in this document.
99
Bonnie and I are celebrating our 73rd anniversary this year so don't forget to send a cameo to your valentine from two old love birds. Order one here! cameo.com/billdaniels cameo.com/bonniebartlett
86
96
22
1,152
171,016
This thread is full of good thoughtful deep understanding of f/oss and "source available"
Replying to @adamhjk
To fully understand what I don't like about these licenses, and what I don't like about the FSL, you have to pull apart the three things in quotes - "your software", "using and learning", and "harmful free-riding". We usually conflate all 3 when we talk about it.
1
186
Phil Dibowitz retweeted
I just realized that Hashicorp has become the first proprietary automation company since BladeLogic and OpsWare. (Maybe Tanium for a hot second, before they became live query splunk?) Maybe they can do the rest of us a favor and raise prices back to those 2006 days? :)
5
2
28
7,178