![]() For these reasons, if the certificate can be transferred to the client machine by some other secure method then that is usually preferable to accepting the certificate during the SSL handshake. It is also a serious inconvenience if you wish to invoke the Subversion client from a non-interactive script. The main drawback of this process is the risk that the user will accept a certificate without checking it carefully enough. ![]() It also displays a ‘fingerprint’ derived from the certificate, which can be used to check the authenticity of the certificate by comparing it with a fingerprint provided by the issuer. If it is not then the client displays a warning, and asks the user whether the certificate should be trusted permanently, temporarily, or not at all. The client then determines which certificate authority (if any) issued the certificate, and whether that authority is trusted. When an SSL connection is established, the server identifies itself to the client by presenting an X.509 certificate. By itself a connection of this type is unencrypted, however it can be used in combination with SSL if encryption is wanted. Subversion is a revision control system that supports the use of an HTTP-based protocol called WebDAV for client-server communication. To configure Subversion to trust a given SSL certificate without prompting for confirmation Background
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |