A number of enquiries have been made regarding the fact that Stamper's PGP keys have not been self-signed. The reason (back in 1995) was to ensure that Stamper did not sign anything other than messages via the service. Back then, there was no requirement to self-sign keys.
More recent software such as GnuPG strongly recommend self-signing, and operate with difficulty when presented with non-self-signed keys.
With this in mind, Stamper's PGP key has today been self-signed and the documentation updated.
It was 15 years ago today, on 12 October 1995, that Stamper made its first timestamp!
As there have been issues with the moderation of messages to comp.security.pgp.announce the weekly summaries will henceforth only be posted to alt.security.pgp. The definitive full copies of all daily and weekly postings continue to be available here.
Notwithstanding the lack of any new items here in recent times, Stamper has remained in continuous operation!
I have had to limit the size of messages allowed to pass through Stamper. I have set the limit to approximately 1Mb, which I hope is more than sufficient for everyone. If anyone has a genuine requirement to increase this, please let me know.
Stamper has now moved to its own domain stamper.itconsult.co.uk with new email addresses for the various services. The old addresses will continue to work automatically for the time being. In the future they may return messages advising of the change of addresses.
Also Stamper now incorporates email Proof of Posting Certificates which confirm that an email was requested to be sent to certain addresses at a given time. Please note that this does not authenticate the sender in any way.
The new email addresses are:-
Although still supported, the mechanism for specifying the "mode" of operation within the subject is no longer documented. Its continued use is not recommended.
The address for support is now firstname.lastname@example.org and (surprisingly enough) the list server is now at email@example.com.
The documentation has been extensively rewritten to reflect all these changes.
With the creation of the "comp.security.pgp" hierarchy within Usenet, it now seems more appropriate to post Stamper's weekly signature summaries to comp.security.pgp.announce instead of alt.security.pgp.
Postings have been being made to both groups for a couple of weeks.
However this weekend's posting will be the last to alt.security.pgp. Thereafter postings will only be made to comp.security.pgp.announce.
As usual anyone wishing to receive the weekly postings via email can join the list "stamper-weekly".
I recently observed a problem whereby mail addressed to (say) firstname.lastname@example.org ended up being stamped in text mode in error.
The problem turned out to be that Stamper was relying on the headers of the inbound message to read the destination address. If the message was sent "Bcc" to (say) stamp-clr, the address was not being recognised as "stamp-clr" did not appear in the headers.
I have made amendments to ensure that the destination address is always read from the SMTP envelope of the message and not the headers, which seems to have overcome this particular problem.
All the PGP source code and some of the binaries now include patch level 'a'. The remaining binaries will be updated as soon as new patched versions become available.
The turnaround time of Stamper should now be within about 15 minutes, assuming no connection problems. Previously it could have been up to two hours (or longer if there were connection problems). The list server and responders should also reply within about 15 minutes. This is as a result of Stamper being on a permanent Internet connection.
In addition the daily files generated by Stamper are now being automatically uploaded to the web pages by about 04:00 the day following the date they refer to.
Whilst working on automating the weekly summary postings, I have been able to provide the facility for anyone who wants to to receive daily postings from Stamper of all signatures made the previous day. These postings are the same as the daily files available from stamper-files or from http://stamper.itconsult.co.uk/stamper-files/.
I am not sure that many people will want this facility but, as I am using it internally as part of the automation, I thought I would make it public.
To receive these messages join the list "stamper-daily" in the normal way. This is by sending a message to email@example.com with the line "join stamper-daily" (without the quotes) in the BODY of the message.
Two new features have now been added to Stamper: "header" mode which clearsigns both the headers and the body of a received message and alternative email addresses in order to specify Stamper's mode of operation without having to use the "Subject:" field.
"Header" mode is selected either by putting the word "header" (without the quotes) in the subject line or by sending the messsage to firstname.lastname@example.org.
The other modes can be specified by sending to the following addresses:-
At the suggestion of one of the users, I have added a "clear" mode. In this mode, Stamper will clearsign the body of any message that it is sent. Normally it would have fully armoured the reply. This mode is invoked by putting the word "clear" (without the quotes) in the subject of the message to Stamper.
I have now loaded all the signature and summary files onto my WWW server.
The page address is:-
Please note that they are currently being manually updated and may therefore be a couple of days behind what is available from the list server.
The web address for the Stamper pages has now changed to:-
The previous address will continue to work for the time being, but is not guaranteed in the longer term.
I have put the latest international release of PGP 2.6.3i on those web pages so that they can be downloaded directly.
There is also a new link for Signature & Summary Files. Within the next few days, those files available from the list server will also be available via WWW. These will include all the signatures made by Stamper as well as the weekly summaries.
I have noticed a very intermittent problem which will cause Stamper to occasionally fail to stamp a message.
The symptoms are that "pgp" or "binary" messages will be rejected claiming that the ASCII armour could not be removed, and that "text" messages will simply receive the terms & conditions header without any stamp.
In either case, simply resubmitting the message should get it properly stamped.
This only seems to be happening to a very small number of messages andI shall try to track the problem down as soon as possible. I will post a further announcement when I have found & fixed it.
I. T. Consultancy Limited, Jersey, Channel Islands
Last updated: 25 May 2014