Hi Daniel,

yes, it is possible to change the algorithm very easily. You have to change the openssl configuration(s) in <prefix>/etc/openca/openssl/ . In particular, the new version(s) come already with sha256 enabled by default. However, you should look at the following files:

* <prefix>/etc/openca/openssl/openssl.cnf.template
*<prefix>/etc/openca/openss/ext/*.template

the configuration keyword is "default_md" and, in your case, should be set to "sha256". The extfile directory, instead, contains the definition of the profiles for the different types of certificates (not related to your request, but I thought you might need to know the distinction anyway).

I hope this helps,

Cheers,
Max


On 08/15/2013 01:29 PM, CHRISTIAN DANIEL ENCISO PADILLA wrote:
Hello Massimiliano,
This is Daniel Enciso, I'm working at Universidad Nacional Autónoma de México (UNAM) and nowadays my office is reciving an old project from grid-UNAM.
The main point of the question is that:
TAGPMA is requesting us to migrate the algorithm from SHA1 to SHA256. So, is that possible with any version of OpenCA? If is yes, Are there some How to manuals to apply these changes in the algorithm?

I really hope not to be a nuisance for you & wait for your answer.

my sincerely respect for you.

--
daniel enciso


--

Best Regards,
Massimiliano Pala, Ph.D.
OpenCA Labs Director

OpenCA Labs
Tel. (603) 369-9332
skype: openca

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Openca-Users mailing list
Openca-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openca-users

Reply via email to