Re: Sex...
"sudo (or su, I guess) make me a sandwich"
996 publicly visible posts • joined 12 Jan 2011
It was a proxy. If you don't know what a proxy is, grab a millennial and we'll tell you. Their use-case is similar to Onion routing, its an important tool especially when governments and organizations like to hide or block things but can be abused.
Brian Krebs actually did a series not that long ago on this proxy actually, if you look for any of his Kimwolf botnet articles he discusses it as the bot herder was using IPIdea for C2 and wasn't shy about it. It seems at best this proxy was blissfully unaware about this sort of thing, and at worst was actively assisting threat actors.
On Linux, which I don't use personally every day but use a lot as we support at work, I've pretty much constantly been using Wayland since it was Fedora's default on my work and home PCs.
At home, I use it on an AMD based system with a recent X3D Ryzen CPU and a Radeon GPU and a ton of memory (need more storage though) I don't notice a performance difference between Wayland and X.org. To be fair though my system is pretty beefy so I doubt I'd notice anything.
As far as the Politics go, we've always had Stallman and the FSF. You may not agree with their politics but you're still using something that has GNU software on it somewhere in your daily life, or GPLed software in general. If this project is technically worth it, the politics don't matter, but introducing two serious bugs, allowing RCE because of course, doesn't bode well.
>In my career, the worst I was ever paid to do was support an entire Linux environment from a Windows pane of glass
I've had to do that before and it's extremely unpleasant, I've also had to do the reverse which is almost as bad, and to this day I don't get why we were doing things that way at either org, both should have really known better, hell one of them used to even develop a commercial UNIX, and sells products with both Windows and Linux, so you'd really think they'd know better and that the way they were doing things wasn't even sub-optimal and was just simply inane, but nope.
I think that's too complex for most juries to understand so if it might go to trial I wouldn't base a case around it. For something that's likely going to never be heard by a jury, maybe, but it would depend on the judge.
I'm not a lawyer but I am really unlucky and wind up on jury duty every couple of years, and usually for complex civil stuff like this too, my last trial took 3 1/2 weeks. I can guarantee you at least 3 people on a jury, enough to cause a mistrial, will not understand the argument at all. Trying to explain that in a jury room to someone who isn't technical would be exceptionally difficult.
It's probably WoL Magic Packets or Bogons that the firewall is confusing itself about, but don't let that irritate the skin under your tinfoil hat.
If NSA or the MSS (*not* Chinese APT subcontractors, the MSS itself) is breaking into your firewalls you'd likely never know unless they wanted you to.
Don't know why they're downvoting you, because honestly if I had the skill I'd be burning the midnight oil on making a migration tool for other Hypervisors precisely because Broadcom does not care about SMB, it never has. It never will.
There's real opportunity here, and I'd say that's not limited to just SMB, even among the big players that Broadcom does want to fuck over long term (like what they did with CA), are probably at least glancing at the exits especially if they dealt with that previous acquisition.
You do realize that's only 22:03 here, right?
They're landing it in literally the middle of nowhere at a secure facility. There's a lot of that here. The media don't normally care enough but they can usually get access to the Range Control on the main post to see the landing while it's being carried out. This isn't the first rodeo for something landing from space. Especially for this, since its been such a total goatfuck there will very likely be someone from the Las Cruces Sun News, Alamogordo Daily News, Albuquerque Journal, and Santa Fe New Mexican, as well as our two bigger NPR affiliates, KUNM and KRWG. Local media will be all over this.
For Unixlikes ever since my preferred Linux for servers decided to be no more because of corporate greed, I've been using and maintaining a whole lot of Free and OpenBSD, but I can't think of any of the OpenBSD machines having a GUI or a need for one. The smaller the attack surface the better, that's the whole point, and for where I work that's extremely important.
I live in New Mexico. In Albuquerque specifically. While I'm not sure what the exact reason is I can guess they're anticipating funding cuts from less money being made from the Permian Basin's oil and gas extraction which is affecting education across the State.
Don't make education funding dependent on something variable like fossil fuel extraction, folks, it's a pretty bad idea.
State may also anticipate losing a lawsuit over a murder one of their Basketball players committed in Albuquerque (State is in Las Cruces) at UNM in December 2022 that may result in a little penny pinching.
Its in everyone's interests that there's competition, the more the better really.
Ariane was the just about the only thing that kept ULA and it's predecessors "honest" (in the typical twisted defense contractor manner of speaking "honest") for a long time before anyone thought SpaceX was a serious competitor.
And if I'm not mistaken the JWST was launched on an Ariane 5, so it's not like there's no US interest in the ESA's programs just regardless.
That's precisely what I was going to say, except I'd go one further and say about 30 years but I pay a lot of attention to ISAs.
ARM has been the "next big architecture" since about the Archimedes. I also remember when PowerPC, Alpha, and IA-64 were all going to "replace" x86 at one time or another.
I dunno about you but it's been a long time since I've seen an Itanium or an Alpha in the wild.
We already have it on FreeBSD and its decent. It's not that difficult to get working with a DE either, I use Wayland with KDE as my daily driver on that OS if I'm using a GUI there anymore actually. OpenBSD is working on it from what the article says, it'll probably wind up being the same way over there but I can't speak to it.
Probably the most upset and irritated I've ever seen your writing here Jake. And you've been around here about as long as I have so that says quite a bit.
Regardless, I agree that trying to rewrite the rules to enforce a monopoly and browser monoculture is foolish. I don't think it's going to work, as soon as Google gets distracted you'll never hear another word about it. What worries me is a more focused company that doesn't kill its projects like it's going out of style doubling down on this.
It's not quite the same, Oracle decided they didn't want to do it anymore so the community forked it into Illumos and OpenIndiana. It's still a thing. OpenZFS is a Illumos project if I'm not mistaken.
This is more IBM being belligerent toward a community that pretty much worked as free advertising for RHEL for a long time to squeeze a couple bucks out of the community. I don't know how many times I sold RHEL because I had the client try out CentOS, now if I'm doing something stable where Fedora isn't appropriate but FreeBSD is overkill, it's mostly Debian derivatives like Ubuntu that I wind up using, and I'm not their biggest fan so it says a lot. I wish I trusted Oracle enough to use theirs but I don't.
That's pretty much how I see it too.
Those of us who can and care to may want to consider donating to the SFLC. They're likely going to need it, fighting IBM over this and whatever else they try and do is going to take forever and cost a fortune, think SCO v. The World writ even larger.
I really wonder what Oracle is going to do here since isn't their Linux basically just RHEL with Oracle branding?
Try that on a Windows, Linux or FreeBSD machine and its about the same, there's a lot of overhead with OSes that don't have their existence predicated on security. Which isn't very surprising as Theo and Co make it a point to have the smallest attack surface as possible OOB. I'm not a fan of his personally but I do have a lot of respect for OpenBSD though I don't tend to use it unless I need something highly secure without much fucking around with it (there's always going to be some, even with how secure it is by default), FreeBSD has long been my UNIXlike of choice with Fedora and RHEL a close second and third but there's a time and a place for something like OpenBSD.
Its called Binning and they most certainly still do it. It saves them money by being able to sell a processor that they'd otherwise have to destroy. I don't know how common it is for other manufacturers but I know Nvidia does the same and Id imagine Samsung and TSMC do it as well.
Fuck the Commonwealth of Massachusetts too.
Big question is what else were they doing with the data and who else had access to it? I'm quite sure DPH were willing to hand over any data that was requested to the Staties, Boston or Springfield Police because thats how it works there. Same with UMass. And the joint Commonwealth-DHS Fusion Centers. And DSS or whatever they call it now.
Massachusetts has never seen an invasion of privacy that it didn't like and as much as I abhor conservative SIGs I really don't trust the Commonwealth with anything like this because they use whatever they can get to fuck with people.
Its probably on an ancient version of an RTOS called VTRX. There are other Electro-Optical and Synthetic Arperture Radar satellites looking the other direction which use it as well which is why I'm not getting into detail here, but its a known quantity.
I can bet some of them probably won't work when they switch over. However, If the addon developers are any good they'll have been testing against chromium builds with the new version of manifest and it should work. I would fully expect something to not work though, have a failover ready for a few days. That's just good advice in general but whenever software like this gets changed, shit breaks unexpectedly. And its always the worst possible component that there's no good workaround for.