I am very happy with Netcup. https://www.netcup.com/en/server/vps

Ah, missed the line in the article about secondary tariffs. Thanks for pointing it out to me. A 100% tariff on China and India until they stop importing Russian oil would indeed be very disruptive

What I’m missing from the articles is putting the potential consequences of the threatened tariffs into context. In 2024, Russian imports into the USA were 3.27 billion USD, whereas the GDP of the Russian economy in 2024 was 2.17 trillion. Even if there is fakery in the reported GDP, exports to the USA are likely less than 1% of the Russian economy

You can sign git commits using SSH keys, including the one you use to connect to GitHub/GitLab/Codeberg. These sites also support verifying the signature.

This is exciting. My only request here is: whenever it works please release a standalone wasm file somewhere (anywhere). So many projects either require building the wasm themselves, or instead of releasing a .wasm, they release a JS wrapper that auto-loads the wasm/wasm-imports. Its a pain to try to extract the wasm out of those projects.

What I am doing is to create a omnikee-lib crate within the project that will get compiled to WASM, not just plain keepass, because I need additional adapter methods to interface with the web part of the application. I don’t have the bandwidth to turn keepass into a general WASM package that could be npm installed at the moment. As I am dogfooding the crate, I might get to a point where I know what a good JS interface for it would be, though, and the omnikee-lib crate could become the official WASM interface for keepass.

sweet! I sent you the invite.

Currently, SSH key management is not supported, but it would probably be possible to implement the SSH agent protocol in the Rust part of the application. I see that russh has a SSH agent server implementation. Let me know if you are interested in contributing such a feature - I am currently working on exposing all the custom entry fields in the UI, so the project would almost be ready. edit: would be ready to add that feature now

thanks for your interest! I have sent you a response with an invite link.

I think the Google as an identity provider example is misleading. The more common use case will be medium to small companies where several admins/developers need to login to various servers and where manually adding and revoking keys across these servers will be cumbersome.

As the other commenter said, in those cases, the organization would also deploy its own IDP.

I have been using it for the last 3 months to expose services from my home internet (plex, wireguard, etc.) through a VPS and I’m pretty happy with it. It’s relatively simple to set up, I haven’t had any outages so far, and it’s nice that it supports UDP port forwarding as well as TCP (for wireguard).