The Doctor

They sure make the task of keeping an eye on the chuds easier. Their OPSEC eats donkey ass.

Why would they hide anymore? They figure they won. No sense in not taking advantage of everything that implies.

I keep a documentation page in my wiki for every thing I set up - how I did it, what I ran into, how I fixed it, and where everything is. Reason being, when it comes time to upgrade or I have to install it again someplace else, I remember how I did it. Basically, every completed step gets copy-and-pasted into a page along with notes about it.

As for watching the file system, I have AIDE on all of my boxen (configured to run daily, but not configured to copy the new AIDE database over the old one automatically). That way, I can look at the output of an AIDE run and see what new files were created where (which would correspond to when I installed the new thing).

The Great Game continues, same as it always has.

You can have them installed next to one another. Just like you can have Firefox and Links installed at the same time. Or twm and gnome3. It comes down to how much work you want for yourself.

Depends on your distro, I think.

If only for the sake of one’s CV. Making your bones by having a couple of 0-days under your belt helps a lot of folks find jobs these days.

It is. That’s why Wayland is being pushed so hard, it’s a codebase that’s actually maintainable, with hopefully some more modern design and engineering principles.

Agreed.

You can install more than one desktop environment at a time. Your login manager should let you pick which one you want to log into.

I’m running MATE on my laptop. It gives me what I need (a task bar, space for some instrumentation, the usual desktop functionality, a way to start applications) and nothing that I don’t care about (wobbling windows, compiz, stuff like that). My DE is a tool; I use tools that don’t get in my way because I have work to do.

I might give COSMIC a try in a few months, I haven’t decided yet.

When I could get away with it at work, I did.

In the last… I want to say six or seven years, issuing Macbooks to sysadmins has been a common thing in the sectors I work in. Rather than put up with us going rogue and messing up license tracking by rebuilding our stuff with a distro of choice, management just throws OSX at the problem (us, we’re the problem) because operationally it’s close enough for our purposes.

It’s not my choice or preference, but the money’s green.

The true final exam would be writing code on an airgapped system.

Gee. What a surprise.

Hey - an explanation. Who’da’thunk it?

https://www.phoronix.com/news/Linux-Compliance-Requirements

Ah, the Crypto Wars…

Nah. If anything, USian and non-Russian companies will add one or two more devs to their efforts to take up the slack. Linux is the bedrock of their revenue streams.

The US and EU governments have the criteria for sanctions available.

• https://www.consilium.europa.eu/en/policies/sanctions-against-russia/sanctions-against-russia-explained/
• https://ofac.treasury.gov/sanctions-programs-and-country-information/sanctions-related-to-significant-malicious-cyber-enabled-activities
• https://ofac.treasury.gov/sanctions-programs-and-country-information/russian-harmful-foreign-activities-sanctions
• https://www.bmwk.de/Redaktion/EN/FAQ/sanctions-against-russia/faq-russland-sanktionen.html
• https://www.trade.gov/russia-sanctions-and-export-controls

Probably because the advice in question was lengthy and technical (subtype: laws and legality), and the short form had the disclaimer "Please don’t publish the short form because it’s too much like giving legal advice.) Something similar happened back in 2012 with Project Byzantium, when we were consulting with the EFF with respect to having cryptographic libraries included in the distro.

Arguably, ITAR set the precedent in the 1990’s during the crypto wars. USians used to have to travel to Canada to work on cryptographic code in OpenBSD because their commits couldn’t legally be exported.