Add a way to get the connection addresses

[kruton]

The local and remote socket address is used for tracking connectivity in ConnectBot.

[Copilot]

Pull request overview

This PR adds access to the underlying connection’s local and remote socket addresses (for ConnectBot connectivity tracking) and wires those addresses into ConnectionInfo, with accompanying unit/integration tests.

Changes:

• Add Connection#getLocalSocketAddress() / getRemoteSocketAddress() APIs backed by TransportManager.
• Store local/remote socket addresses on ConnectionInfo during key exchange completion.
• Add unit and OpenSSH integration tests covering the new behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/main/java/com/trilead/ssh2/Connection.java	Exposes local/remote socket addresses via new public methods.
src/main/java/com/trilead/ssh2/transport/TransportManager.java	Provides socket address accessors from the underlying Socket.
src/main/java/com/trilead/ssh2/transport/KexManager.java	Populates socket address fields into ConnectionInfo on NEWKEYS.
src/main/java/com/trilead/ssh2/ConnectionInfo.java	Adds localSocketAddress and remoteSocketAddress fields.
src/test/java/com/trilead/ssh2/ConnectionTest.java	Adds unit tests for “not connected” error behavior.
src/test/java/com/trilead/ssh2/OpenSSHCompatibilityTest.java	Adds integration test validating socket address access and propagation to ConnectionInfo.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud