use_name_as_alias is a script that reads a GAIM 2.0 BuddyList file (~/.gaim/blist.xml) and assigns aliases based on the contact's name, but only for contacts without a locally user-defined alias. This feature was present in GAIM 1.5, but was removed in 2.0. It makes use of the ElementTree.py module, which is included.
My Freshmeat Subscriptions are a collection of scripts that let you manage your Freshmeat subscriptions. Currently, it only supports saving your subscriptions' name and URL, and a full XML record for each subscription by means of helper scripts. It is quite simple, yet useful for those who would like to share their freshmeat choices with the world, or whatever.
> I like this plugin very much. Any idea
> when there will be a new version? There
> are some features I am missing, would be
> cool if anybody can update this and add
> some more features! Bye, Paul.
I'm glad oyu like the plugin. I'll be releasing a new version, along with a new release of mod_openpgp in the next few weeks.
News? Well, a Secure Session Initiation Protocol has been implemented. You're gonna LOVE it.
A webmaster has a site on an OpenPGP-enabled Apache server, and wants to avoid having to implement a username/password based login system. So he just implements a signup mechanism that asks users for their pgp public key.
Then, he just adds a special "Login" link to his page, and all Enigform-enabled browsers will be able to click on it, start a session, and be automatically authenticated.
The protocol is a challenge/response mechanism which uses openpgp encryption/decryption to accomplish its goal.
From then on,e ach request that goes to the server will be signed, and have this sesison hash embedded, thus the apache server can determine if the sesison is valid, invalid, or timed-out :)
Re: https and certificates?
> IMHO this method has no advantages over
> good old HTTPS connection and personal
> Using Apache's mod_ssl with
> ExportCertData enabled, you can even do
> deeper checks of the certificate in your
> server-side scripts or use information
> contained therein for script-side
> authentification (see FakeBasicAuth
> option of mod_ssl).
Sure. I said nothing against SSL :) - But you have some important differences:
1) SSL = for the whole connection. it's socked-based. you might not want that.
2) web-of-trust approach versus hierarchy-based approach
3) although you can be your own CA, if you want to avoid the hassle of telling your users to have your root cert into their browsers or whatever, then you need to spend lots of money on ssl certificates.
4) message-based, not socket-based.
5) you can mix openpgp signed requests (which are VERY flexible from web-developers and designers' perspective) over HTTPS.
6) it's good to have alternatives. :)