Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 5 Posts
  • 378 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • dan@upvote.autoProgrammer Humor@lemmy.mlAbstractons
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    5 days ago

    Windows itself is technically running in a VM if you have Hyper-V enabled (not quite that simple, but that’s a reasonable approximation). Hyper-V is a type 1 hypervisor which means it runs directly on the underlying physical hardware, and both Windows as well as any VMs you create are running on top of Hyper-V.



  • For DNS challenges, I personally prefer using acme-dns. It’s a separate DNS server that only serves ACME DNS challenges. I felt a bit uneasy using an access token for my actual DNS host since it grants full read/write access to every record. acme-dns reduces the attack surface.

    Let’s Encrypt follows CNAMEs and supports IPv6-only DNS servers, so you could just run acme-dns on a spare IPv6 address (assuming your internet provider has a static IPv6 range, or you have a VPS with IPv6).







  • mostly a wrapper around their proprietary library

    I’m not familiar with exactly what Bitwarden are doing, but Nvidia are doing something similar to what you described with their Linux GPU drivers. They launched new open-source drivers (not nouveau) for Turing (GTX 16 and RTX 20 series) and newer GPUs. What they’re actually doing is moving more and more functionality out of the drivers into the closed-source firmware, reducing the amount of code they need to open source. Maybe that’s okay? I’m not sure how I feel about it.






  • You only have to pay for a license if you need multiple users or want to use their cloud services, I believe.

    AFAIK you can have multiple users for free when self-hosting, and the features are essentially the same as the free hosted version. You need to pay if you want to get the premium features or share passwords across multiple users using an organization. Essentially the pricing is the same as the hosted version.

    I’d recommend Vaultwarden for a small-scale self-hosted solution. It’s not Bitwarden, but it’s fully API-compatible so you can use all the Bitwarden clients and browser extensions. Self-hosted Bitwarden is quite a bit heavier than Vaultwarden since it’s designed for large-scale usage (like for an entire company of tens of thousands of people)


  • if you work somewhere that uses 1password, you can usually get your personal subscription comped as an individual

    Same with Keeper as far as I know (which is what we use at work).

    I prefer security software to be open-source though, which is why I love Bitwarden. Even if you don’t self-host it, there’s still value in it being open-source.



  • Accessing Vaultwarden through a VPN

    Hmm maybe I should move mine to my VPN. Currently I have it publicly accessible so I can access it from systems where I can’t run other VPNs for security reasons (work systems). I use a physical token with FIDO2 (Yubikey) for two factor authentication though, so I’m not too worried about unauthorized access.




  • it seems pretty sub-optimal for a personal site to be publicly associated with even a permanent IP address

    What’s the downside you see from having a static IP address?

    I don’t see any way to achieve this without a CDN, unfortunately.

    I think you’re looking for a reverse proxy. CDNs are essentially reverse proxies with edge caching (their main feature is that they cache files on servers that are closer to a user), but it sounds like you don’t really care about the caching for your use case?

    I don’t know if any companies provide reverse proxies without a CDN though.