Setting DRA's Key Length to 4096

Posted on 2008-10-23
Medium Priority
Last Modified: 2012-05-05

I'm deploying a Microsoft PKI solution and need to create a DRA for EFS.  By default, using the cipher \r command, it creates a DRA key of 2048 bits on either a Vista or a 2008 machine (1024 on 2003 and XP).  However, I would like create them as 4096 bit in length.  I have added theHKLM\Software\Microsoft\Windows NT\CurrentVersion\EFS\RSAKeyLength DWORD with a decimal value of 4096 as recommended by Microsoft document.  Unfortunately, when I run the cipher \r command to create a DRA key, it is created as a 2048 bit length RSA key.   I have no idea how to get around this problem.

Any help would be appreciated.

Question by:nav_support
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
LVL 31

Expert Comment

ID: 22789900
Dare I ask why you would want a 4096 keyset?  2048 is plenty good enough to last you for over a decade.

Are you trying to create this on a smartcard or just as a local file?  The CSP needs to support the 4096 keyset, which most, if not all, smartcards do not.  4096 can be created on another device and stored on a smartcard, that's a different story, such as with an HSM, but that would not suite your purpose.  The default MS CSPs should support 4096 ok though.

Also, is this using a self-signed cert or one from a CA?
LVL 31

Expert Comment

ID: 22790004
If this is a CA issued cert, you should try adding that same reg key to the CA server as well.
likewise, a CA cannot issue a cert with a key strength greater than its own.  I.e. the CA cert needs to be 4096 or higher to issue a 4096 key.  The reasoning behind this is that the CA cert would be made vulnerable prior to the cert it is authorizing.
Also keeping in mind that the validity period cannot be longer than that of the CA cert - if it is set longer it will be truncated.

Author Comment

ID: 22790408
Thanks for your comments Paranormastic.

I should have mentioned in my question, this will be a self-signed certificate as opposed to a CA issued one.  Essentially, it is so we don't have to worry about renewing it at any point.  

I'm essentially trying to create the self-signed certificate locally, so there are no smartcards in the equation (perhaps in the future, but not anytime soon).

As for why we would a 4096 key length, it is probably just paranoia (most likely misplaced!) since the key will be in use for a long while.  I suppose if I can't get around this issue, I'll end up using a 2048 key length.

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

LVL 31

Accepted Solution

Paranormastic earned 500 total points
ID: 22795812
Have you tried rebooting since setting that registry key?  I don't recall ever seeing if that key actually affected the DRA cert or just the EFS cert, but by means of logic it should affect both.  I am not familar and am not finding reference to anything that specifically designates the keysize for the DRA vs. normal EFS keysets.  To my memory this reg key affects standard EFS certs, hence your normal EFS cert would be 4096 - does that match up?

BTW, here is a handy reg key to add the Encrypt/Decrypt option to your standard right-click menu:

Author Comment

ID: 22799341
Thanks again Paranormastic for your response.  I just tested creating a self signed EFS key on a Vista box and the key was created using a 4096 key length using that Registry entry.  However, when I create a DRA key it is only a 2048.  So your suspicion about the registry entry only working on the EFS keys and not the DRA are correct.  I guess I'll have to settle for a 2048 key length for the DRA unless I use a CA issued one.

Also, thanks for the handy reg key - I had read about this option, but I had not seen the actual registry entry.  Much appreciated.

Author Closing Comment

ID: 31509375
Paranormastic made me think about what I was doing by seing what would happen when I changed the registry value and created a self-signed EFS cert and a DRA (the EFS cert was affected by the registry key and not the DRA).  This convinced me that what I was trying to do won't work.  

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A procedure for exporting installed hotfix details of remote computers using powershell
Encryption for Business Encryption (https://en.wikipedia.org/wiki/Encryption) ensures the safety of our data when sending emails. In most cases, to read an encrypted email you must enter a secret key that will enable you to decrypt the email. T…
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
Suggested Courses
Course of the Month10 days, 3 hours left to enroll

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question