uriagassi / sash Goto Github PK

Fantastic code... was building my own when stumbled across this.

We have tended to not allow ssh access into our ec2 instances from any external interface, forcing us to tunnel through a gateway. Any thoughts on how to add this to sash? I'd be up for taking a stab at it if you can point me where it might be added

--profile flag

Just tried this with ZSH and got a bunch of errors:

sash:22: bad option: -a
_get_data:20: bad option: -a
_get_data:declare:21: no such variable: pems
_get_data:shift:6: shift count must be <= $#
_get_data:20: bad option: -a
_get_data:declare:21: no such variable: ips
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:20: bad option: -a
_get_data:declare:21: no such variable: hosts
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:20: bad option: -a
_get_data:declare:21: no such variable: resource_ids
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:20: bad option: -a
_get_data:declare:21: no such variable: users
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:shift:6: shift count must be <= $#
_get_data:20: bad option: -a
_get_data:declare:21: no such variable: private_ips
sash:31: bad substitution

(Bash works fine though.)

see http://stackoverflow.com/a/4342085

basically if using ubuntu@ you will get Permission denied (publickey) need the user to be ec2-user

Your project is conflicting with the old (but still alive and used) stand alone shell sash. Perhaps your README.md should mention that it is unrelated to that well known shell.

We're implementing some security practices to prevent sharing the AWS pem files among multiple users. We are putting public keys from our developers into the ~/.ssh/authorized_keys file.

So it would be an enhancement to use keys other than the AWS private pem files to connect. Would this be difficult or does sash already do this?

When running sash with no params it would be helpful to show a short help text (usage)

hi, wow this is a great piece of help; though I have 2 questions

*you say enable SASH_USE_VPN=true goes to private IP; I have so:

Dominiks-MacBook-Air:sash dsimm$ env | grep -i vpn
SASH_USE_VPN=true
Dominiks-MacBook-Air:sash dsimm$ clear_sash
Dominiks-MacBook-Air:sash dsimm$ sash production-main-ingestion
Connecting to production-main-ingestion (52.16.5.182)

I would expect a 10.x.x.x IP

2.) any chance to not use .pem files to connect? just with ssh private key?

connecting to demo-main-encoder (54.171.70.3)

• ssh -i /Users/dsimm/.aws/kuba.pem [email protected]
  Warning: Identity file /Users/dsimm/.aws/kuba.pem not accessible: No such file or directory.

I don't have "kuba.pem" key this is the key of the person who set it up; but on the host itself my public key is there..