HP Jetdirect 610n HP Jetdirect Print Servers - HP Jetdirect and SSL/TLS - Page 12

Public Key Infrastructure and Public Key Certificate Basics - drivers

Get HP Jetdirect 610n PDF manuals and user guides View all HP Jetdirect 610n manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

Public Key Infrastructure and Public Key Certificate Basics Let's go back to the certificate information dialog, shown in Figure 14: Figure 14 - Certificate Information Here is the message: "This CA Root certificate is not trusted." To enable trust, install this certificate in the Trusted Root Certification Authorities store". What the message is trying to say is that "HP Jetdirect 85C1F319", who issued the certificate "HP Jetdirect 85C1F319", is not trusted. Because the "Issued by:" name is the same as the "Issued to:" name, this is a self-signed certificate. The Security Alert dialog is troubling because it is indicative of a trust problem. In the terms of our analogy, it would be like a driver, who has been pulled over by the Highway Patrol, handing the officer a driver's license that the driver has created for himself indicating that he has the privilege to drive in the state. The Highway Patrol would obviously not trust it and unfortunately may not consider it a laughing matter. In essence, a digital certificate, one used by computers, binds an identity to a key and needs to be issued by a trusted third party. What is a key? A key is a secret that is used in cryptographic algorithms. There are public keys and private keys used for asymmetric cryptography and symmetric keys used for symmetric cryptography. Let's look at symmetric cryptography first. 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
12
Public Key Infrastructure and Public Key Certificate Basics
Let’s go back to the certificate information dialog, shown in Figure 14:
Figure 14 - Certificate Information
Here is the message: “This CA Root certificate is not trusted.”
To enable trust, install this certificate in
the Trusted Root Certification Authorities store”.
What the message is trying to say is that “HP
Jetdirect 85C1F319”, who issued the certificate “HP Jetdirect 85C1F319”, is not trusted.
Because
the “Issued by:” name is the same as the “Issued to:” name, this is a self-signed certificate.
The Security Alert dialog is troubling because it is indicative of a trust problem.
In the terms of our
analogy, it would be like a driver, who has been pulled over by the Highway Patrol, handing the
officer a driver’s license that the driver has created for himself indicating that he has the privilege to
drive in the state.
The Highway Patrol would obviously not trust it and unfortunately may not consider
it a laughing matter.
In essence, a digital certificate, one used by computers, binds an identity to a key and needs to be
issued by a trusted third party.
What is a key?
A key is a secret that is used in cryptographic
algorithms.
There are public keys and private keys used for asymmetric cryptography and symmetric
keys used for symmetric cryptography.
Let’s look at symmetric cryptography first.