Accepting a self-signed certificate

Issue:
When connecting over a secured connection, self-signed certificates may trigger an "Untrusted Connection" error.
Resolution:
Each browser handles security differently. In Firefox, you can create a permanent exception. In Chrome or Internet Explorer you must install the certificate in your trusted certificates store.
Both Chrome and Internet Explorer use the Trusted Root Certification Authorities store when verifying certificates. If you have performed the steps to install the certificate for either Internet Explorer or Chrome, you do not have to perform the same steps again to use either browser.
Note:   You must close all instances of your Internet Explorer or Chrome and completely clear your cache.
To create a permanent exception for Firefox:           
  1. Open a browser to your Virtualization Manager server using https.
  2. When the error occurs, expand I Understand the Risks.
  3. Click Add Exception.
  4. When prompted, click Confirm Security Exception.
To install the certificate at a trusted certificate with Internet Explorer:
  1. Open a browser to your Virtualization Manager server using https.
  2. When the error occurs, click Continue to the website (not recommended).
  3. In the address bar, click Certificate Error.
  4. Click View Certificates
  5. In the General tab, click Install Certificate…
  6. Click Next.
  7. Select Place all certificates in the following store, and click Browse.
  8. Select Trusted Root Certification Authorities, and click OK.
  9. Click Next.
  10. Click Finish.
  11. When prompted to confirm installation, select Yes.
  12. Close the tab, and restart Internet Explorer.
To install the certificate at a trusted certificate with Chrome:
  1. Open a browser to your Virtualization Manager server using https.
  2. When the error occurs, click Proceed Anyway.
  3. In the address bar, click the lock icon to view the site information.
  4. On the Connections tab, click Certificate Information.
  5. On the Details tab, click Copy to File…
  6. Click Next.
  7. Select DER encoded binary X.509 (.CER), and click Next.
  8. Enter a file name. By default Chrome saves the certificate in a hidden file in \Users\username\AppData\Local\Google\Chrome\Applications\...
    If you do not want to make hidden files visible, browse to a different location to save the certificate.
  9. Click Next.
  10. Check the location of the certificate, and click Finish.
  11. In Chrome, open Settings > Advanced Settings, and click Manage certificates…
  12. Navigate to the Trusted Root Certification Authorities tab.
  13. Click Import.
  14. Click Next.
  15. Browse to the certificate you exported, and click Next.
  16. Select Place all certificates in the following store, and select Trusted Root Certification Authorities.
  17. Click Next, and then click Finish.
  18. When prompted, select Yes.
  19. Close the tab and restart Chrome.

Comments

Post a Comment

Popular posts from this blog

CDbConnection failed to open the DB connection mysql 8

Image
While accessing web configured with mysql 8 and php and you see the following error: CDbConnection failed to open the DB connection: SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client OR  PHP Fatal error:  Uncaught PDOException: PDO::__construct(): The server requested authentication method unknown to the client [caching_sha2_password]  It maybe due to  PHP devs might have not implemented the MySQL's 8.0 connection protocol ( auth with caching_sha2_password ) within the newer PHP versions. If you want to use mysql >= 8 and you dont care about caching_sha2_password,  If you are running a fresh install of mysql 8, just select the second option as shown in the image. Otherwise, you need to  configure MySQL 8.0 to run in mysql_native_password mode. As it can't configured in my.cnf, change the user profile as:- ALTER USER 'mysqlUsername'@'localhost' IDENTIFIED WITH mysql_native_password BY 'mysqlUs...
Read more

/bin/sh^M: bad interpreter: No such file or directory Linux

While running a script in Linux, if you encounter an error such as : /bin/sh^M: bad interpreter: No such file or directory The error is due to incorrect format of the script. Most probably when the script is created in Windows and transferred to Linux. The script might have a dos line ending file. The clue is the ^M Inorder to resolve this error: Open the script in Linux using vim editor,  enter in vi command mode (key ESC), then type this: : set fileformat = unix   Finally save it :x! or :wq! Thats it! Try running the script again and the error would have disappeared.  
Read more

Send mail from Oracle Solaris OS with attached files

To send mail from Solaris, use this syntax echo "some text to send" | mailx -s "subject of email" recipient's@address Or, if you have body of email in some file: mailx -s "subject of email" recipient's@address < some_file.txt If you want to send mails with zip files of image files use the following formats: uuencode reports.tar.gz reports.tar.gz | mailx -s "My Report" you@domain.com     uuencode office.jpeg office.jpeg | mail -s "Subject" you@domain.com   If you need to send multiple attachments in single mail:   $ uuencode r1.tar.gz r1.tar.gz > /tmp/out.mail $ uuencode r2.tar.gz r3.tar.gz >> /tmp/out.mail $ uuencode r3.tar.gz r3.tar.gz >> /tmp/out.mail $ cat email-body.txt >> /tmp/out.mail $ mail -s "Reports" you@domain.com < /tmp/out.mail            
Read more