-
Notifications
You must be signed in to change notification settings - Fork 602
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
Android Compability, again ;-) #392
Android Compability, again ;-) #392
Conversation
Codecov Report
@@ Coverage Diff @@
## master #392 +/- ##
============================================
+ Coverage 55.2% 55.26% +0.05%
- Complexity 1147 1148 +1
============================================
Files 189 189
Lines 7486 7482 -4
Branches 651 652 +1
============================================
+ Hits 4133 4135 +2
+ Misses 3005 2998 -7
- Partials 348 349 +1
Continue to review full report at Codecov.
|
…rovider. On Android 5.0 reading the version from the jar does throw a SecurityException due to a bug in Android (see https://issuetracker.google.com/issues/36993752). Including that Exception in the catch provides a workaround for that issue.
I updated to PR to include another fix/workaround when SSHJ is used on Android 5.0 (see 18b0cca). |
Thanks! |
@hierynomus I don't want to rush you, but do you have any plans for a new release which includes this fix? |
As mentioned in #308 (comment), PCKS8KeyFile had a hard dependency on BouncyCastle as JCE provider.
In combination with SpongyCastle on Android an the updated AndroidConfig, this leads to exceptions when running on Android and using publickey auth (excerpt from my Android app):
With these changes PKCS8KeyFile relies on the previously registered JCE provider (which could be BC or SC).
Furthermore, AndroidConfig is now much simpler (no more dirty workarounds for isBouncyCastleRegistered() as this method now returns true when SpongyCastle was registered).