Nicolas Couture

This is not really production quality software, there are no unit tests and it has mostly been a toy project for me to play around and tests different ways to...

Testing SSH seems to be a problem shared by the unit tests of a set of networking libraries. Looking at the referenced fabric tickets (https://github.com/fabric/fabric/issues/185 https://github.com/fabric/fabric/issues/275) I am also in...

Created: - [x] Rename PasswordPromptingCommand to PromptingCommand #3 - [ ] Rename ArgumentValidatingCommand as SSHCommand #4 - [ ] Implement unit tests #5 It's Friday night and I'm using Emoji...

https://pypi.python.org/pypi/MockSSH/1.3

Same as #18 ([comment](https://github.com/ncouture/MockSSH/issues/18#issuecomment-307561012)) --- Thanks for taking the time to share your improvements on MockSSH @ruivapps . Would you be able to write a test to support this feature?...

@ruivapps apologies for the late reply. I will be following Github notifications more closely in the future. I have opened the pull request and have no objection to add you...

@ruivapps I had a few questions about your implementation, notably regarding the non-termination of connections for non-interactive (exec command) sessions after command execution but also about the purpose and/or need...

The only criterias for inclusion we have right now is that this functionality results in the same behavior than using "exec command" on a standard OpenSSH server, which I think...

Well said, and the same is true for MockSSH; it has no notion of command execution, all execution is mocked by named commands that can only do input/output (to some...

The ArgumentValidatingCommand does not support unknown positional arguments, this is a problem in this use case (see examples/mock_cisco.py): > username john password jd03 In order to replace SSHCommand with ArgumentValidatingCommand...