traumivator

You are very close to solving a real business problem. The problem is not "how can I have SSH aliases on my computer" but "how can we manage, company-wide, who can access which SSH servers."

My company currently uses YubiKeys to support hardware-based individual SSH keys. These SSH keys are distributed with Ansible. It works but is cumbersome and lacks a single pane of glass.

What we would like to have: a list of servers, a list of users, user roles (via sudoers), and a WebUI to manage all of it. And I don't know of any tool to do this. Of course, there are tools like Teleport or SSH CA instead of SSH keys, but they are for larger organizations and are overkill for my company.

My company evaluated both Yubikey and Nitrokey and decided to use Yubikey. While they are both in the same price range, Yubikeys are more durable, whereas the Nitrokey plastic cover began to show cracks. Because our employees wear them on their keychains, that would be a problem, while the Yubikeys were fine.

Also, the cheap Nitrokey FIDO2 key doesn't support ED25519 for SSH keys, only RSA and ECDSA, and even though they are open source, the promised support for ED25519 is still not delivered even after 4 years, so I doubt it will ever come: https://github.com/Nitrokey/nitrokey-fido2-firmware/issues/3...

Ultimately, while I like the idea of open-source, for a company use case, we had to go with Yubikey.

Hi everyone, this the Creator of ExampleConfig.

I encountered the following problem: When editing configuration files I sometimes reached a point where I messed up the config file pretty bad. No point in trying to fix things, when clearly a fresh start makes more sense. Turns out finding the shipped original version of the configuration file is actually pretty hard. If you are lucky you find this original config file on some random GitHub Gist or accidentally indexed FTP server. You probably know this situation.

Solution: I went ahead and built an archive of these clean, original configuration files. Now you and me got them all in one place. They are collected from a fresh installation of the application (Apache, nginx, MariaDB, etc) on various Linux distros (Debian, CentOS, Alpine, etc). This is important because config files differ slightly between Linux distros.

Tech: Frontend: static site generated with Hugo.

Backend: applications are installed in Docker containers. The shipped configuration files are fetched and the containers are destroyed. This process is repeated for every Linux distro.

The goal of ExampleConfig is to provide a collection of original, unaltered configuration files for multiple applications.

Let me know what you think, what I should improve and what applications/distros you are missing and so on! (especially since this is my first time launching a product)

Check the volume for USDC/USDT. It has been increasing the last couple of weeks.

So one could argue that people are trading largely unbacked USDT for backed and audited USDC. Which increases the demand for USDC and the USDC minting.

I can recommend https://twelvedata.com/

Same, I still see my colleagues typing but that's it.

Their status page reports it's fine: https://status.slack.com/