Skip to main content

Import root certificate in Windows

Following are the steps to import a digital certificate into the trusted root certification authorities folder:
  1. Click Start, click Run, type mmc, and then click OK.
  2. Click File, and then click Add/Remove Snap-in.
  3. On the Standalone tab, click Add.
  4. Select Certificates, and then click Add. When prompted, select Computer account, and then click Next.
  5. On the Select Computer page, select Local computer (the computer this console is running on), and then click Finish.
  6. In MMC, expand Certificates – Local Computer, and then expand Trusted Root Certification Authorities.
  7. In the details pane, right-click and point to All tasks, and then click Import.
  8. On the first page of the Certificate Import Wizard, click Next.
  9. In the File name dialog box, type the name and location of the file containing the root CA's digital certificate, and then click Next.
  10. On the Certificate Store page, click Place all certificates in the following store, ensure that the Certificate store dialog box shows Trusted Root Certification Authorities, and then click Next.
  11. On the final page of the wizard, click Finish.
Labels:
Location: Pune, Maharashtra, India

Comments

Anonymous said…
Hello Everyone.. I'm from Pandharpur (Maharashtra).. I want to change my Birth date on Birth Certificate. To change it I went to Panchyat Samiti of Pandharpur but they told me that they dont have rights to correct birth Date. pls tell me the procedure for correction in birth date.
22 March, 2017 15:15
Post a Comment

Popular posts from this blog

MPlayer subtitle font problem in Windows

While playing a video with subtitles in mplayer, I was getting the following problem: New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). Solution is as follows: Right click on "My Computer". Select "Properties". Go to "Advanced" tab. Click on "Environment Variables". Delete "HOME" variable from User / System variables.
4 comments
Read more

Kafka performance tuning

Performance Tuning of Kafka is critical when your cluster grow in size. Below are few points to consider to improve Kafka performance: Consumer group ID : Never use same exact consumer group ID for dozens of machines consuming from different topics. All of those commits will end up on the same exact partition of __consumer_offsets , hence the same broker, and this might in turn cause performance problems. Choose the consumer group ID to group_id+topic_name . Skewed : A broker is skewed if its number of partitions is greater that the average of partitions per broker on the given topic. Example: 2 brokers share 4 partitions, if one of them has 3 partitions, it is skewed (3 > 2). Try to make sure that none of the brokers is skewed. Spread : Brokers spread is the percentage of brokers in the cluster that has partitions for the given topic. Example: 3 brokers share a topic that has 2 partitions, so 66% of the brokers have partitions for this topic. Try to achieve 100% broker spread
1 comment
Read more

wget and curl behind corporate proxy throws certificate is not trusted or certificate doesn't have a known issuer

If you try to run wget or curl in Ununtu/Debian behind corporate proxy, you might receive errors like: ERROR: The certificate of 'apertium.projectjj.com' is not trusted. ERROR: The certificate of 'apertium.projectjj.com' doesn't have a known issuer. wget https://apertium.projectjj.com/apt/apertium-packaging.public.gpg ERROR: cannot verify apertium.projectjj.com's certificate, issued by 'emailAddress=proxyteam@corporate.proxy.com,CN=diassl.corporate.proxy.com,OU=Division UK,O=Group name,L=Company,ST=GB,C=UK': Unable to locally verify the issuer's authority. To connect to apertium.projectjj.com insecurely, use `--no-check-certificate'. To solution is to install your company's CA certificate in Ubuntu. In Windows, open the first part of URL in your web browser. e.g. open https://apertium.projectjj.com in web browser. If you inspect the certifcate, you will see the same CN (diassl.corporate.proxy.com), as reported by the error above
Post a Comment
Read more