openssh | Development repository for the openssh cookbook | SSH Utils library

close the idle ssh connection if they are idle for more than 5 minutes

This task is surprisingly difficult. OpenSSH itself has no functionality to set a idle-timeout on shell commands, probably for a good reason: killing "idle" shells itself is non-trivial:

• There's multiple ways to define "idleness", e.g., no stdin, no stdout, no I/O activity whatsoever, no CPU consumption etc
• Even when a process is deemed "idle", it's difficult to kill the process and all its child processes that have possibly been created.

Given that, it's not surprising that there's only few solutions for killing idle shell sessions in general. Those that I could find with (little) research rely on background daemons that check the idle status of all processes running on a system (e.g., doinkd/idled, idleout).

One possible solution is to check if any of those solutions can be adapted to enforce an idle timeout on a specific shell session.

Another option is to adapt the OpenSSH source code to support your specific requirement. In principle, OpenSSH should be able to easily access console I/O activity and session duration, so assessing the "idle" property is probably relative easy. As for "killing" the shell and all involved children, running (and killing) the remote shell in a PID namespace is an effective option on Linux systems.

Both options a relatively complex -- so before pursuing them further, I'd further check if there's existing solutions to enforce an idle timeout on a shell session. Using them under OpenSSH will be straightforward.

You can try to configure the temporary cache directory

Use Homebrew's OpenSSH

Imo, it's a bug in Paramiko. It does not handle correctly absence of server-sig-algs extension on the server side.

Try disabling rsa-sha2-* on Paramiko side altogether:

There's a few reasons why environment variables may be different. Chiefly:

1. The user account being used by the runner
2. The powershell profile you're using locally (which will not be used by the runner)
3. Any changes to environment variables made in the runner's config.toml
4. environment variables changed/added through CI/CD variables.

The effective PATH is a combination of both the system environment variables as well as user environment variables. For your runner to reflect the same environment variables that you see locally when running powershell, you must use the same user account, otherwise user environment variables you're seeing may be missing/different based on the user account.

One way to fix differences that may be caused by the user would be to change the user used by the gitlab service

To change the user used by the GitLab runner, go to services -> gitlab-runner -> (right-click) properties -> Log On tab and choose the account the runner should use.

Alternatively, specify this when installing the runner:

For communicating between multiple docker-compose clients, you need to make sure that the containers you want to talk to each other are on the same network.

For example, (edited for brevity) here you have one of the docker-compose.yml

You can say, however ruby sets up to say, git -c core.sshcommand='/usr/bin/ssh -F my.temp.config' and set up your one-shot connection-setup params in that temp config.

OpenSSH uses different formats for private EC keys, the SEC1 (as generated by your Go code), the PKCS#8 or the newer OpenSSH format (as generated with the ssh-keygen command). This is described here, which also contains a more detailed explanation of the OpenSSH format. The SEC1 format is explained e.g. in this post.

The current Go code generates a SEC1 key with wrong header and footer. This turned out to be the cause of the problem! To fix the bug, ECDSA must be replaced by EC in header and footer:

java.lang.UnsatisfiedLinkError: no prism_sw in java.library.path

Means you're definitely missing some dlls from your library path, although this could only be a part of the problem.

When you download javafx sdk for windows from this link, you get a zip with the following structure:

The bin folder contains all the natives you need to run JavaFx (on windows, or the platform you downloaded the sdk for)

Note that you don't always need all the natives, jfxwebkit.dll for example is only needed when you work with javafx-web.

You need to extract them somewhere and add the folder you extracted them in to the library path when you run the java program