Explore >> Select a destination
|
You are here 
|
github.com | ||
| | | | |
msfjarvis.dev
|
|
| | | | | ? Type of change Bugfix New feature Enhancement Refactoring ? Description Add support for multiple authentication methods by offering password authentication after public key authentication. Along the way, refactor GitOperation to use a (somewhat) proper builder pattern. This uncovered that we were previously not using SSHJ for the case of no authentication, which is now rectified. ? Motivation and Context Fixes #333, fixes #548 and fixes #782 if it works. ? How did you test it? I lack the setup to test ... | |
| | | | |
blog.pshrmn.com
|
|
| | | | | ||
| | | | |
crpt.fyi
|
|
| | | | | Issues for organizations and discussions, repo for debriefs and resources - Call For Proposal · francep2p/community Wiki | |
| | | | |
jmmv.dev
|
|
| | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | ||
