Created attachment 24187 [details] Affected document, unsigned and signed, and a key pair used. It appears that the c14n algorithm is outputting xmlns:xml in certain conditions even when set to the usual/presumed value, which is improper. A kit to help reproduce is attached. From exchanging email with Sean, I believe the trigger for this is probably the poor choice (but not outright bug) of including the xml prefix in the inclusive prefix parameter. If so, only exclusive would be broken, and only with this trigger. We agree that identifying the prefix there is a bad idea, but it's not illegal and it doesn't change the algorithm, so it should get fixed here also.
Fixed in main trunk.