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

Doesn't work with Netbeans defalut keystore #40

Open
scop opened this issue Aug 18, 2012 · 7 comments
Open

Doesn't work with Netbeans defalut keystore #40

scop opened this issue Aug 18, 2012 · 7 comments

Comments

@scop
Copy link
Owner

scop commented Aug 18, 2012

Looks like a dead project. Bugs untouched for 7 years.

Well just in case:
portecle-1.7, Netbeans 7.2
I can open the Netbeans default keystore using
keytool -list -keystore ...builtin.ks
with a blank password, and it shows three certificates.

Portecle in contrast, shows a blank screen, no error message, on stderr or otherwise.
Just nothing.

Reported by: stevan_white

@scop
Copy link
Owner Author

scop commented Aug 25, 2012

Looks like a bug report with weird, unrelated, hastily drawn conclusions apparently based on incomplete home work in the beginning.

Well, just in case:

There's no "builtin.ks" keystore file in the netbeans 7.2 I just downloaded. There is however a ide.ks in the nb/core subdir, and that one opens successfully with Portecle using the password "open4all" for me. Note that unlike keytool, Portecle doesn't support opening keystores in "read only mode", ie. without a password.

If you have the keystore file that can be used to reproduce the "blank screen" problem, feel free to reopen this bug and attach or email it along with its password.

Original comment by: scop

@scop
Copy link
Owner Author

scop commented Aug 25, 2012

  • status: open --> closed-works-for-me

Original comment by: scop

@scop
Copy link
Owner Author

scop commented Aug 26, 2012

Pardon the hastiness. I was frustrated.

I should have added: the keystore in question is in
~/.netbens/config/j2me/builtin.ks
It didn't occur to me at the time that it was j2me-specific.

This may be added when J2ME project is created (it isn't clear to me; I only know I didn't do anything special.)
As I think the contents are auto-generated, I'll attach it ... I *would* attach it. I don't see how, at this point. There seems to be no option to do that.

As to support for blank passwords,
This is stil a UI bug. It should give the user some indication of what went wrong, or what to do next.

Original comment by: stevan_white

@scop
Copy link
Owner Author

scop commented Aug 26, 2012

scop,

I looked into the attachment issue.

The reason I don't see any means to attach a file, is probably that the report is closed.

It seems the capacity of a submitter to re-open a ticket was removed some time ago.

If you would like to see the example file, please re-open the report.

Original comment by: stevan_white

@scop
Copy link
Owner Author

scop commented Aug 26, 2012

  • status: closed-works-for-me --> open-works-for-me

Original comment by: scop

@scop
Copy link
Owner Author

scop commented Aug 26, 2012

Under no circumstances should the "just blank" behavior occur. The bug is now open again, try attaching again now.

Original comment by: scop

@scop
Copy link
Owner Author

scop commented Aug 26, 2012

From .netbeans/7.2/config/j2me/
builtin.ks.zip

Original comment by: stevan_white

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant