OpenPGPComment

Before I switched to WordPress on May 1st I was using MovableType and Srijiths MovableType plugin OpenPGPComment. When I found out there was no comparable plugin for WordPress I had to start doing one of my own.

The hardest part was finding out how to pass the signed comments to GPG. Then I’ve found Atom Emets gpg_encrypt and was able to reuse a lot of his code.

The rest was a lot of fiddling with the WordPress-API and trying to find out how to write plugins. Thanks to Mark Gosh who gave me some insights on IRC-channel #wordpress.

The way this plugin works is it strips all of the GPG-stuff off the comment so it looks just like an ordinary comment. Instead of the quite unreadable signature a hint is added to see this is a signed comment you’re dealing with here. This hint contains a link which opens a popup-window. Only when this link is clicked, gpg is called to verify the signed comment against the key being signed with. The result of the verification is shown and a cleartext version of the comment. This is being done by putting the comment into a textarea so a comment can be copy’n'pasted and any HTML that might be included is not parsed.

The popup window is very simple. It used to be the original wp-comments-popup.php that has been stripped off most of its code. This makes this window look pretty ugly and a lot of beautification could be done here. But hey, it’s version 0.9!

If you want to give OpenPGPComment a try, you can find installation instructions following the given link and within the archive.

25 Kommentare ↓

Pages: [3] 2 1 » Zeige alle

#1 Johannes schrieb am 2005-04-15 um 20:14 Uhr:

Super, danke! Mal sehen, ob ich das im chroot zum laufen bewegen kann!

#2 Will Hayworth schrieb am 2005-03-29 um 01:14 Uhr:

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA1

Thanks very much for the excellent plugin!

—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.4.1 (MingW32) - WinPT 0.9.90

iD8DBQFCSI/H3KUrxmmXe+ARAvXYAKDf3ldf0cv0Z7IAzexbq+aogaRKkgCfUIMf
06SFEaYbcgqJsZChjuWFfQk=
=7w6l
—–END PGP SIGNATURE—–

#3 Dominik schrieb am 2004-12-09 um 14:27 Uhr:

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA1

Works like a breeze now. :) Thanks a lot.
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.2.1 (MingW32) - WinPT 0.7.96rc1

iD8DBQFBuFLOCFFxLzl8aXcRAgZ2AJ46Den4ivAjbPmS44K4nqv3JJ4NlgCeP/hy
LS7TONoFuXftbl5y2xn37kE=
=OTSM
—–END PGP SIGNATURE—–

#4 Christoph Rummel schrieb am 2004-12-09 um 13:26 Uhr:

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA1

Delete lines 13 - 28 in openpgpcommentadmin.php
I’ll delete that in a new version.

Step 5 - can you create a keyring on your home-machine? you can upload those dirs and the keyring via http://FTP.
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.2.6 (SunOS)

iEYEARECAAYFAkG4REsACgkQ/ay4pK+rrYPlrQCfYoGU9H5F4TLZpFcap51DQKC0
7qcAoJXmyFxT2R4SqiKJEB1n3efgHzf6
=yKgU
—–END PGP SIGNATURE—–

#5 Dominik schrieb am 2004-12-09 um 13:04 Uhr:

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA1

It looks quite good, but I get an error:

Fatal error: Cannot redeclare add_magic_quotes()
(previously declared in /wp-admin/openpgpcommentadmin.php:13) in
/wp-admin/admin.php on line 20

when trying to install it. Furthermore I can’t do step five, since I
don’t have command line access to my host. Any ideas on how I can fix
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.2.1 (MingW32) - WinPT 0.7.96rc1

iD8DBQFBuD9HCFFxLzl8aXcRAnCoAJ9tfHqZEx/eCBspsHHA04DhcWV5dQCggm/l
1yZKjZhOXit2h9wzoIPuDb4=
=Kfpf
—–END PGP SIGNATURE—–

Pages: [3] 2 1 » Zeige alle

Kommentar schreiben