When a client connects to Bitbucket Server via HTTP, the user agent is included in the access logs. However, when a client connects via SSH, the client version is not logged.
As an example of where this would be useful, recent versions of TortoiseGit have upgraded to Plink 0.68, which can cause OutOfMemoryErrors in Bitbucket Server (see BSERV-10100). However, since the client version is not included in the access logs it can be difficult to track such clients down, especially for a busy server with many clients.
[BSERV-10141] Include SSH client version in access logs
Workflow | Original: JAC Suggestion Workflow [ 3397494 ] | New: JAC Suggestion Workflow 3 [ 3624981 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: BSERV Suggestions Workflow [ 3391721 ] | New: JAC Suggestion Workflow [ 3397494 ] |
Workflow | Original: Stash Workflow - Restricted [ 2432172 ] | New: BSERV Suggestions Workflow [ 3391721 ] |
Issue Type | Original: Development Task [ 12 ] | New: Suggestion [ 10000 ] |
Priority | Original: Low [ 4 ] | |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Remote Link |
New:
This issue links to "Bitbucket Server › 4.14.X › |
Remote Link |
New:
This issue links to "Bitbucket Server › Pull Request Build with Coverage › |
Remote Link |
New:
This issue links to "Bitbucket Server › Pull Request Build › |
Fix Version/s | New: 5.4.0 [ 73619 ] | |
Fix Version/s | New: 4.14.10 [ 74410 ] | |
Fix Version/s | New: 5.0.8 [ 74411 ] | |
Fix Version/s | New: 5.1.6 [ 74412 ] | |
Fix Version/s | New: 5.2.4 [ 74413 ] | |
Fix Version/s | New: 5.3.2 [ 74414 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To be reviewed [ 10026 ] | New: Closed [ 6 ] |
Remote Link |
New:
This issue links to "Bitbucket Server › 4.14.X › |
Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |
The remote client's version has been added to the access logs:
"SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.3" is the remote client's version.