Thanks for the quick feedback everyone. Of course we would have liked to avoid this situation altogether, but anyone who is familiar with phasing out legacy systems knows what kind of unfortunate obstacles can arise. Allow me to explain this in a little more detail, at the risk of ending up in a bikeshedding discussion. :)
Currently, tickets are being signed by a very old server, running an unsupported legacy OS and GNUPG1. In the beginning of the year, we tried phasing this server out and handle signing from one of our standard platforms running GNUPG2. That box signs emails very well, however our legacy ticketing refuses to play nice with it. We spent many, many hours on getting it our ticketing system to behave, but to no avail. The result was that we rolled back to the old solution, followed by this announcement:
http://www.ripe.net/ripe/mail/archives/ncc-services-wg/2013-January/001968.htmlThe proposal to discontinue ticket signing would be a temporary measure to allow an easier transition. That's all we're asking for.
After we have migrated to a new platform, of course we can re-install the signing of e-mails if this is desired by the Community. Some of you have asked for a time indication for this transition period, but that is very hard to predict at this time as we have yet to decide on a new ticketing system and implementation plan.
If the membership feels that a having any period, no matter how short, without these emails being signed is unacceptable then we will have to return with an alternative solution.
Again, your feedback is very valuable in helping us with our planning. Please let me know if you have any questions.
Cheers,
-Alex