If you're forcing someone to print and sign a document, understand that you're hurting the underprivileged who don't own or have easy access to a printer. I'm traveling this week and HAD to print something. My friend's printer is broken. This was the cost for ONE PAGE. 1/
Now that's not hurting me a bit, but also recognize it's not the total cost. The nearest place advertising self service printing was Staples, and thankfully I have a car. I'm still out just over an hour + gas costs all in. With public transit, double that (or more). 2/
The money doesn't matter. The time does though. And while my time is more valuable (measured by hourly rate), the time impact to someone underprivileged is much higher. "Pull yourself up by your bootstraps" only works if you don't rob them of time. /3
The technology divide is real and creates significant challenges for some. Just because something is easy for you, that doesn't mean it will be easy for others. Try to think about workflow and the burden you might be creating for others. /4
I know there are libraries, print it at work, etc arguments. But if you're making them, you're missing the point. It's about more than printers, it's about privilege.
Today reinforced the technology divide and challenges it creates for the underprivileged. /FIN
Also, before I get security shamed, I used a disposable USB with the single one page doc on it. But I guess having a bin of disposable USBs (and the knowledge to use them) is another example of privilege.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
If @GitHub (Microsoft) truly believes copilot isn't infringing on anyone's work, I want to offer them a chance to prove it: I'll donate $50k to a charity of their choice (or @EFF if we can't agree) if they release a Copilot version trained solely on Windows kernel source. 1/
This isn't a joke. It would be amazingly helpful for device driver developers. This in turn would ostensibly benefit Windows users through fewer BSODs. Add the charity money in and there's literally NO REASON not to do it. 2/
So let's set some ground rules:
Independent verification that the newly released model is only trained on kernel source
It's the full kernel source, from all versions (leave Win2k out if you want due to that pesky Java thing)
All kernel drivers owned by MSFT are included too 3/
These newly disclosed vulnerabilities in tcpip.sys are a really interesting case study in why holistic security matters. Sure you should still be patching, but are your firewalls and IPs systems properly configured? If so, these probably aren't an issue 1/ msrc-blog.microsoft.com/2021/02/09/mul…
First, let's look at CVE-2021-24094/24086. Both involve the reassembly of packet fragments. If you've never dealt with issues IP fragmentation and never had to worry about the MTU across the network path, that's okay. It was a common thing many moons ago, but not much today. 2/
In IPv4 there are lots of variations in how fragments are handled, particularly for out of order delivery. It turns out the original standards weren't very clear on this so everybody did what was easy. But as IPv6 was being built, the standard is clear: no overlaps. 3/
As I continue to interact with folks dealing with the aftermath of the NYT JetBrains story, I'm calling it - the story was irresponsibly released.
The story lacks any actionable details and has collectively cost overworked security teams *thousands* of hours in response. 1/4
One defender I know called it "the NYT denial of service." I'm sorry if that hurts the author's feelings, but perspective and all...
"Officials are investigating" is hardly enough with something this big. The impact of speculation like this is HUGE for network defenders. 2/4
I get why executives are hammering security teams for assessments though.
Look at the wording used. We pivot from "officials are investigating" to "the company is unaware of any investigation/compromise" to "officials are not certain how THE compromise" (as if confirmed). 3/4
This story is getting a lot of attention. Let me quickly break down for followers not in offensive security what it means.
This is not great, but *the sky isn't falling*. Anyone who says this will immediately result in {thing} is uninformed (or worse) 1/ reuters.com/article/us-glo…
First, we need to take the MSFT information at face value. MSFT says attackers could *view* some code (not sure how much/what) but specifically notes that the attackers could not modify anything.
Claiming "well there's risk they had write access" is unproductive in every way. 2/
As MSFT notes in their blog post, they have embraced an open source threat modeling approach - assume the code will become open and don't tie security to secrecy.
Quick thread 🍸:
I’m a gen-X kid. I grew up in an age where I was told that nobody cared what you got a degree in, as long as you had a degree “they would know you can be trained.”
WTAF did that mean, anyway? Why did I need a college degree for that? 1/
But hey, I failed out of college. It was the best thing that ever happened to me. It took me out of medicine (I’d have been a practitioner, not a researcher) and put me on a track for something else. Of course it took a TBI along the way to get me here, but fate and all... 2/
Now I have degrees that are barely worth the paper they’re printed on. Lots of my friends do too. Most of them aren’t doing as well. The vast majority work in fields outside of their study.
But hey, you can still succeed. I come from food stamps, not generational wealth. 3/