sshw | SSH client in a browser , via a JEE webapp | SSH library

by the-james-burton Java Version: 0.0.4-SNAPSHOT License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | sshw Summary

sshw is a Java library typically used in Networking, SSH, Docker applications. sshw has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

A regular SSH connection is done over TCP port 22. However in most corporate environments, only ports 80 and 443 are open to the internet (for HTTP and HTTPS respectively). This means that is it not possible to use a tool like putty to open an SSH session to a server on the internet when inside a corporate environment. In this case, port 80 or 443 could be repurposed for SSH assuming the corporate firewall allows this. However, if this server is also hosting JEE webapps, then it is very difficult (and could be impossible) to get an interactive SSH session to such a server from a corporate environment. This is where SSHW steps in. It is designed to offer interactive SSH sessions from a JEE container alongside any other webapps that may be deployed on the server. The alternative is to use a web SSH client, but do you trust them with your root passwords?.

Support

Quality

Security

License

Reuse

Support

sshw has a low active ecosystem.

It has 13 star(s) with 0 fork(s). There are 4 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 3 have been closed. On average issues are closed in 1 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of sshw is 0.0.4-SNAPSHOT

Quality

sshw has 0 bugs and 0 code smells.

Security

sshw has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sshw code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

sshw is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sshw releases are available to install and integrate.

Build file is available. You can build the component from source.

sshw saves you 569 person hours of effort in developing the same functionality from scratch.

It has 1329 lines of code, 51 functions and 30 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed sshw and discovered the below as its top functions. This is intended to give you an instant insight into sshw implemented functionality, and help decide if they suit your requirements.

Login using username and password
Logs out
Closes the session
Configures this webSecurity instance
Configures Http Security
Configure the ssh authentication provider
Decrypt the message with the specified password
Generates a PBKDF2 with the given password
Set the web socket session
Set websocket session
Enable default servlet handling
Logout user
Log a user
Handles the login request
Add the resource handlers to the registry
Logout the given username
Login with username and password
Handle the login request
Registers the servlet
Authenticate with username and password
Handles a websocket message
Handles connection closed
Main loop
Override handleRequest to handle the session id
Add view controllers to the given registry
Encrypt a string with a password

Get all kandi verified functions for this library.

sshw Key Features

No Key Features are available at this moment for sshw.

sshw Examples and Code Snippets

No Code Snippets are available at this moment for sshw.

Community Discussions

Trending Discussions on SSH

How to fix? "kex_exchange_identification: read: Connection reset by peer"

BitBucket: You are using an account password for Git over HTTPS

Connection reset when using jsch to connect to an sftp server hosted in azure

Paramiko authentication fails with "Agreed upon 'rsa-sha2-512' pubkey algorithm" (and "unsupported public key algorithm: rsa-sha2-512" in sshd log)

AWX all jobs stop processing and hang indefinitely -- why

How to Generate ECDSA Key Pair for SSH in Go?

Separate gitconfig by directory

Server SSH Fingerprint Failed to Verify

What is the purpose of the "[fingerprint]" option during SSH host authenticity check?

gitea: Built-in ssh server not starting when sshd server running

QUESTION

How to fix? "kex_exchange_identification: read: Connection reset by peer"

Asked 2022-Mar-30 at 10:07

I want to copy data with scp in GitLab pipeline using PRIVATE_KEY error is :

...

ANSWER

Answered 2021-Sep-30 at 19:40

kex_exchange_identification: read: Connection reset by peer

Source https://stackoverflow.com/questions/69394001

QUESTION

BitBucket: You are using an account password for Git over HTTPS

Asked 2022-Mar-01 at 19:41

Today I got the following message when I used Git + BitBucket on MacOS while pushing a new branch to BitBucket.

You are using an account password for Git over HTTPS.

Beginning March 1, 2022, users are required to use app passwords remote: for Git over HTTPS. To avoid any disruptions, change the password used in your Git client remote: to an app password. Note, these credentials may have been automatically stored in your Git client and/or a credential manager such as Git Credential Manager (GCM).'

...

ANSWER

Answered 2022-Jan-31 at 09:00

In my case, I used BitBucket via HTTPS and not via SSH. Therefore I had to change it.

Follow this guide to create and add a new SSH key.
Follow this guide to switch from HTTPS to SSH.

Unrelated and optional:

While you are at this security related task, activate 2FA in your BitBucket security settings.

Source https://stackoverflow.com/questions/70832548

QUESTION

Connection reset when using jsch to connect to an sftp server hosted in azure

Asked 2022-Feb-18 at 18:21

we are currently working with a cloud product that uses JSCH internally to connect to external sftp sources. Im investigating an connection reset exception that we are getting when trying to connect to azure sftp.

Using wireshark i determined that the problem occurs after we send the Client: Key Exchange Init. Establishing the same connection with filezilla we dont have this issue.

comparing the packages from jsch and filezilla i didn't see an obivious issue, but im not an expert on the ssh protocol. im gonna post both requests below if somebody could give me any pointers it would be greatly appreciated.

Request with JSCH (not working)

Request with Filezilla (working)

Response with Filezilla (working)

See below for the log output:

...

ANSWER

Answered 2022-Feb-03 at 08:09

i wanted to post a quick update for anybody that is having the same issue, i opened a similiar question on the microsoft q&a site and looks like it's an issue on the azure side that they are working on fixing for GA Microsoft Q&A

Source https://stackoverflow.com/questions/70878675

QUESTION

Paramiko authentication fails with "Agreed upon 'rsa-sha2-512' pubkey algorithm" (and "unsupported public key algorithm: rsa-sha2-512" in sshd log)

Asked 2022-Jan-13 at 14:49

I have a Python 3 application running on CentOS Linux 7.7 executing SSH commands against remote hosts. It works properly but today I encountered an odd error executing a command against a "new" remote server (server based on RHEL 6.10):

encountered RSA key, expected OPENSSH key

Executing the same command from the system shell (using the same private key of course) works perfectly fine.

On the remote server I discovered in /var/log/secure that when SSH connection and commands are issued from the source server with Python (using Paramiko) sshd complains about unsupported public key algorithm:

userauth_pubkey: unsupported public key algorithm: rsa-sha2-512

Note that target servers with higher RHEL/CentOS like 7.x don't encounter the issue.

It seems like Paramiko picks/offers the wrong algorithm when negotiating with the remote server when on the contrary SSH shell performs the negotiation properly in the context of this "old" target server. How to get the Python program to work as expected?

Python code

...

ANSWER

Answered 2022-Jan-13 at 14:49

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:

Source https://stackoverflow.com/questions/70565357

QUESTION

AWX all jobs stop processing and hang indefinitely -- why

Asked 2021-Dec-21 at 14:42

Problem

We've had a working Ansible AWX instance running on v5.0.0 for over a year, and suddenly all jobs stop working -- no output is rendered. They will start "running" but hang indefinitely without printing out any logging.

The AWX instance is running in a docker compose container setup as defined here: https://github.com/ansible/awx/blob/5.0.0/INSTALL.md#docker-compose

Observations

Standard troubleshooting such as restarting of containers, host OS, etc. hasn't helped. No configuration changes in either environment.

Upon debugging an actual playbook command, we observe that the command to run a playbook from the UI is like the below:

ssh-agent sh -c ssh-add /tmp/awx_11021_0fmwm5uz/artifacts/11021/ssh_key_data && rm -f /tmp/awx_11021_0fmwm5uz/artifacts/11021/ssh_key_data && ansible-playbook -vvvvv -u ubuntu --become --ask-vault-pass -i /tmp/awx_11021_0fmwm5uz/tmppo7rcdqn -e @/tmp/awx_11021_0fmwm5uz/env/extravars playbook.yml

That's broken down into three commands in sequence:

ssh-agent sh -c ssh-add /tmp/awx_11021_0fmwm5uz/artifacts/11021/ssh_key_data
rm -f /tmp/awx_11021_0fmwm5uz/artifacts/11021/ssh_key_data
ansible-playbook -vvvvv -u ubuntu --become --ask-vault-pass -i /tmp/awx_11021_0fmwm5uz/tmppo7rcdqn -e @/tmp/awx_11021_0fmwm5uz/env/extravars playbook.yml

You can see in part 3, the -vvvvv is the debugging argument -- however, the hang is happening on command #1. Which has nothing to do with ansible or AWX specifically, but it's not going to get us much debugging info.

I tried doing an strace to see what is going on, but for reasons given below, it is pretty difficult to follow what it is actually hanging on. I can provide this output if it might help.

Analysis

So one natural question with command #1 -- what is 'ssh_key_data'?

Well it's what we set up to be the Machine credential in AWX (an SSH key) -- it hasn't changed in a while and it works just fine when used in a direct SSH command. It's also apparently being set up by AWX as a file pipe:

prw------- 1 root root 0 Dec 10 08:29 ssh_key_data

Which starts to explain why it could be potentially hanging (if nothing is being read in from the other side of the pipe).

Running a normal ansible-playbook from command line (and supplying the SSH key in a more normal way) works just fine, so we can still deploy, but only via CLI right now -- it's just AWX that is broken.

Conclusions

So the question then becomes "why now"? And "how to debug"? I have checked the health of awx_postgres, and verified that indeed the Machine credential is present in an expected format (in the main_credential table). I have also verified that can use ssh-agent on the awx_task container without the use of that pipe keyfile. So it really seems to be this piped file that is the problem -- but I haven't been able to glean from any logs where the other side of the pipe (sender) is supposed to be or why they aren't sending the data.

...

ANSWER

Answered 2021-Dec-13 at 04:21

Had the same issue starting this Friday in the same timeframe as you. Turned out that Crowdstrike (falcon sensor) Agent was the culprit. I'm guessing they pushed a definition update that is breaking or blocking fifo pipes. When we stopped the CS agent, AWX started working correctly again, with no issues. See if you are running a similar security product.

Source https://stackoverflow.com/questions/70320452

QUESTION

How to Generate ECDSA Key Pair for SSH in Go?

Asked 2021-Dec-15 at 18:14

I'm trying to generate ECDSA Key Pair for SSH with Go, but I find that the private key format is different from ssh-keygen and can't be accepted by GitHub.

Here's the 256-bit key pair generated via ssh-keygen -t ecdsa -b 256:

...

ANSWER

Answered 2021-Dec-15 at 18:14

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:

Source https://stackoverflow.com/questions/70353152

QUESTION

Separate gitconfig by directory

Asked 2021-Nov-20 at 09:48

I have 2 different github accounts, 1 for work and 1 for personal projects. On my laptop, I created 2 different directories to clone my Github repositories:

Perso: /Users/pierre-alexandre/Documents/perso

Work: /Users/pierre-alexandre/Documents/work

Then, I generated 2 different SSH keys on /Users/pierre-alexandre/.ssh and added each .pub key on their respective Github repository. At the end this is what my /Users/pierre-alexandre/.ssh folder looks like:

...

ANSWER

Answered 2021-Nov-20 at 09:48

Git just runs ssh to connect to a host. Once connected, Git has that ssh run an appropriate Git command on their end, to handle the fetch or push operation. But the entire authentication process—determining who you are and deciding whether you have access—is wholly up to ssh and Git plays no real part in this process.

Your ssh -Tv is therefore the crucial debug output here. We see that your connection to github fails to authenticate as you, after trying these keys:

Source https://stackoverflow.com/questions/70044276

QUESTION

Server SSH Fingerprint Failed to Verify

Asked 2021-Oct-28 at 22:30

I've got a local Swift Package Manager package that uses a private Github repo as a dependency. When I open the local package with Xcode, it fails to “Resolve Packages” with this error:

Error while fetching remote repository: git@github.com:mayoff/Preamble.git

Server SSH Fingerprint Failed to Verify

However, if I use the command line swift program, it can clone the private repo. For example, I can run swift package show-dependencies in the local package's directory without complaint. I can also successfully clone the remote package repo with git clone. So it's not a problem with my .known_hosts file or my SSH key.

How do I fix Xcode's complaint?

...

ANSWER

Answered 2021-Oct-28 at 22:30

So it turns out the “Server SSH Fingerprint Failed to Verify” error message in Xcode's log navigator is double-clickable. Who'd have guessed?

Anyway, double-clicking the error message brought up a dialog box that let me tell Xcode to trust the Github server:

After I clicked the Trust button, Xcode was able to clone the remote repo.

Source https://stackoverflow.com/questions/69761667

QUESTION

What is the purpose of the "[fingerprint]" option during SSH host authenticity check?

Asked 2021-Oct-25 at 12:12

when connecting to a git repository using SSH for the first time, it is asked to confirm the authenticity of the host according to its fingerprint:

...

ANSWER

Answered 2021-Oct-22 at 12:43

each ssh server have host ssh keys, which are used for

auth host and later check that you are connecting to the same host
to establish secure connection (exchange credentials in secure way)

So first time you are connecting to any ssh server, you will get public key and fingerprint of this key, and proposition to store fingerprint in "known hosts" file.

fingerprint is a new option just in addition to "yes", so you can provide fingerprint manually if you have received it in other way. https://github.com/openssh/openssh-portable/commit/05b9a466700b44d49492edc2aa415fc2e8913dfe

seems manpages is not updated yet.

Source https://stackoverflow.com/questions/69675690

QUESTION

gitea: Built-in ssh server not starting when sshd server running

Asked 2021-Oct-23 at 13:00

I have a problem with my gitea version 1.15.5 running on my raspberry pi. I appears that the built in ssh server is not starting:

...

ANSWER

Answered 2021-Oct-23 at 13:00

After some more googling, I found the solution myself:

If there is an sshd server running, gitea does not automatically start its built-in ssh server. Instead, you have to force it by adding this line under [server] in the app.ini configuration:

Source https://stackoverflow.com/questions/69688288

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sshw

You can download it from GitHub.
You can use sshw like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the sshw component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: