top | item 42580821 (no title) ldjb | 1 year ago A terminal doesn't need SSH integration, but it's convenient if it does, to allow you to easily start and manage connections. Is there something inherently unsafe about such an integration? discuss order hn newest Xelynega|1 year ago There's something inherently unsafe with replacing an industry-standard security tool with anything.I don't think it's inconvenient enough to type `ssh -i key_file name@host` that we need to be creating more security risk to skip typing it. wkat4242|1 year ago > I don't think it's inconvenient enough to type `ssh -i key_file name@host` that we need to be creating more security risk to skip typing it.Also, you can easily configure that in your .ssh/config file, even with different options per host or group of hosts.
Xelynega|1 year ago There's something inherently unsafe with replacing an industry-standard security tool with anything.I don't think it's inconvenient enough to type `ssh -i key_file name@host` that we need to be creating more security risk to skip typing it. wkat4242|1 year ago > I don't think it's inconvenient enough to type `ssh -i key_file name@host` that we need to be creating more security risk to skip typing it.Also, you can easily configure that in your .ssh/config file, even with different options per host or group of hosts.
wkat4242|1 year ago > I don't think it's inconvenient enough to type `ssh -i key_file name@host` that we need to be creating more security risk to skip typing it.Also, you can easily configure that in your .ssh/config file, even with different options per host or group of hosts.
Xelynega|1 year ago
I don't think it's inconvenient enough to type `ssh -i key_file name@host` that we need to be creating more security risk to skip typing it.
wkat4242|1 year ago
Also, you can easily configure that in your .ssh/config file, even with different options per host or group of hosts.