#rust#cli#command_line_interface#command_line_tool#dns#icmp#linux#macos#mtr#netbsd#network#networking#ping#ratatui#rust#rustlang#tool#traceroute#tui#tui_rs#windows
Trippy is a powerful tool that combines traceroute and ping functions to help you analyze network problems easily. It works on Linux, BSD, macOS, and Windows, and you can install it through many package managers or directly with commands like `cargo install trippy`. Running a simple trace is as easy as typing `sudo trip example.com`. Trippy offers detailed network tracing with features like multipath strategies and unprivileged modes, making it flexible for different needs. Using Trippy helps you quickly find where network issues occur, saving time and improving troubleshooting efficiency. Full guides and documentation are available online to get you started smoothly.
https://github.com/fujiapple852/trippy
https://pypi.python.org/pypi/oauthlib
A generic, spec-compliant, thorough implementation of the #OAuth request-signing logic for python
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provide support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
https://aaronparecki.com/2012/07/29/2/oauth2-simplified#others
OAuth 2 Simplified
Sun, Jul 29, 2012 9:30am -07:00
Many services such as #Facebook, #Github, and #Google have already deployed OAuth 2 servers, and deployed implementations win.
The #OAuth 2 spec itself leaves many decisions up to the implementor. Instead of describing all possible decisions that need to be made to successfully implement OAuth 2, this post makes decisions that are appropriate for most implementations.
This post is an attempt to describe OAuth 2 in a simplified format to help developers and service providers implement the protocol.