-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sshnoports: Add unit tests #104
Comments
Unassigning myself and moving to Triage again ... hoping someone else has capacity to pick this up in this sprint |
@cconstab I was trying to run sshnp, But I got a remote SSH client failure
SHOUT|2023-04-06 11:24:55.364158| sshnpd |@95consistent sync complete SHOUT|2023-04-06 11:27:16.519554| sshnpd |ssh session started from: @aquamarine659 session: 45891ce5-1f0e-4248-a409-a35885cb01b6
dart sshnp.dart -k sshnoports/.atsign/keys/@aquamarine659_key.atKeys -f @aquamarine659 -t @95consistent -h 27d00de9-3719-56b3-82d2-5b97212a9959.swarm0002.atsign.zone -p 2215 -d device1 From the logs, I could see a failure as Remote sshnpd error: Remote SSH Client failure : SSHAuthAbortError(Connection closed before authentication) But at the end, it says notification as delivered FINER|2023-04-06 16:57:17.067081|AtLookup|SENDING: notify:status:91752f94-991c-47e4-aa0b-232c0d7958eb FINER|2023-04-06 16:57:17.332635|OutboundMessageListener|RECEIVED data:delivered |
So the -h and -p should point to the place you are running sshnp.. Currently you have the host and the port of the secondary server which is not where you are running ssh from.. My Host -------------------------> Hosty I want to log into so in this case the -h "my host" and -p "22" hope that helps |
The sshnp repo has lots of clues https://github.com/atsign-foundation/sshnoports |
@cconstab Remote machine:
ngrok (via SSH) (Ctrl+C to quit) Account murali@atsign.com (Plan: Free)
client machine: remote machine: ngrok (via SSH) (Ctrl+C to quit) Account murali@atsign.com (Plan: Free) TCP connection opened murali@murali-Latitude-3460:~/git/at_protocol/sshnoports$ journalctl -fu ssh |
I would make sure that ssh logins are allowed on the remote machine the logs would suggest they are not.. To test on the remote machine try
You should be able to login The other thing I notice is the sshnpd has |
In the remote machine on which sshnpd runs, I ran the ssh service on port 2222. ssh 0 didn't work. We tried a manual ssh from purnima's machine to murali's machine
shaikirfan is the username on Purnima's machine. sshnp.dart also picks this username from envVars I guess. |
Will ping on here once sshnp refactoring is complete so that unit tests can be written, likewise then for sshnpd and sshrvd |
sshnp refactoring is complete; a small number of unit tests were added during PR64 |
no progress during PR65 but work should proceed during PR66 now that refactoring is complete for sshnpd and sshnp |
Refactoring is mostly done, but there are still some bugs that need to be addressed first. Once v3.4.0 is officially released I will update this card. |
Since we now have comprehensive end-to-end test automation, this is not as important; reducing priority to P2 |
Reducing to 5SP |
Lowered priority to P1 now that we've released 4.0.0 |
Will resume in PR 78 |
Will resume in PR80 |
I think this is in a good place for now, e2e tests cover the rest. |
Is your feature request related to a problem? Please describe.
No unit tests currently
Describe the solution you'd like
Need unit tests which, while they do not test the whole thing end to end, can check the logic and behaviour of the atProtocol interactions - the records that are created and updated, the notifications that are sent and received, etc
Describe alternatives you've considered
No response
Additional context
No response
Tasks
The text was updated successfully, but these errors were encountered: