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
Description:
I would like to request support for comments in the exclusion file when using sshuttle with the -X option. Currently, comments are not recognized, and it would be helpful to have the ability to add comments for better organization and documentation purposes.
Expected Behavior:
I expect that lines starting with a designated character, such as "#" or "//", should be treated as comments and ignored by sshuttle when parsing the exclusion file.
Steps to Reproduce:
Create an exclusion file with domains to exclude.
Add comment lines starting with a designated character.
Run sshuttle with the exclusion file using the -X option.
Observe that comments are not ignored, and the tool tries to interpret them as domains.
Additional Information:
I have seen other tools and scripts that support comments in configuration files using a designated character at the beginning of the line.
The ability to include comments would greatly improve the readability and maintainability of exclusion files.
Environment:
sshuttle version: 1.1.1
Operating System: Ubuntu
Please let me know if any further information is needed. Thank you for considering this feature request!
The text was updated successfully, but these errors were encountered:
Description:
I would like to request support for comments in the exclusion file when using
sshuttle
with the-X
option. Currently, comments are not recognized, and it would be helpful to have the ability to add comments for better organization and documentation purposes.Expected Behavior:
I expect that lines starting with a designated character, such as "#" or "//", should be treated as comments and ignored by
sshuttle
when parsing the exclusion file.Steps to Reproduce:
sshuttle
with the exclusion file using the-X
option.Additional Information:
Environment:
sshuttle
version: 1.1.1Please let me know if any further information is needed. Thank you for considering this feature request!
The text was updated successfully, but these errors were encountered: