wouldn't be so bad if he was part of the call in the first place.
need to learn how to think about OPSEC in an open office. coworker is repeatedly using information I give over the phone to ask me questions.
I think it’s time to show my kids just how much network knowledge I have. Had to unplug the router twice to get their attention. Going to automate that with voice commands.
Disconnect thing one now.
hahaha. org.eclipse.jetty.util.thread.strategy.EatWhatYouKill
Going into the app you get one further question: Why? Choices are "this is a fraudulent authentication" or "I hit this by mistake".
The logging is fascinating... if I decline Duo auth without actually going to the app, it gets recorded as denied by mistake. Nope, pretty sure I declined it on purpose. If I fail to notice the request at all, it's accidental decline by mistake. Fair, I'll accept that one.
Oh hey, somebody is trying to break into one of my servers. Duo keeps prompting me for authentication. Pretty sure I'm not at that source address.
Mastodon on Mobile Safari is weird. Have to hit refresh twice before my feed updates.
Living in those "interesting times" again. Who did I piss off this time?
Monday morning routine:
Start Parallels Desktop
See that RHEL7 and HardenedBSD were running when it shut down on Friday
> ssh hbsd
(Oh, this pause probably means it didn't restart prop... what is this?)
"Autopushing login request to phone..."
Verify Duo Security login request
(let's see what I can do in this VM today. yay)
Haha! I have a rhel and a hardenedbsd system being authenticated by Duo Security for ssh, local login, and sudo access.
Okay, second system configured. #hardenedbsd uses Duo Security to authenticate sudo, but not ssh. Time to troll Duo's forums, I guess.
Oops... just killed my logins but good
oh hey, the Duo security library is already in hardenedbsd ports.
Sigh. sudo is the only system authenticating via Duo. local login and ssh both skip the Duo part of the configuration
Got me partial Duo authentication... didn't confirm on login, but did during a sudo call
@lattera so, umm, what's with hbsd-update returning `[*] Could not get the version number` ?
Freaked the kids out with how fast I did the splits.
Grabbed a knife from the block and it spun out of my hand straight to the floor between my feet.
I may have pulled several muscles in the process.
So far: OpenBSD -> doesn't recognize my ssh key?!
HardenedBSD -> latest download needed to be updated before I could add pkg or ports to it.
Moving along on HBSD while OBSD languishes.
Cleared itself up. I think.
