2014-12-30 19:30:39 +01:00
|
|
|
---
|
|
|
|
layout: page
|
2015-01-05 18:04:04 +01:00
|
|
|
title: Public keys
|
2014-12-30 19:30:39 +01:00
|
|
|
permalink: /keys/
|
|
|
|
---
|
|
|
|
|
|
|
|
This page contains key fingerprints that might interest you if you wish
|
|
|
|
to communicate with me securely.
|
|
|
|
|
|
|
|
## Table
|
|
|
|
|
|
|
|
| Type | Fingerprint |
|
|
|
|
|------|-------------|
|
|
|
|
| OTR | DA0CFDDE E05BE012 B2E726B5 0789F4E2 E7DB582D |
|
|
|
|
| PGP | 2910 4A46 C561 5BF9 78A0 83F2 0C20 7F07 B2F3 2B67 |
|
|
|
|
|
|
|
|
<br/>
|
|
|
|
|
|
|
|
Note that my OTR key matches just WeeChat and is affected by [this issue].
|
2015-01-14 09:02:55 +01:00
|
|
|
If you notice that my OTR key is different, please mention it to me and I will
|
|
|
|
copy the correct key. If that doesn't help, don't think that you are talking to me.
|
2014-12-30 19:30:39 +01:00
|
|
|
|
|
|
|
[this issue]:https://github.com/mmb/weechat-otr/issues/70
|
|
|
|
|
|
|
|
## DNS TXT records
|
|
|
|
|
|
|
|
I should probably sign that table using PGP (but it wouldn't increase
|
|
|
|
trust as I still have met no one whom with to sign keys), but with your
|
|
|
|
own responsibility\* you can verify the following DNS records:
|
|
|
|
|
2014-12-31 07:20:52 +01:00
|
|
|
```bash
|
2015-01-28 20:59:26 +01:00
|
|
|
dig +short otr.mikaela.info TXT
|
2014-12-31 09:26:51 +01:00
|
|
|
dig +short pgp.mikaela.info TXT
|
2014-12-31 07:20:52 +01:00
|
|
|
```
|
2014-12-30 19:30:39 +01:00
|
|
|
|
|
|
|
\* This site doesn't have DNSSEC (but you would be trusting ICANN) and
|
|
|
|
cache of your DNS server can be poisoned to give wrong results and long
|
|
|
|
list of different risks that can be there…
|