You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to propose a feature request - it requires no coding at all!
I recently configured a locked-down jump box. Lxterminal was the only terminal emulator I could find which would allow a user to run programs when their account is configured with no login (shell = /sbin/nologin). That meant I could configure a minimal desktop environment which still allowed the user to ssh to other machines and potentially run a restricted set of terminal based programs. The continued availability of this behaviour to the function and security of my bastion host.
My feature request is that this is ratified as a behaviour of lxterminal.
I've not seen any documentation for lxterminal saying that this is how it behaves. Conversely I've not seen any documentation for the other terminals I looked at to describe how they would behave in this regard. Since so many other terminals do not behave this way, I suspect there may be an underlying security reason for this / that this behaviour in lxterminal might be perceived as a defect. If that is the case, then I ask that any change to the default behaviour includes the ability to override the default and continue to operate as-is.
The text was updated successfully, but these errors were encountered:
I want to propose a feature request - it requires no coding at all!
I recently configured a locked-down jump box. Lxterminal was the only terminal emulator I could find which would allow a user to run programs when their account is configured with no login (shell = /sbin/nologin). That meant I could configure a minimal desktop environment which still allowed the user to ssh to other machines and potentially run a restricted set of terminal based programs. The continued availability of this behaviour to the function and security of my bastion host.
My feature request is that this is ratified as a behaviour of lxterminal.
I've not seen any documentation for lxterminal saying that this is how it behaves. Conversely I've not seen any documentation for the other terminals I looked at to describe how they would behave in this regard. Since so many other terminals do not behave this way, I suspect there may be an underlying security reason for this / that this behaviour in lxterminal might be perceived as a defect. If that is the case, then I ask that any change to the default behaviour includes the ability to override the default and continue to operate as-is.
The text was updated successfully, but these errors were encountered: