If you are new to the concept of security certificates, verifying their fingerprints, etc, you may want to view the "Web SSL Certificates" tutorial. It explains why you may get dialog boxes talking about unknown CA's or certificates for different domain names (dagertech.org vs www.dagertech.net, etc). Update: Tutorial is currently unavailable. I hope to replace it soon.

Otherwise, here are the necessary fingerprints to my services. You may also wish to just download the signed file rather than cut and paste. My public key is located here or you can look it up in a keyserver. It should be 0xD0D753BB.

Also, I have my own Certificate Authority. So if you don't want to verify individual services, you can import my CA Cert; be sure to also verify its signature.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



DaGerTech Certificate Authority:
MD5 Fingerprint=FD:06:97:9A:6C:41:E4:39:7F:0E:8D:5D:9C:A8:4C:F2
SHA1 Fingerprint=85:93:7B:6E:A9:72:96:21:92:8F:CD:6F:35:CD:68:F2:AE:4F:02:FE

DaGerTech Web Server:
MD5 Fingerprint=82:CD:A5:BF:A6:DC:F2:C5:70:26:C6:0B:A3:33:19:58
SHA1 Fingerprint=84:A2:0C:39:E4:75:0D:7B:CB:05:D5:2C:02:EF:B7:12:26:7C:1A:22

DaGerTech (A)POP3 Server:
MD5 Fingerprint=39:CD:98:8C:7D:B5:B2:CB:0E:FA:87:FC:E5:8A:4F:DA
SHA1 Fingerprint=4F:7A:6C:31:2A:E3:B3:67:CA:15:FC:40:41:34:0B:48:04:F0:4F:00

DaGerTech SMTP Server :
MD5 Fingerprint=85:11:97:9E:A9:DB:51:88:57:25:68:40:3D:60:EA:27
SHA1 Fingerprint=21:68:59:D6:7E:08:58:A8:E5:8C:5A:24:DC:8A:F1:D4:9F:3F:78:AD

Matrix Secure Shell:
1024 57:88:e6:90:12:12:94:bb:f0:d9:be:59:73:ad:fd:9f ssh_host_dsa_key.pub
2048 85:8e:8a:a6:a4:27:43:31:99:b6:dc:82:d1:66:28:93 ssh_host_rsa_key.pub
2048 55:65:c1:04:15:ef:8d:d1:65:f5:98:50:84:ec:e2:78 ssh_host_key.pub

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFILNZ83GktKdDXU7sRAq75AJ9DJ4kED3DVJJ6pY9i1DeinzLLT4wCgnLf6
uhuIe3097GmQQsMK9cxN6h4=
=I5Ek
-----END PGP SIGNATURE-----