Update on running MS Office in closed lab networks

Some of you might have been subject to my old-man ranting about how difficult it has become to install software that “just works.” My raging against the cloud, against everything-as-a-subscription, and against software that requires the capability of phoning home, either during install or on a continual basis.

My task was to install MS Office in a closed lab network, so that the users doing the work in the lab could write reports, etc., without having a separate machine just for that purpose. This network does not connect to the internet. It is a self-contained lab network with only what is needed for the lab installed on it.

It’s been a while since I fucked around with Microsoft products, and I naively assumed it would be a piece of cake. Just install it, give it a key, and be good to go. I was warned by those who had gone before me that it’s no longer that simple. Everything in Microsoft-land requires internet, they told me. “Surely they understand that a use case exists for no internet/no cloud,” I started to respond, before reliving the trauma of having to kill Atlassian when they made their on-prem product completely out of reach for small groups/businesses.

So I started down the road. I bought 12 licenses for “standalone” office 2016, went through the process of installing it on one of the lab machines, and yep, it requires internet to activate. OK, I’ll play along. We use FOG to image these lab workstations, so I set up a fresh install on a golden image candidate, activated it over the internet (very ugly process, by the way, if you buy multiple licenses), confirmed it was functional, and then captured an image of it. Rolled it out to other workstations, only to find that each new clone required its own activation. Well, this will never work.

I managed to get MS to refund the product after a lengthy discussion with a support rep. I decided I wanted to go the way of a volume license, only to learn that the KMS server too needs to touch the internet. I kept reading and reading and learning, and finally came across vlmscd, which is a linux-based open-source KMS server. Its only job is to say yes. When configured as the KMS server for a workstation (using DNS or manually via slmgr), any activation requests received by that KMS server are simply approved.

So I built one, making sure our licensing is properly paid for and accounted for,I of course. I added the SRV record for announcing the KMS service to the closed-network DNS, and installed the VL version of Office. Initially, running OSPP.VBS from the Office16 directory reported that the software was under a grace period with <30 days remaining, but after a reboot it reported it was fully licensed.

I wish vendors would provide a bit more flexibility in their product offerings, and understand that there are use cases that are outside the norm. I understand their need to protect their software from piracy, but this kind of heavy-handed control really makes it difficult for some of us who, for various reasons, don’t want to connect every network in our enterprise to the internet. We still exist.

DC540 is Virtual this evening

Tune in to the Discord voice channel at 1830. Good chance to get to know some of us if you haven’t been to an in-person, or to participate in summer camp decisionmaking if you’re a regular.

DC540 Monday 4/18 VIRTUAL

We’ll be meeting up in the Discord voice channels on Monday evening @ 1830. We will likely break off into at least one non-public channel for badgedev discussion, but please feel free to join us in the main meeting channel anyway.

In-Person @ Social House Again Tonight

We’ll be in person at the Social House tonight. Social House is a restaurant — not my house, FYI. Will have the Malort if anyone’s feeling stupid. Will have last year’s badge to compare and discuss w/r/t planning and measuring for this year’s badge.

The Hacker/Modular Overlap

Oooh, that could be a stage name. HMO.

I wanted to take a moment to digress a bit and go into what makes modular synthesis so rewarding to folks with a hacker mindset.

I’m not a musician. I have dabbled in bass, guitar, keys and drums, but as for formal training, I’ve had guitar and djembe lessons, and not a whole lot of them. But the thing about music is, if you LOVE music, it will find a way to move you in one direction or another.

I’ve had many thousands of dollars worth of equipment over the years from Korg, Kawai, Yamaha, Casio, Nord, Alesis, Peavey, PRS, Epiphone, Tascam, Moog, Ableton and many more. And they’ve all been very rewarding in their own way. But none of them has given me the sustained high that exploring modular synthesis has given me. My first exploration was a Moog Subharmonicon, which quickly grew into the entire Moog semi-modular trio of Subharmonicon, DFAM and Mother32. I realized that being able to tweak and modulate sounds and sequences on the fly on an intuitive basis would more than make up for the fact, for me anyway, that I have limited musical playing ability.

And when I expanded that setup to include specialized Eurorack modules like Clank Chaos, Castor & Pollux, and utility modules like mults and LFOs, I realized this was the space I needed to be in. The limiting factor for making music, for me, was always that without musical skill, there was only so much variety I was able to create in realtime. Sure, I could layer multiple track and create sonically rewarding pieces, but look — I work in tech all day long, and I pursue tech hobbies on the side as well. The last damn thing I want to do when I make music is drill down into menus and learn advanced software tools. I wanted something far more tactile, and something closer to magic. Rather than directly crafting a particular sound, I find value in combining functionalities and making the different components “influence” each other in unique and interesting ways. I find that when I start a session with modular equipment, it never ends up in the same place twice. Sometimes I’ll start with a keyboard CV value to start, and route it into one or five places. Sometimes I’ll take the audio from one component and throw it into another for further manipulation. I’m particularly drawn to the modules with an element of randomness or surprise, like the Clank Chaos or the QuBit Bloom.

I credit another DC540 member for triggering me to make some changes and fall even deeper down the modular rabbit hole. Now the semi-modulars are on their way out, and I got a new case to replace the non-portable homemade Ikea rack I was using before. I find myself imagining how this configuration could be taken completely portable, and actually considering replacing the brand new 24-channel mixer I just bought a few months back with something similar that fits in the box.

For a while I had a friend’s Minimoog Voyager. I loved how it combined the best of both worlds. You could easily choose presets, but you could make vast modifications to those presets by twiddling knobs, and then save those changes to your presets. A bit out of my league pricewise, though, unless I sacrificed much of my other gear.

Busy busy busy, FlipperZero and Proxmark3 RDV4

As I posted the other day, I recently received my FlipperZero. I learned that it would read my 26bit LF RFID cards, but not my 34bit LF RFID cards. I fed my info back to the developer(s) via github, we’ll see if improvements happen over time.

But during the process, I ended up using my Proxmark3 RDV4 to help troubleshoot, and ended up getting the latest, most maintained and seemingly most capable firmware.

What some people don’t realize about the PM3, like a lot of SDR type devices, is that the software consists of two parts — firmware for the unit itself, and client software that runs locally, connecting over the USB serial, to issue the commands to and receive replies from the firmware. This means that it’s critical, when you swap firmwares, to swap clients as well. Managing multiple firmware versions can be confusing for this reason.

In the process of troubleshooting, I realized was using the iceman firmware from a few years ago, and the official “stock” firmware, also from a few years ago, None of this firmware was able to give the developer dumps in the format requested. Turns out there’s a far more current build out there at https://github.com/RfidResearchGroup/proxmark3.git, and even flashing the bootrom has gotten easier. Just hold the button down while you’re plugging it in, and continue to hold it while entering the command to flash the bootrom. Seems that tactic also works if you’re having trouble flashing the firmware itself. Painless firmware flashes. I did this from a Macbook M1 Air, and it took a bit of fiddling to get all the requirements down, but once I did, it works like a breeze, and the pm3 client and pm3-flasher client are both in my path now.

Still bummed that I haven’t been able to read my cat’s RFID tag yet, but I’ll keep banging on it, and maybe eventually I’ll figure it out. No idea if the Flipper will be able to read that.

Next temptation: Maybe a dual RFID ring. They make nice looking rings that carry both LF RFID and a MiFare 1K “magic” tag. I wonder if many hotels are still using MiFare 1K. It’d be fun to clone my hotel room key to a ring.

I’ll probably have them both with me at the meeting tomorrow evening if anyone wants to experiment.

DC540 Meetup 3/21 In-Person

We’ll be meeting at Social House in South Riding tomorrow evening, starting at 1830 til whenever. A great opportunity for noobs and strangers to prove their worth for elevated Discord status and invites to the private meetups.

Bring badges, wear swag, show your defcon colors. We’ll be easy to spot. If the weather holds out as planned we’ll try to hang outdoors.

Monday 2/28 HYBRID.

This week’s DC540 meetup will be HYBRID. In person for those who want to share a common space and a common table, and virtual for those who can’t make it out. Tune into the Discord for topics.

NEXT week, 3/7, will be virtual only due to stuff going on.