SignedData Example

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C17929.276428A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I have a new SignedData example that I would like to get some opinions
of.  I have tried it againist the Microsoft CAPI 2.0 system and it
failed to verify, but I know how that code is implemented and it would
fail this case.

I encoded the sequence of authenticated attributes using the DER rules
and hashed it.  Then I encoded the entire message, including the
autenticated attributes, using BER encoding rules - that is the SET OF
is not sorted.  I believe that this constitutes a legal SignedData
message but would like some verification.

Jim

------=_NextPart_000_0001_01C17929.276428A0
Content-Type: application/octet-stream;
	name="s1.bin"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="s1.bin"

MIIBXQYJKoZIhvcNAQcCoIIBTjCCAUoCAQExCTAHBgUrDgMCGjAPBgkqhkiG9w0BBwGgAgQAMYIB
JzCCASMCAQEwJjASMRAwDgYDVQQDEwdDYXJsUlNBAhBGNGvHgABWvBHTbi7EELOwMAcGBSsOAwIa
oF0wHAYJKoZIhvcNAQkFMQ8XDTAxMTEzMDA2NTMwNVowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEH
ATAjBgkqhkiG9w0BCQQxFgQU2jmj7l5rSw0yVb/vlWAYkK/YBwkwCwYJKoZIhvcNAQEBBIGAoCN+
9nLwUfXsv+zCfyNFgBQsSC5fhtBbSe7RazOkTocs0qqJrawVqHRsGVtaFASYyeJid/Vrv6djODog
YPmjuVMiuEQQphR6INI4ue4qrjTQGkvb8zK+NLHOwAOBxqGs6X6dfg8MLOu//+YSoN2sovC558rI
4A8+jUtZyxhTC84=

------=_NextPart_000_0001_01C17929.276428A0--