starred/sshsrv
1
0
Fork 0
mirror of https://github.com/Crosse/sshsrv.git synced 2026-04-25 03:45:55 +03:00
Code Issues 2 Projects Releases 2 Packages Wiki Activity

[GH-ISSUE #4] Cannot use sshsrv username@example.com #3

New issue
Closed
opened 2026-02-26 17:45:08 +03:00 by kerem · 4 comments
kerem commented 2026-02-26 17:45:08 +03:00
Owner
Copy link

Originally created by @UlyssesZh on GitHub (Oct 5, 2022).
Original GitHub issue: https://github.com/Crosse/sshsrv/issues/4

Originally assigned to: @Crosse on GitHub.

If I use sshsrv username@example.com, the wrapper will not look up for SRV records and behaves identically as ssh username@example.com. I have to use sshsrv example.com -l username instead to make it look up for SRV records.
It seems that this project has not been maintained for a long time, but this is a rather low-hanging fruit, so I hope someone may fix this.

Originally created by @UlyssesZh on GitHub (Oct 5, 2022). Original GitHub issue: https://github.com/Crosse/sshsrv/issues/4 Originally assigned to: @Crosse on GitHub. If I use `sshsrv username@example.com`, the wrapper will not look up for SRV records and behaves identically as `ssh username@example.com`. I have to use `sshsrv example.com -l username` instead to make it look up for SRV records. It seems that this project has not been maintained for a long time, but this is a rather low-hanging fruit, so I hope someone may fix this.
kerem closed this issue 2026-02-26 17:45:08 +03:00
kerem commented 2026-02-26 17:45:08 +03:00
Author
Owner
Copy link

@Crosse commented on GitHub (Oct 5, 2022):

This is what I get when I use the user@host format:

$ ./sshsrv -v seth@my.host.org
Found 1 SRV record(s) for _ssh._tcp.my.host.org.
Record 0:       0 0 2022 my.host.org.
Target for my.host.org is my.host.org:2022
command: /opt/pkg/bin/ssh -p 2022 -v -l seth my.host.org
[…]

Would you mind running the command with -v and providing that output? Redactions are fine, and I only need to see what I have above.

Thanks for the report!

<!-- gh-comment-id:1268937766 --> @Crosse commented on GitHub (Oct 5, 2022): This is what I get when I use the `user@host` format: ``` $ ./sshsrv -v seth@my.host.org Found 1 SRV record(s) for _ssh._tcp.my.host.org. Record 0: 0 0 2022 my.host.org. Target for my.host.org is my.host.org:2022 command: /opt/pkg/bin/ssh -p 2022 -v -l seth my.host.org […] ``` Would you mind running the command with `-v` and providing that output? Redactions are fine, and I only need to see what I have above. Thanks for the report!
kerem commented 2026-02-26 17:45:08 +03:00
Author
Owner
Copy link

@UlyssesZh commented on GitHub (Oct 5, 2022):

This is what I get when I use the user@host format:

$ ./sshsrv -v seth@my.host.org
Found 1 SRV record(s) for _ssh._tcp.my.host.org.
Record 0:       0 0 22 my.host.org.
Target for my.host.org is my.host.org:22
command: /opt/pkg/bin/ssh -p 22 -v -l seth my.host.org
[…]

Would you mind running the command with -v and providing that output? Redactions are fine, and I only need to see what I have above.

Thanks for the report!

Oh, the SRV lookup is good. What I have found is actually another bug: with sshsrv user@example.com, the username is read as  user instead of user (with an extra space in front).

<!-- gh-comment-id:1268944072 --> @UlyssesZh commented on GitHub (Oct 5, 2022): > This is what I get when I use the `user@host` format: > ``` > $ ./sshsrv -v seth@my.host.org > Found 1 SRV record(s) for _ssh._tcp.my.host.org. > Record 0: 0 0 22 my.host.org. > Target for my.host.org is my.host.org:22 > command: /opt/pkg/bin/ssh -p 22 -v -l seth my.host.org > […] > ``` > > Would you mind running the command with `-v` and providing that output? Redactions are fine, and I only need to see what I have above. > > Thanks for the report! Oh, the SRV lookup is good. What I have found is actually another bug: with `sshsrv user@example.com`, the username is read as <code>&nbsp;user</code> instead of `user` (with an extra space in front).
kerem commented 2026-02-26 17:45:08 +03:00
Author
Owner
Copy link

@Crosse commented on GitHub (Oct 18, 2022):

Ah, I see. It should be fixed now. Let me know if it works for you!

<!-- gh-comment-id:1282613239 --> @Crosse commented on GitHub (Oct 18, 2022): Ah, I see. It should be fixed now. Let me know if it works for you!
kerem commented 2026-02-26 17:45:08 +03:00
Author
Owner
Copy link

@Crosse commented on GitHub (Oct 18, 2022):

I also added releases, so you can download a pre-built binary now. Feel free to reopen this if your issue isn't resolved. Thanks!

<!-- gh-comment-id:1282640105 --> @Crosse commented on GitHub (Oct 18, 2022): I also added releases, so you can download a pre-built binary now. Feel free to reopen this if your issue isn't resolved. Thanks!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.0.2
v1.0.1
v1.0
Labels
Clear labels   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

No labels
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sshsrv#3
No description provided.