tcpauth VS leapp

Also became a fun learning experience about terminals.

https://github.com/ThomasHabets/cmdg

I wanted to use GMail from a fast cli that used the native gmail API.

https://github.com/ThomasHabets/rslurp

I wanted to download concurrently and according to patterns. Ok, so honestly this one probably exists somewhere in a form that I would like, but I couldn't find it.

https://github.com/ThomasHabets/sim

I wanted multi-party authorization for sudo, and couldn't find one.

https://github.com/ThomasHabets/monotonic_clock

People kept using gettimeofday, so this is part of my compaign against it. (see https://blog.habets.se/2010/09/gettimeofday-should-never-be-...)

https://github.com/ThomasHabets/gtping

I worked in mobile core networks, and wanted a "ping" that used the GTP protocol since that won't be firewalled.

https://github.com/ThomasHabets/ind

I wanted my bash scripts to have automatic indentation, while not sacrificing buffering latency and such.

https://github.com/ThomasHabets/tlscheck

I wanted a simple tool to audit my TLS certificates for expiry.

https://github.com/google/huproxy

I was travelling to China on vacation and wanted a VPN out that would be unlikely to be blocked by the great firewall. Ok, so there are many VPN-like tools for getting through the GFW. Maybe it was just an excuse for me to write it. Honestly ssh -D would have likely worked just fine. It's being used by the keymaster project now though, so maybe it did something right: https://github.com/Cloud-Foundations/keymaster/blob/master/d...

https://github.com/google/tcpauth

I wanted to lock down SSH to anyone who doesn't have a secret key (and portknocking is usually ridiculous). Why not use TCP MD5 for it? https://github.com/google/tcpauth

Summary:

Do you find yourself overwhelmed with work, requests, or complaints and in need of assistance to alleviate the pressure, enhance communication, facilitate organization, prioritize tasks, and foster greater trust and transparency?

Alternatively, I can work as a full stack developer.

AWS Community builder, AWS User group Leader, public speaker (https://www.youtube.com/watch?v=qdu58NAQfU0&t=271s)

Or perhaps you need both? =)

I have 4+ years of experience as a product manager and 8 in product development (before pm: agile coach, UX designer, and developer).

I've been the co-founder of the open-core company behind the OSS project Leapp (https://github.com/Noovolari/leapp)

Please feel free to reach out.

You can switch to saml2aws using the browser method instead of the Okta method and it will continue to work after the upgrade. There is also a really neat GUI tool to manage your session tokens that also works. https://www.leapp.cloud

Take a try to Leapp: https://github.com/Noovolari/leapp

Hello everyone, I'm the maintainer of an open-source DeveloperTool (https://github.com/Noovolari/leapp)

With a heuristic of 7000 users daily, I started feeling the need to have more information on how Users are using the project to improve it.

Is it the right thing to do to create a better Developer Experience and gain feedback for the end users?

On a side:

- For all your employees I can advice you Leapp as open-source project (https://github.com/Noovolari/leapp). It solve mayor of the problem listed here:

I am looking to manage Leapp (https://www.leapp.cloud/) from the StreamDeck. Leapp allows you to manage and switch between different Cloud Accounts (AWS, Azure, etc). Leapp has a command line interface which I could automate with a StreamDeck plugin. Unfortunately it looks like the only official SDK is the sandboxed JavaScript one. This means I cannot automate command line tools with it.

If you’re wondering if there is a tool that allows you to stop thinking about AWS credentials and where to store them in the right way, give a look at Leapp! It takes the responsibility of storing long-term credentials in the system vault, generating/refreshing short-term credentials, and placing them in the right place for the clients to use them.

Still, there is an elementary problem that we need to address, and it’s more on the operational side of things. Once we secured and implemented a tremendous multi-account strategy, how do people access AWS accounts? It turns out there is a fantastic open-source tool that lets you handle that with no effort, and its name is Leapp.

When you have to configure access to multiple AWS accounts using the Assume Role access pattern, it becomes difficult to get rid of all the Named Profiles configuration data and relationships. When you’ve to deal with a complex access scenario, tools like Leapp (https://www.leapp.cloud) come to the rescue! Leapp avoids you to specify relationships between Named Profiles in the config file, as the access methods are stored in the tool-specific configuration file.

Leapp Github repository