I knew SHA1 is going to be expired on all internet browser in 2016.
All FWs of Paloalto are using SHA1 when access Web-UI.
I think if PA keep using it on, administrator could not access Web-UI by browser bloking.
So It has to change from SHA1 to SHA256.
I just want to know plan when chainging it.
Please someone let me know it.
If you do not have a plan for it.
Do I have to make self-generated certificate with SHA256 and then enable "certificate for Secure Web GUI"?
Is there another way?
The deprecation of SHA-1 is completely browser dependent, though most of the major browsers (like firefox,chrome) are
contemplating to completely block the pages secured through SHA1. Please look for official announcements from the organizations who develop these browsers to keep a track of the timeline.
Following is a good read :
As for PA ,WebGUI access or SSL decryption (forward-proxy) certificate, you can create a new certificate using a more secure hashing algorithm like SHA-256 which is acceptable for the browser hence would not block or through error.
Hope this helps !
Thanks for your comment.
I have read a google blog page what you suggest.
This blog mentioned the following,
The Issuer is localhost for certificate when accessing Web-UI.
Chorme could not block SHA-1 certificate that issuer is localhost(self-generated) when accessing Web-UI after 2017. RIGHT?
Do I understand correct it?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!