[GH-ISSUE #437] Login with user@domain #116

New issue

Closed

opened 2026-05-07 00:19:07 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:19:07 +02:00

Owner

Originally created by @hanunes on GitHub (Dec 19, 2023).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/437

We have some devices that only accept the username with the appended domain (user@domain).

If we try to use this combo, the bastion says "Remote user name 'user@domain' seems invalid".

Unfortunately, I've looked at the device's config, but haven't found a way to change the behavior. Is this something that can be done on the bastion side?

Originally created by @hanunes on GitHub (Dec 19, 2023). Original GitHub issue: https://github.com/ovh/the-bastion/issues/437 We have some devices that only accept the username with the appended domain (user@domain). If we try to use this combo, the bastion says "Remote user name 'user@domain' seems invalid". Unfortunately, I've looked at the device's config, but haven't found a way to change the behavior. Is this something that can be done on the bastion side?

BreizhHardware closed this issue

2026-05-07 00:19:07 +02:00

BreizhHardware commented

2026-05-07 00:19:08 +02:00

Author

Owner

@speed47 commented on GitHub (Jan 19, 2024):

Thanks for your report!

The @ is not an allowed character for accounts on Linux/BSD or more generally POSIX systems, which are historically the main targets for the bastion, which is why it's not allowed as a remote user name.

However, if some devices that have an SSH daemon expect this format, this should be doable, we'd however have to check first that this doesn't have side effects, as the @ is usually used for SSH as a separator between the login and the host, as in ssh user@host.

What kind of device do you have that accepts such format for users logging in to SSH?

@speed47 commented on GitHub (Jan 19, 2024): Thanks for your report! The @ is not an allowed character for accounts on Linux/BSD or more generally POSIX systems, which are historically the main targets for the bastion, which is why it's not allowed as a remote user name. However, if some devices that have an SSH daemon expect this format, this should be doable, we'd however have to check first that this doesn't have side effects, as the @ is usually used for SSH as a separator between the login and the host, as in `ssh user@host`. What kind of device do you have that accepts such format for users logging in to SSH?

BreizhHardware commented

2026-05-07 00:19:08 +02:00

Author

Owner

@hanunes commented on GitHub (Jan 22, 2024):

Good afternoon, we have Huawei OLTs that need this format specifically. The idea is not to have the bastion user with an @ at the system level, but just allow the ssh command within the bastion to this host with that format.

@hanunes commented on GitHub (Jan 22, 2024): Good afternoon, we have Huawei OLTs that need this format specifically. The idea is not to have the bastion user with an @ at the system level, but just allow the ssh command within the bastion to this host with that format.

BreizhHardware referenced this issue

2026-05-07 00:19:59 +02:00

[PR #116] [MERGED] fix: global-log: directly set proper perms on file creation #249