If you are seeing the "Bad configuration option: usekeychain" error during a git command, it may be because Git isn't running the Apple-installed version of SSH. To ensure that you know which version of ssh is called from git, set an environment variable:

GIT_SSH="/usr/bin/ssh"

More generally, any wrapper of SSH could cause this kind of error. So I'd suggest checking which SS

The documentation is pretty straightforward, I only need to do the following:
echo -n "mypassword" | docker run -i --rm atmoz/makepasswd --crypt-md5 --clearfrom=-
then copy the output $1$1TWZh6FZ$XNf2mNVT8HLIXEjAqGnZe/ to the arguments then append :e,

here is my whole argument:
tester:$1$1TWZh6FZ$XNf2mNVT8HLIXEjAqGnZe/:e

its not working, but an unencrypted password like `tester:mypa

The config file is currently mandatory. Some parts of cashierd can be configured via environment variables (I'm really not sure why I did this) but ideally the config should be entirely settable using cmdline flags and the config file should be optional.

This bastion host is bloody useful and will save our team an enormous effort, thanks!

I had a little trouble working out how to run this on ECS so I'm posting my cloudformation template here for anyone that is looking to do the same:

AWSTemplateFormatVersion: 2010-09-09
Description: Bastion

Parameters:

  KeyPairName:
    Description: >-
      Enter a Public/private key pair. If

We should support

• a known_hosts of registered hosts (what we have right now)
• a known_hosts with the CAs used for all currently issued certs (today, we only support one, so just that)
• or both.

Sharkey-client should grab both by default.

I just had an issue that I was unable to execute neither wsl-ssh-pageant or wsl-ssh-pageant-gui. Both just exited immediately, without any error message or log file produced. It was quite hard to debug and it took me some time to notice that the SSH_AUTH_SOCK file already existed. Probably some leftover from a previous run. I just deleted the file and it was working again.

It would be goo

Over the years, I've come up with a way to accomplish this + there are problems.

Likely there's a better way. Love to hear how other people do this.

My steps using Ubuntu with the following directory structure for my LXD hosting clients...

/sites/$client/$site/{wordpress,logs,htdocs}

1. First set a www-data ACL, so any newly created files/dirs inherit www-data in addition to creator ow

• enabling offline bruteforcing
• vulnerable to shoulder surfing
• explain this is the reason we only do signing keys (for authentication) and not ECDH keys for encryption
• et cetera