@jborean.bsky.social
@jborean.bsky.socialA greek coin you gave to Charon to ferry you to the underworld. Fit into the whole Kerberos/Cerberus and was a short word :)
@jborean.bsky.socialI've always disliked that I couldn't test Kerberos in CI easily and so I've written a #PowerShell module called Obol that can setup a KDC and configure the environment for the platform you are on github.com/jborean93/Po.... Uses @syfuhs.net's Kerberos.NET for the message parsing and encryption work.
@jborean.bsky.socialJust had a play around tonight and it's a no. There's a few smaller issues that look to be trivial but the biggest blocker is the krb5.conf parser which heavily relies on reflection. Most likely more on other platforms plus adding a net8.0 target so it can mark itself as AOT compatible
@jborean.bsky.social@syfuhs.net are you aware if Kerberos.NET is Native AOT compatible? Do you know if there are/were blockers to supporting it or it’s just not tested/tried?
@jborean.bsky.socialAny #WinRM users out there on Linux/macOS that use #PowerShell. I've been busy trying to get the v3 release of my module ready to go but this is a massive shift from how it used to work. Would love to get some real world testing to identify issues before I release it. github.com/jborean93/PS...
@jborean.bsky.socialTLDR: .NET Framework vs .NET and it not being 100% compatible. They have announced that they are hoping to ship 7.x in box with the next Windows Server release and hopefully Win 11 follows along. Probably will still be side by side for the near future.
@jborean.bsky.socialDefinitely fair, ultimately I think in today’s world even getting access to your normal user environment is mostly game over. Still MS themselves need to follow their security boundaries.
@jborean.bsky.socialIn WT's defence doing this exposes a window that a non-admin user could type into to run things as admin. I get that for some people they don't care about this but if Microsoft shipped a feature like this it would be DoA with the security reports.