Re: Best practices for signing a plugin

Hi Frank,

> Is it possible to access an keystore outsde of the current project folder

Yes. I updated
http://wiki.netbeans.org/DevFaqSignNbm#Can_I_sign_Maven_based_NBMs_I_create.3F
to answer your question.

> Do I really need to generate a new key or is the better approach to use a
known key for it (eg the key linked to my GitHub profile)

I sign my plugins with a self-generated key. Of course if you already have
a valid certificate from a root authority then use it. Else your plugin
will be shown as untrusted when installing/updating the plugins. But this
is not so important as it might sound. There has never been a request to
sign my plugins with a trusted certificate so far.



With kind regards, markiewb

2015-12-28 11:07 GMT+01:00 user0815 <[email protected]>:

> I'm currently preparing my first plugins for publishing them.
>
> I have some questions related to best practices for singing them
>
> I'm using Maven for the build process. Is it possible to access an
> keystore outsde of the current project folder eg. by using an relative path
> like ../../mykeystore ? In this case I would have a single keystore for
> signing all plugins and the keystore would be outside of the public
> repository (teh plugins are stored on GitHub).
>
> Do I really need to generate a new key or is the better approach to use a
> known key for it (eg the key linked to my GitHub profile)?
>
> TIA + Best regards,
>
>
>
>
>