dss-x — archive

[Clemens Orthacker]

Pim, Thanks for your comment. In this context we should consider using what is called threshold cryptography schemes, however, I'm not aware of support of such schemes in XMLEnc (I might be wrong, though). Basically we could, instead of encrypting the session key for n recipients, encrypt for every of the n recipients a so called 'share' and define an identifier (URN) for the threshold scheme to be used in dss:OptionalInputs/xenc:EncryptionMethod. Provided the existence of such an identifier, the encryption profile would support your usecase out of the box. I will further investigate the issue, Clemens Am Mittwoch, 30. Januar 2008 13:50 schrieben Sie: > Hello Clemens, > > I came across a potential use case for an encryption profile: electronic > tendering (in the context of public procurement in Europe). I'm told > encryption/decryption services would help solve many practical > interoperability issues in this domain. But there is a requirement (in > some countries) that the content can only be decrypted if all participating > key owners agree. This could be done by splitting the generated symmetric > key in parts, with the various parts encrypted using different keys. Could > your profile (be extended to) support this? > > Pim > >