possiblylinux127

Yes

If it is a different team, why wouldn’t you just say that’s your recommendation? Your story isn’t making sense

I don’t know what is happening any more

If this is for work you probably should bring in a professional. There are enterprise solutions for this.

This is selfhosted after all

The web interface is based on bitwarden. You are thinking of the client api.

https://github.com/dani-garcia/vaultwarden

The web interface is from bitwarden. Technically they could fork it but that would be much more work.

They don’t make any money off of the open source version. It is just a matter of the before they “discontinue” the open source version and move to source available.

Vaultwarden still depends on upstream bitwarden

It is effectively going closed source

Shoot

Ah, that makes sense

Side note: you don’t need multiple ports to have multiple subnets. (You can just use vlans)

Do you have any network segmentation is all your stuff on the same lan?

You also could try IPv6 public or private addresses

TrueNAS Scale is cool but I moved away from it as it is a pain and not terribly open

I run podman in proxmox vms

300 EUR is a lot of money depending on who you are

True but if you look online Chrome OS devices are dirt cheap. The major trade off is that storage is limited

I would instead look into old Chromeboxes. They have about the same compute but don’t have a battery and can typically run mainline Linux (assuming they are supported by mrchromebox)

The transparency logs would mean that any rouge certificates created would leave a paper trail not to mention there is nothing stopping them from issuing a certificate for any domain of there choosing

You go to a different CA

You do make a good point. However, Let’s encrypt is run by the IRSG which is a non profit focused on improving internet security. They are the ones who are pushing for shorter certificate lifetimes among other things.

ZeroSSL is probably what OP is looking for

The private key isn’t used for encryption

The certificate is only used for authentication. The actual data is encrypted with a temporary symmetric key that is generated via a diffie-hellman exchange

Maybe I’m mistaken but aren’t the logs cryptography verifiable? (As in you can’t create a rouge cert without it creating a trace)

Let’s encrypt is very transparent and has been designed to be auditable. What are you worried about exactly?

Lost Lemmings?

Are they Broadcom based?

If they aren’t you might be able to get the Linux kernel running on them. Openwrt would be much better.

Just use mediawiki

It is what powers Wikipedia

Have you considered putting your kids up for adoption?

OpenWRT now uses DSA so that article is dated

Thanks for the clarification