You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2022. It is now read-only.
I have found that when I use grep to filter the storm list output, by bash terminal looses the previous terminal colour when it encounters a host entry that uses custom options (for example specifying deprecated ciphers for legacy equipment) and falls back to grey colour.
Is this an minor issue with storm ssh or just a known bug with bash/grep (likely)?
The command I use which is triggering this is: storm list | grep HOST
An example of a .ssh/config entry that causes this when I use the following:
Host HOST
hostname hostname
user admin
port 22
ciphers aes256-cbc
My system is fully up-to-date, however I am running Ubuntu 19.04 and the below list is my venv (pytools) pip3 module list used for storm ssh:
I have found that when I use grep to filter the storm list output, by bash terminal looses the previous terminal colour when it encounters a host entry that uses custom options (for example specifying deprecated ciphers for legacy equipment) and falls back to grey colour.
Is this an minor issue with storm ssh or just a known bug with bash/grep (likely)?
The command I use which is triggering this is:
storm list | grep HOST
An example of a .ssh/config entry that causes this when I use the following:
My system is fully up-to-date, however I am running Ubuntu 19.04 and the below list is my venv (pytools) pip3 module list used for storm ssh:
The text was updated successfully, but these errors were encountered: