|
Hi Varun,
created a keystore:
keytool -genkey -alias christian -keystore keystore.ease
Then I tried to sign a script with the alias 'christian' from
that store. I went with the defaults: provider=SUN,
algorithm=SHA256.
When clicking 'Finish' I end up with an error message: "Unable to
access state location" and the dialog would not close.
Digging in the code you are trying to store the signature to a
dedicated folder. We should change that as we want to store the
signature to the file directly from the context menu. As sometimes a
file might be read-only it is a good idea to have alternative
locations to store signatures.
What about changing the wizard to not directly write the signature.
Instead it should return the signature data and the caller of the
wizard should decide where the signature should go to afterwards.
When the file is writable, this would be the preferred location. A
context menu on a workspace file should not do anything else.
Christian
On 07/31/2016 06:49 AM, Varun Raval
wrote:
Hi Christian,
I have updated the patch [1].
One reason you might not be able to perform
signature maybe the algorithm of private key. Since
specific providers provide implementation of algorithms
for e.g. SHA1withDSA by SUN, SHA1withRSA by SunRsaSign. I
solved this issue.
Previously, I was taking SUN as default one. Now, in the
update, if not selected explicitly on advanced page, it will
try to chose preferred provider. Hence, for private key
created for any algorithm like DSA or RSA, if provider combo
box is not selected, it will iterate over all algorithms and
chose preferred one.
In this case, it would be helpful to user if we provide
"preferred" as an option so that once user has selected an
algorithm, user can still let system make the choice of
algorithm. I am saying this because, we previously agreed on
showing specific types to user like "SUN" and not "Preferred"
as default option.
Other reason might be that there are no alias with
private key in provided keystore. jre/lib/security/cacerts is
a kind of trust store that contains list of trusted
certificates. These aliases are just certificates that contain
public key. There is no alias with private key there by
default.
Thanks,
Hi Christian,
Wherever you want to create a new keystore file, try
this from terminal to make a new private key with name
MYALIAS and place it in a new keystore with name
KEYSTORE_NAME
keytool -genkey -alias
MYALIAS -keystore KEYSTORE_NAME
To list the current aliases in keystore
keytool -list -keystore
KEYSTORE_NAME
Generate a self-signed certificate file
keytool -export -alias MYALIAS -file certfile.cer
-keystore KEYSTORE_NAME
To make a Certificate Signing Request(CSR) from
existing JAVA Keystore
keytool -certreq -alias MYALIAS -keystore
KEYSTORE_NAME -file MYALIAS.csr
Thanks,
Hi
Varun,
could you provide a short totuorail how to create a
keystore with a self
signed certificate that works with your current patchset?
I was trying
out some settings but none of them worked so far.
thanks
Christian
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev
--
Varun Raval
--
Varun Raval
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev
|
