Different/bad signature output format for RSA/EC keys

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Different/bad signature output format for RSA/EC keys

Peter Popovec
Hi,

I found some difference in pkcs15-crypt output for usage with RSA/EC keys.

Please, check the following two examples of file signing:


# create testing file
$ echo "test" > testfile.txt
# create sha1 hash of testing file in binary form:
$ sha1sum testfile.txt|cut -d ' ' -f 1|xxd -p -r > testfile.txt.sha1
# store testing RSA key to (initialized) card:
$ pkcs15-init --store-private-key keys/testTEST.key --pin 1111 --auth-id=1
# then I sign the testing file:
$ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
# verification of this signature by openssl:
$ openssl dgst -sha1 -verify  keys/testTEST.pub -signature testfile.txt.sha1.signature  testfile.txt
Verified OK

This seems to be expected behavior. I repeat this with EC key:

#store testing EC key to (initialized) card
$ pkcs15-init --store-private-key keys/prime192v1-key.pem  --auth-id=1 --pin 1111
# extract public part directly from card:
$ pkcs15-tool --list-public-keys
Public EC Key [Public Key]
        Object Flags   : [0x2], modifiable
        Usage          : [0x40], verify
        Access Flags   : [0x0]
        FieldLength    : 192
        Key ref        : 0 (0x0)
        Native         : no
        Path           : 3f0050155501
        ID             : 55e1379c931514e60f9a6f4f687fa79e69b90159
#
$ pkcs15-tool --read-public-key 55e1379c931514e60f9a6f4f687fa79e69b90159 > keys/prime192v1-pub.pem
# Or we can use:
$ openssl ec -in keys/prime192v1-key.pem -pubout > keys/prime192v1-pub.pem
# Now signature is generated:
$ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
# verifing signature:
$ openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1  testfile.txtError Verifying Data
140316864693904:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1345:
140316864693904:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:388:Type=ECDSA_SIG

This should work in my opinion in the same way as with use of RSA key ...  but this does not work.

By inspection of signature:

$ hexdump -C testfile.txt.sha1.signature
00000000  b7 0f f5 1b 85 e1 3c 91  3d ef 3f 7a 30 ef 95 bf  |......<.=.?z0...|
00000010  95 c7 8c 8b 4d 98 3c 4f  80 97 09 05 93 29 41 5c  |....M.<O.....)A\|
00000020  21 a5 3f 01 ea ff 8b 38  bb 43 93 f4 cf fc 61 7f  |!.?....8.C....a.|
00000030

seems to be some missing tags in this file.


I add these missing tags:

(echo -n -e "06\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24; echo -e -n "\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24 skip=24)2>/dev/null > testfile.txt.sha1.signature.corrected

Corrected signature dump:

$ hexdump -C testfile.txt.sha1.signature.corrected
00000000  30 36 02 19 00 b7 0f f5  1b 85 e1 3c 91 3d ef 3f  |06.........<.=.?|
00000010  7a 30 ef 95 bf 95 c7 8c  8b 4d 98 3c 4f 02 19 00  |z0.......M.<O...|
00000020  80 97 09 05 93 29 41 5c  21 a5 3f 01 ea ff 8b 38  |.....)A\!.?....8|
00000030  bb 43 93 f4 cf fc 61 7f                           |.C....a.|
00000038

Then signature verification:

openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1.signature.corrected  testfile.txt
Verified OK

Do You think that this behavior is correct or this is (pkcs15-crypt) design error ?

Thanks.


------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Different/bad signature output format for RSA/EC keys

Anders Rundgren-2
On 2015-04-14 15:10, Peter Popovec wrote:
> Hi,
>
> I found some difference in pkcs15-crypt output for usage with RSA/EC keys.

I have limited insight in OpenSC and PKCS #15 but there are unfortunately
two different signature formats for EC.  XML DSig uses a different
signature format than X.509 certificate signatures.
OpenSSL uses the (old) X.509 ASN.1 DER-encoded format.

The following code shows the differences:
https://github.com/cyberphone/openkeystore/blob/master/library/src/org/webpki/crypto/SignatureWrapper.java

Anders

>
> Please, check the following two examples of file signing:
>
>
> # create testing file
> $ echo "test" > testfile.txt
> # create sha1 hash of testing file in binary form:
> $ sha1sum testfile.txt|cut -d ' ' -f 1|xxd -p -r > testfile.txt.sha1
> # store testing RSA key to (initialized) card:
> $ pkcs15-init --store-private-key keys/testTEST.key --pin 1111 --auth-id=1
> # then I sign the testing file:
> $ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
> # verification of this signature by openssl:
> $ openssl dgst -sha1 -verify  keys/testTEST.pub -signature testfile.txt.sha1.signature  testfile.txt
> Verified OK
>
> This seems to be expected behavior. I repeat this with EC key:
>
> #store testing EC key to (initialized) card
> $ pkcs15-init --store-private-key keys/prime192v1-key.pem  --auth-id=1 --pin 1111
> # extract public part directly from card:
> $ pkcs15-tool --list-public-keys
> Public EC Key [Public Key]
>          Object Flags   : [0x2], modifiable
>          Usage          : [0x40], verify
>          Access Flags   : [0x0]
>          FieldLength    : 192
>          Key ref        : 0 (0x0)
>          Native         : no
>          Path           : 3f0050155501
>          ID             : 55e1379c931514e60f9a6f4f687fa79e69b90159
> #
> $ pkcs15-tool --read-public-key 55e1379c931514e60f9a6f4f687fa79e69b90159 > keys/prime192v1-pub.pem
> # Or we can use:
> $ openssl ec -in keys/prime192v1-key.pem -pubout > keys/prime192v1-pub.pem
> # Now signature is generated:
> $ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
> # verifing signature:
> $ openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1  testfile.txtError Verifying Data
> 140316864693904:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1345:
> 140316864693904:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:388:Type=ECDSA_SIG
>
> This should work in my opinion in the same way as with use of RSA key ...  but this does not work.
>
> By inspection of signature:
>
> $ hexdump -C testfile.txt.sha1.signature
> 00000000  b7 0f f5 1b 85 e1 3c 91  3d ef 3f 7a 30 ef 95 bf  |......<.=.?z0...|
> 00000010  95 c7 8c 8b 4d 98 3c 4f  80 97 09 05 93 29 41 5c  |....M.<O.....)A\|
> 00000020  21 a5 3f 01 ea ff 8b 38  bb 43 93 f4 cf fc 61 7f  |!.?....8.C....a.|
> 00000030
>
> seems to be some missing tags in this file.
>
>
> I add these missing tags:
>
> (echo -n -e "06\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24; echo -e -n "\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24 skip=24)2>/dev/null > testfile.txt.sha1.signature.corrected
>
> Corrected signature dump:
>
> $ hexdump -C testfile.txt.sha1.signature.corrected
> 00000000  30 36 02 19 00 b7 0f f5  1b 85 e1 3c 91 3d ef 3f  |06.........<.=.?|
> 00000010  7a 30 ef 95 bf 95 c7 8c  8b 4d 98 3c 4f 02 19 00  |z0.......M.<O...|
> 00000020  80 97 09 05 93 29 41 5c  21 a5 3f 01 ea ff 8b 38  |.....)A\!.?....8|
> 00000030  bb 43 93 f4 cf fc 61 7f                           |.C....a.|
> 00000038
>
> Then signature verification:
>
> openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1.signature.corrected  testfile.txt
> Verified OK
>
> Do You think that this behavior is correct or this is (pkcs15-crypt) design error ?
>
> Thanks.
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>
>
>
> _______________________________________________
> Opensc-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>


------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Different/bad signature output format for RSA/EC keys

Viktor Tarasov-3
In current master branch
the pkcs15-crypt tool has 'output signature format' option added.

  -f, --signature-format <arg>  Format for ECDSA signature <arg>: 'rs' (default), 'sequence', 'openssl'


On 04/14/2015 03:16 PM, Anders Rundgren wrote:

> On 2015-04-14 15:10, Peter Popovec wrote:
>> Hi,
>>
>> I found some difference in pkcs15-crypt output for usage with RSA/EC keys.
> I have limited insight in OpenSC and PKCS #15 but there are unfortunately
> two different signature formats for EC.  XML DSig uses a different
> signature format than X.509 certificate signatures.
> OpenSSL uses the (old) X.509 ASN.1 DER-encoded format.
>
> The following code shows the differences:
> https://github.com/cyberphone/openkeystore/blob/master/library/src/org/webpki/crypto/SignatureWrapper.java
>
> Anders
>
>> Please, check the following two examples of file signing:
>>
>>
>> # create testing file
>> $ echo "test" > testfile.txt
>> # create sha1 hash of testing file in binary form:
>> $ sha1sum testfile.txt|cut -d ' ' -f 1|xxd -p -r > testfile.txt.sha1
>> # store testing RSA key to (initialized) card:
>> $ pkcs15-init --store-private-key keys/testTEST.key --pin 1111 --auth-id=1
>> # then I sign the testing file:
>> $ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
>> # verification of this signature by openssl:
>> $ openssl dgst -sha1 -verify  keys/testTEST.pub -signature testfile.txt.sha1.signature  testfile.txt
>> Verified OK
>>
>> This seems to be expected behavior. I repeat this with EC key:
>>
>> #store testing EC key to (initialized) card
>> $ pkcs15-init --store-private-key keys/prime192v1-key.pem  --auth-id=1 --pin 1111
>> # extract public part directly from card:
>> $ pkcs15-tool --list-public-keys
>> Public EC Key [Public Key]
>>           Object Flags   : [0x2], modifiable
>>           Usage          : [0x40], verify
>>           Access Flags   : [0x0]
>>           FieldLength    : 192
>>           Key ref        : 0 (0x0)
>>           Native         : no
>>           Path           : 3f0050155501
>>           ID             : 55e1379c931514e60f9a6f4f687fa79e69b90159
>> #
>> $ pkcs15-tool --read-public-key 55e1379c931514e60f9a6f4f687fa79e69b90159 > keys/prime192v1-pub.pem
>> # Or we can use:
>> $ openssl ec -in keys/prime192v1-key.pem -pubout > keys/prime192v1-pub.pem
>> # Now signature is generated:
>> $ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
>> # verifing signature:
>> $ openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1  testfile.txtError Verifying Data
>> 140316864693904:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1345:
>> 140316864693904:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:388:Type=ECDSA_SIG
>>
>> This should work in my opinion in the same way as with use of RSA key ...  but this does not work.
>>
>> By inspection of signature:
>>
>> $ hexdump -C testfile.txt.sha1.signature
>> 00000000  b7 0f f5 1b 85 e1 3c 91  3d ef 3f 7a 30 ef 95 bf  |......<.=.?z0...|
>> 00000010  95 c7 8c 8b 4d 98 3c 4f  80 97 09 05 93 29 41 5c  |....M.<O.....)A\|
>> 00000020  21 a5 3f 01 ea ff 8b 38  bb 43 93 f4 cf fc 61 7f  |!.?....8.C....a.|
>> 00000030
>>
>> seems to be some missing tags in this file.
>>
>>
>> I add these missing tags:
>>
>> (echo -n -e "06\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24; echo -e -n "\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24 skip=24)2>/dev/null > testfile.txt.sha1.signature.corrected
>>
>> Corrected signature dump:
>>
>> $ hexdump -C testfile.txt.sha1.signature.corrected
>> 00000000  30 36 02 19 00 b7 0f f5  1b 85 e1 3c 91 3d ef 3f  |06.........<.=.?|
>> 00000010  7a 30 ef 95 bf 95 c7 8c  8b 4d 98 3c 4f 02 19 00  |z0.......M.<O...|
>> 00000020  80 97 09 05 93 29 41 5c  21 a5 3f 01 ea ff 8b 38  |.....)A\!.?....8|
>> 00000030  bb 43 93 f4 cf fc 61 7f                           |.C....a.|
>> 00000038
>>
>> Then signature verification:
>>
>> openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1.signature.corrected  testfile.txt
>> Verified OK
>>
>> Do You think that this behavior is correct or this is (pkcs15-crypt) design error ?
>>
>> Thanks.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>>
>>
>>
>> _______________________________________________
>> Opensc-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Opensc-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>


------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel
Reply | Threaded
Open this post in threaded view
|

Re: Different/bad signature output format for RSA/EC keys

Peter Popovec
Hi,

Thanks for hint,  this switch (--signature-format "openssl")  does what I need.

(my fault, switch is not mentioned in the manual page, but can be found in pkcs11-tool --help or pkcs15-crypt --help)





On Tue, Apr 14, 2015 at 3:36 PM, Viktor Tarasov <[hidden email]> wrote:
In current master branch
the pkcs15-crypt tool has 'output signature format' option added.

  -f, --signature-format <arg>  Format for ECDSA signature <arg>: 'rs' (default), 'sequence', 'openssl'


On 04/14/2015 03:16 PM, Anders Rundgren wrote:
> On 2015-04-14 15:10, Peter Popovec wrote:
>> Hi,
>>
>> I found some difference in pkcs15-crypt output for usage with RSA/EC keys.
> I have limited insight in OpenSC and PKCS #15 but there are unfortunately
> two different signature formats for EC.  XML DSig uses a different
> signature format than X.509 certificate signatures.
> OpenSSL uses the (old) X.509 ASN.1 DER-encoded format.
>
> The following code shows the differences:
> https://github.com/cyberphone/openkeystore/blob/master/library/src/org/webpki/crypto/SignatureWrapper.java
>
> Anders
>
>> Please, check the following two examples of file signing:
>>
>>
>> # create testing file
>> $ echo "test" > testfile.txt
>> # create sha1 hash of testing file in binary form:
>> $ sha1sum testfile.txt|cut -d ' ' -f 1|xxd -p -r > testfile.txt.sha1
>> # store testing RSA key to (initialized) card:
>> $ pkcs15-init --store-private-key keys/testTEST.key --pin 1111 --auth-id=1
>> # then I sign the testing file:
>> $ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
>> # verification of this signature by openssl:
>> $ openssl dgst -sha1 -verify  keys/testTEST.pub -signature testfile.txt.sha1.signature  testfile.txt
>> Verified OK
>>
>> This seems to be expected behavior. I repeat this with EC key:
>>
>> #store testing EC key to (initialized) card
>> $ pkcs15-init --store-private-key keys/prime192v1-key.pem  --auth-id=1 --pin 1111
>> # extract public part directly from card:
>> $ pkcs15-tool --list-public-keys
>> Public EC Key [Public Key]
>>           Object Flags   : [0x2], modifiable
>>           Usage          : [0x40], verify
>>           Access Flags   : [0x0]
>>           FieldLength    : 192
>>           Key ref        : 0 (0x0)
>>           Native         : no
>>           Path           : 3f0050155501
>>           ID             : 55e1379c931514e60f9a6f4f687fa79e69b90159
>> #
>> $ pkcs15-tool --read-public-key 55e1379c931514e60f9a6f4f687fa79e69b90159 > keys/prime192v1-pub.pem
>> # Or we can use:
>> $ openssl ec -in keys/prime192v1-key.pem -pubout > keys/prime192v1-pub.pem
>> # Now signature is generated:
>> $ pkcs15-crypt  -s --sha-1 -i testfile.txt.sha1 --pkcs1 --pin=1111 -o testfile.txt.sha1.signature
>> # verifing signature:
>> $ openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1  testfile.txtError Verifying Data
>> 140316864693904:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1345:
>> 140316864693904:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:388:Type=ECDSA_SIG
>>
>> This should work in my opinion in the same way as with use of RSA key ...  but this does not work.
>>
>> By inspection of signature:
>>
>> $ hexdump -C testfile.txt.sha1.signature
>> 00000000  b7 0f f5 1b 85 e1 3c 91  3d ef 3f 7a 30 ef 95 bf  |......<.=.?z0...|
>> 00000010  95 c7 8c 8b 4d 98 3c 4f  80 97 09 05 93 29 41 5c  |....M.<O.....)A\|
>> 00000020  21 a5 3f 01 ea ff 8b 38  bb 43 93 f4 cf fc 61 7f  |!.?....8.C....a.|
>> 00000030
>>
>> seems to be some missing tags in this file.
>>
>>
>> I add these missing tags:
>>
>> (echo -n -e "06\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24; echo -e -n "\002\031\000";dd if=testfile.txt.sha1.signature bs=1 count=24 skip=24)2>/dev/null > testfile.txt.sha1.signature.corrected
>>
>> Corrected signature dump:
>>
>> $ hexdump -C testfile.txt.sha1.signature.corrected
>> 00000000  30 36 02 19 00 b7 0f f5  1b 85 e1 3c 91 3d ef 3f  |06.........<.=.?|
>> 00000010  7a 30 ef 95 bf 95 c7 8c  8b 4d 98 3c 4f 02 19 00  |z0.......M.<O...|
>> 00000020  80 97 09 05 93 29 41 5c  21 a5 3f 01 ea ff 8b 38  |.....)A\!.?....8|
>> 00000030  bb 43 93 f4 cf fc 61 7f                           |.C....a.|
>> 00000038
>>
>> Then signature verification:
>>
>> openssl dgst -sha1 -verify  keys/prime192v1-pub.pem  -signature testfile.txt.sha1.signature.corrected  testfile.txt
>> Verified OK
>>
>> Do You think that this behavior is correct or this is (pkcs15-crypt) design error ?
>>
>> Thanks.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>>
>>
>>
>> _______________________________________________
>> Opensc-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Opensc-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>


------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel


------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel