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

Jump to bottom

Null pointer loading keys from sun.security.mscapi.KeyStore #8372

Closed
cyberduck opened this issue Nov 26, 2014 · 5 comments
Closed

Null pointer loading keys from sun.security.mscapi.KeyStore #8372

cyberduck opened this issue Nov 26, 2014 · 5 comments
Assignees
@ylangisc
Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Milestone
4.6.1

Comments

@cyberduck
Copy link
Collaborator

344c7f6 created the issue

When connecting to S3, the connection fails immediately. In cyberduck 4.5.n this caused a complete app crash, but in 4.6 it just appears to do nothing.

  • Click Open Connection or create a bookmark
  • enter AWS Access Key ID and Secret Access Key
  • click Connect
  • the status bar flashes a message very briefly, but nothing else seems to happen

The log file shows the error:

[background-1] FATAL ch.cyberduck.ui.AbstractController - Unhandled exception running background task null
java.lang.NullPointerException
	at IKVM... etc...

(log file attached)

As a result I'm completely unable to use (the awesome) Cyberduck for connecting to S3.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

2014-11-27 09:56:44,205 [background-1] INFO  ch.cyberduck.core.ssl.CertificateStoreX509KeyManager - Load default store of type Windows-MY
2014-11-27 09:56:44,268 [background-1] FATAL ch.cyberduck.ui.AbstractController - Unhandled exception running background task null
java.lang.NullPointerException
	at IKVM.Runtime.JNIEnv.StringFromUTF8(Unknown Source)
	at IKVM.Runtime.JNIEnv.NewStringUTF(Unknown Source)
	at sun.security.mscapi.KeyStore.loadKeysOrCertificateChains(Native Method)
	at sun.security.mscapi.KeyStore.engineLoad(KeyStore.java:760)
	at sun.security.mscapi.KeyStore$MY.engineLoad(KeyStore.java:62)
	at java.security.KeyStore.load(KeyStore.java:1214)
	at ch.cyberduck.core.ssl.CertificateStoreX509KeyManager.init(CertificateStoreX509KeyManager.java:88)
	at ch.cyberduck.core.ssl.CertificateStoreX509KeyManager.<bridge>init(CertificateStoreX509KeyManager.java:51)
	at ch.cyberduck.core.ssl.SSLSession.getKeyManager(SSLSession.java:87)
	at ch.cyberduck.core.http.HttpSession.registry(HttpSession.java:177)
	at ch.cyberduck.core.http.HttpSession.builder(HttpSession.java:106)
	at ch.cyberduck.core.s3.S3Session$RequestEntityRestStorageService.<init>(S3Session.java:123)
	at ch.cyberduck.core.s3.S3Session.connect(S3Session.java:372)
	at ch.cyberduck.core.s3.S3Session.<bridge>connect(S3Session.java:82)
	at ch.cyberduck.core.Session.open(Session.java:112)
	at ch.cyberduck.core.LoginConnectionService.connect(LoginConnectionService.java:151)
	at ch.cyberduck.core.LoginConnectionService.check(LoginConnectionService.java:98)
	at ch.cyberduck.core.LoginConnectionService.check(LoginConnectionService.java:105)
	at ch.cyberduck.core.threading.SessionBackgroundAction.connect(SessionBackgroundAction.java:198)
	at ch.cyberduck.ui.threading.BrowserBackgroundAction.connect(BrowserBackgroundAction.java:59)
	at ch.cyberduck.core.threading.SessionBackgroundAction.call(SessionBackgroundAction.java:166)
	at ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:171)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:167)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:604)
	at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:58)
	at java.lang.Thread.run(Thread.java:937)

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

Fixed in 67c38a9.

@cyberduck
Copy link
Collaborator Author

344c7f6 commented

Woohoo! That was quick.
I'm looking forward to 4.6.1.

Cheers!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available and let me know if the issue is resolved.

@cyberduck
Copy link
Collaborator Author

344c7f6 commented

IT WORKS!

Thank you very much.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ylangisc ylangisc

Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
4.6.1
Development

No branches or pull requests
2 participants
@ylangisc @cyberduck