Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test #248

Closed
wants to merge 2,194 commits into from
Closed

test #248

wants to merge 2,194 commits into from

Conversation

zhoutt96better
Copy link

No description provided.

Lyor Goldstein and others added 30 commits March 26, 2021 09:46
…lback to DH group exchange using SHA-1 if no suitable primes found for SHA-256
SftpInputStreamAsync.transferTo must not have the @OverRide annotation;
it's an override only from JAva 11 on.
If the server had announced via server-sig-algs which signature
algorithms it supports, UserAuthPubKey tries the known algorithms
first. If authentication with such a known signature algorithm fails,
there is no point trying other algorithms.

Trying different signature algorithms may make sense only if the client
doesn't know which algorithms the server supports.
…eflect the use of a property to govern fallback mode
Install a DefaultClientKexExtensionHandler by default.
When the peer closes the channel, just reply with a CLOSE message.
Do not send an EOF before the CLOSE. See RFC 4254, section 5.3.[1]

[1] https://tools.ietf.org/html/rfc4254#section-5.3
…Utils#resolveDefaultClass in SecurityProviderRegistrars (apache#189)

Signed-off-by: Grzegorz Grzybek <gr.grzybek@gmail.com>
Rename the method to getCertPubKey() in preparation of using the class
also for client certificate pubkey login.
Drop the restriction to host keys only in OpenSshCertificate.

Add comparison of OpenSshCertificate taking into account the public
key of the certificates, their serial number, and their signatures.

Add a signature algorithm map to be able to choose the correct
signature algorithm name during pubkey authentication.

Also-by: Alex Sherwin <alex-sherwin@users.noreply.github.com>
Add a unit test exercising authentication with all supported *-cert
key types against a real OpenSSH server run in a docker container.

The OpenSSH server runs in an Alpine container and is primed with two
host keys, selectable via an environment variable, and two users. It
supports pubkey and password authentication.

The test case uses org.testcontainers to build a cached docker image
and to run and teardown the docker container instance. The test uses
the Apache MINA sshd client using client certificate keys to
authenticate at the OpenSSH server in the docker container.

The test is not run with the mina and netty back-ends; testcontainers
has problems resolving files when run from the re-usable test JAR. It
also isn't run on Windows; GitHub actions Windows Server VM's don't
have Docker (Linux) support.

Also note that the test makes sure that the real BouncyCastle security
provider is installed; testcontainers contains a shaded BC copy that
may fail at runtime due to being unsigned.
@zhoutt96oci
Copy link

sss

@zhoutt96oci
Copy link

kj/nn

@zhoutt96oci
Copy link

mmm

@zhoutt96oci
Copy link

merge only comment

@zhoutt96better
Copy link
Author

yyyyy

@zhoutt96oci
Copy link

mmmm

@zhoutt96oci
Copy link

test

@zhoutt96oci
Copy link

reopen

@zhoutt96oci
Copy link

@zhoutt96better

1 similar comment
@zhoutt96oci
Copy link

@zhoutt96better

@zhoutt96oci
Copy link

comment not

@zhoutt96oci
Copy link

hhhhhhhh

@zhoutt96better
Copy link
Author

test

@zhoutt96better
Copy link
Author

@zhoutt96oci

1 similar comment
@zhoutt96better
Copy link
Author

@zhoutt96oci

@zhoutt96oci
Copy link

@zhoutt96better

@zhoutt96oci
Copy link

comment @zhoutt96better

@zhoutt96oci
Copy link

xoo

1 similar comment
@zhoutt96oci
Copy link

xoo

@zhoutt96oci
Copy link

,,,

@zhoutt96oci
Copy link

participate

@zhoutt96oci
Copy link

nnnnn

@zhoutt96oci
Copy link

bkbjllblk

@zhoutt96oci
Copy link

nnnnnn

@tomaswolf
Copy link
Member

@zhoutt96better , @zhoutt96oci : stop these stupid test pull requests. They are a nuisance; maintainers of this repository get spammed with nonsense e-mails.

@tomaswolf tomaswolf closed this Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet