Twitxy Saved

Steve Friedl

Verified account This account is verified. Learn more

@SJFriedl

C/C# Software Consultant; Public-safety networking; very amateur EE (Keysight fan); exMSFT Security MVP 2004-11; high tolerance for ideas I don't share; KA8CMY
Southern California USA unixwiz.net Joined April 2013
847 Following 819 Followers 16K Posts

Latest posts 5

Pinned post

Steve Friedl Verified account @SJFriedl
Hello Twitter, I don't think I've ever made a proper introductory post and provided a face to a name.

I've been a self-employed software and network security consultant since the mid 1980s, living in Southern California with my wife, and mostly working at home in my pajamas

From 2003-2011 I was grateful to be named a Microsoft Enterprise Security MVP. They changed their award trophy in the middle of my tenure so don't have several of the early rings, and I think my 5-year ring should be at the bottom.

Being named a Microsoft MVP was one of the two highlights of my professional career: the other was teaching advanced C/UNIX at AT&T Bell Labs in New Jersey.

MVPs are such a wonderful community. #mvpbuzz

I took a degree in Math/Computer Science and have been working with UNIX since 1981, and wrote in C/C++ for many years on Windows, UNIX/Linux, and occasionally other platforms.

In my work on commercial fax software back in the day, I ported to almost three dozen UNIX platforms, most of which nobody's ever heard of these days.

Of late have been doing almost all my professional work in C#, and I absolutely love #Dotnet

Computer security has been an interest for a long time - I broke root on a VAX running BSD UNIX using vi back in the eighties - and used to do a lot of pen tests, but those days are behind me as I settle into work that's less stressful.

For the last 15 years or so, I've run a public safety network here in Orange County where I live; our 911 fire dispatch center talks to every other fire agency in the county, and this means firewalls and T1 circuits and all that. It's been very rewarding work to support the fire service.

I also tinker with electronics, having a decent set of test gear (mostly @Keysight , née Agilent, née HP - shown below) despite zero formal training, and I build small controllers and robots for my brother's biomedical manufacturing business, mostly with Arduino and ESP32 in C.

Also a huge fan of 3D design (Fusion 360) and printing (Prusa MK4); I have designed and printed hundreds of workpieces - some trivial, some substantial - and I wish I'd gotten into this a long time ago.

My wife Jaimee - who I met on a hike - writes romance novels in her spare time, and together we enjoy good food, wine, and travel, especially river cruises, especially in Europe. I love France.
9 replies 0 reposts 63 likes 6.9K views View on X
Steve Friedl Verified account @SJFriedl
A fun story about a customer who doubled down on bad choices.

Many years ago, they had a Windows SBS 2003 system to run their enterprise, and for discussion let's call them XYZ Construction Company.

The guy who installed it (before my time) used the domain literally `.xyz` (rather than `xyz dot local` or the like), and this is known as a "single label domain".

This is legal but not recommended, and it ran into all kinds of compatibility problems here and there with software that didn't expect it, but we lumbered on: changing the domain of a Small Business Server system in place was essentially impossible.

Well, they grew *a lot* and were past what SBS could support, so they were building up a full new Windows domain system, and this was the time to do it right!

It's still a heavy lift.

We all talked about this and agreed that `xyz dot local` would be the internal domain, and their in-house IT guy - arrogant but nominally competent - went to town.

But when I showed up to help with some stuff, I discovered that the guy used `xyz dot com` (instead of dot-local, even though this was not their domain.

This created all kinds of problems, and at some point I believe we had to set up egress filtering on the firewall to block attempts to reach the *real* `xyz dot com` mailservers because misconfigurations were sending stuff to them all the time.

What a mess.

Sadly, their business took a turn some years later so I guess you could say the problem solved itself, but I'm still boggled that an experienced guy could do this.

It's always DNS.