v2.0.1

Fix Dockerfile SHAs

Dockerfiles had been pinned to AMD64 SHAs rather than manifest SHAs.

What's Changed

• build(deps): bump dart from 9a6a450 to 7bccbb9 by @dependabot in #47
• build(deps): bump debian from cb1452a to 3859a08 by @dependabot in #48

Full Changelog: v2.0.0...v2.0.1

v2.0.0

Version 2.0.0 Released

Major release brings encrypted acknowledgements between sshnpd and sshnp clients. This enables sshnp to work on very low bandwidth and high latency connections without timeout issues. The only timeout now is if sshnpd fails to respond after 30 seconds.

This work closes #24

Breaking Changes :
sshnpd v2.*.* is backward compatible with 1.*.* sshnp although new features are simply ignored.
sshnp v2.*.* is not backward compatible with 1.*.* sshnpd.
RiscV binaries should be considered in beta as they depends on Dart for RiscV which is itself in beta

What's Changed

• fix: typo in README.md in the directory location of atKeys by @cconstab in #41
• feat: Migrated to release to initiate Docker image build by @cconstab in #42
• build(deps): bump github/codeql-action from 2.1.33 to 2.1.35 by @dependabot in #43
• build(deps): bump debian from 110d5f9 to 3859a08 by @dependabot in #45
• build(deps): bump dart from 7744c20 to f2c0eea by @dependabot in #44
• chore(deps): bump lints from 1.0.1 to 2.0.1 by @dependabot in #37
• chore(deps): bump ssh_key from 0.7.1 to 0.8.0 by @dependabot in #38
• feat: Ack notification of sshnpd daemon back to sshnp client by @cconstab in #46

Full Changelog: v1.1.4...v2.0.0

v1.1.4

Added to sshnp
--local-ssh-options to allow options to the local ssh command to for instance tunnel ports to and from remote devices. Useful for GUI access or streaming content.

Windows Support
sshnp/sshnpd does work on windows but have been removed from the release as setting things up on Windows correctly is very painful to install and maintain. If you need Windows let us know or build and install yourself.

Dockerfile for sshnpd
Reason for work
Docker/Containers at the edge are becoming an easy way to deploy applications and sshnpd in a container allows remotes and secure access to those environments without the normal pain of firewalls/vpns/static IP's. If the container can see the the Internet then you will be able to log into that container.. This is really useful if the device is on a foreign network or cellular network where the IP address cannot be static, or were getting NAT/Firewall ports open is troublesome.

container is automatically built at each push using GitHub Actions and is ready to download on DockerHub at

atsigncompany/sshnpd:latest

v1.1.3

Small change to only SHOUT in the logs unless the -v flag is set. This way scripts using sshnp/d do not get confused with warning or severe error messages that often have no effect on the operation of sshnp.

v1.1.2

Updated binaries due to underlying library updates and more explicit use of the namespace (sshnp)

v1.1.0

Now using the notification decryption options rather than the untidy code that was used in the past.

What's Changed

• Example command lines to use packaged filenames by @cpswan in #8
• Decrypt notification by @cconstab in #9

New Contributors

• @cconstab made their first contribution in #9

Full Changelog: v1.0.3...v1.1.0

v1.0.3

A few bugs found and fixed.
Thanks to @cpswan for the detailed bug reports and ideas for enhancements

What's Changed

• Docs fixes by @cpswan in #5

New Contributors

• @cpswan made their first contribution in #5

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Fixed a few annoying errors in the command line argument testing..

Binary tarballs are all for Linux accept the OSX ones which are for Darwin/Mac, both arm and x86_64

v1.0.0

All known bugs and issues fixed.

But there may be more to find please raise an issue or PR if you find anything

v0.0.3

This releasee tidies up ~/.ssh files after using sshnp or sshnpd

Full Changelog: v0.0.2...v0.0.3