• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • Years (decades) ago it wasn’t uncommon to create self-signed/local CAs for active directory, but it’s really uncommon today since everything is internet facing and we have things like Let’s Encrypt.

    It’s so old, the “What’s New” article from Microsoft references Windows Server 2012 which is around when I stopped working on Windows Server. I kinda remember it, and you needing to add the server’s cert to your trusted roots. (I don’t know about Linux, but the concept is the same, I’m sure. I never tried generating certificates, but know all the other client -side stuff. Basically you need a way to fulfill CSRs.)

    https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/

    What you’d want to do it in Windows is all there, and Microsoft made that pretty easy back then to integrate with all their platforms and services, but I’d caution, do you really want to implement 10+ year old tech?



  • ShortFuse@lemmy.worldtoFirefox@lemmy.mlHow about no?
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    6 months ago

    Definitely not.

    I have to version check to workaround Chrome, FireFox and Safari bugs. Some things they fix and I can flag around version (eg: FF113 has buggy focus detection with Web Components), but some just have never been fixed (eg: Firefox does not support animated styles with CSS variables in Web Components).

    That’s not to pick on FireFox. Chrome doesn’t support scrolling two elements simultaneously which breaks any type of fancy horizontal scrolling in horizontal tabs. Safari has some buggy implementation with ARIA tags for Web Components and [type=range] doesn’t follow spec for min.

    If we were going to just not support new features because browsers are buggy, we’d never get any new features. It’s better to feature detect and that includes knowing what versions need workarounds.