Re: [opensc-devel] new release?

[Viktor Tarasov]

Hello,

New release candidate is tagged as '0.13.0rc1' -- commit 6b7d8af0 of github 
OpenSC/OpenSC.git.

The tarball, MSI and SuSE RPM can be downloaded from
http://www.opensc-project.org/downloads/projects/opensc/releases/
or directly from CI service
https://opensc.fr/jenkins/

Here listed the changes since '0.13.0pre1' (only 'essential'):
40ff0e4e pkcs11: Fixed SIGV when deleting public key objects via PKCS#11
c91f0e84 entersafe: Disable RSA:512bits that modified in entersafe_generate_key 
and entersafe_store_key function
72786abe sc-hsm: Added write support for RSA and ECC keys, certificates and 
data objects
a9393aa9 framework-pkcs15: Fixed a SIGV when key generation returned 
ERROR_NOT_SUPPORTED
1619a423 ecc: Adding more curves
db3f5f5f framework-pkcs15: Fixed issued with uninitialized variable keysize
f508b212 pkcs15: Add support to encode EC private key description
02fe6d47 pkcs11-tool: Fixed issue with ID increment failing on constant data
249b769a pkcs11: unlink 'pubkey' FW object when deleting related certificate
ea40e7fe Use AM_CPPFLAGS instead of INCLUDES
3656b478 Use AX_PTHREAD instead of ACX_PTHREAD
d525ca97 libopensc: OID with only zeros in array do not valid

Thanks for your participation.

There are still few issues inherited from pre1:
- building MAC OS X packages (waiting for someone who know/can/will to bring 
more details on this problem);
- ePass2003 signing problem -- seems to be related with pkcs11 engine ...
- ... and as a consequence -- need to be tested with engine;
- still to be tested smartcard logon.

Kind regards,
Viktor.


Le 26/09/2012 11:12, Viktor Tarasov a écrit :
> Hello Andreas.
>
> On Tue, Sep 25, 2012 at 8:07 PM, Andreas Schwier 
> mailto:andreas.schw...@cardcontact.de>> 
> wrote:
>
> we are testing on Windows XP SP3, Debian Lenny and a current Ubuntu
> version. Our focus is on PKCS#11 and integration with Firefox,
> Thunderbird and XCA. We already tested minidriver with IE and Outlook,
> but we do short regression tests with each new build.
>
>  
> Ok, thanks. 
>
>
> We've set up automated tests using our Smart Card Shell, which
> interfaces with PKCS#11 using opensc-java. This way we test key
> generation of all kinds (RSA/EC), certificates issuance and storing as
> well as data element reading/writing. We also have a quick regression
> test using a script with various pkcs11-tool commands. We've also done
> tests using the IAIK PKCS#11 wrapper that worked well.
>
>
> Your automated tests are triggered-by/pulled-from your-branch/opensc-opensc 
> github ?
>
> Do you see any interest in connecting your automated tests to the common 
> OpenSC CI service ?
> https://opensc.fr/jenkins/
>
>
>
> So far we're quite confident that the current code base is stable.
>
> We have three things left on our list, but they are not pressing:
>
> 1. Adding support to have domain parameter at the PKCS#11 interface for
> EC public keys after on card generation (i.e. serialize/ deserialize
> public keys as spki)
> 2. Adding support for explicit domain parameter in EC_PARAMS
> 3. Fast-track C_Initialize and C_SetPIN into the card-driver (The
> SmartCard-HSM uses a PKCS#11 like token initialization)
>
> Given the fact, that these changes touch core code, we would schedule
> this topics for the .14 release.
>
> Andreas
>
> Am 25.09.2012 17:04, schrieb Viktor Tarasov:
> > Hi Andreas,
> >
> > On Tue, Sep 25, 2012 at 9:14 AM, Andreas Schwier
> > mailto:andreas.schw...@cardcontact.de>
> >  >> wrote:
> >
> > we've completed the development of write support for the 
> SmartCard-HSM
> > and are in the middle of testing and bug-fixing.
> >
> >
> > Fine,
> > what part of the common OpenSC libraries are involved into your tests
> > (pkcs11, minidriver, pkcs15, ...) ?
> > What are the OSs?
> >
> >
> >
> >
> > The code is based on the latest version in OpenSC/staging and 
> changes
> > mostly apply to our own code.
> >
> > Is there a chance to get write support into the upcomin release ?
> >
> > If yes, I would prepare a pull request against the 
> CardContact/staging
> > branch.
> >
> >
> > Ok,
> > you can make pull request to 'staging' or 'master' of OpenSC/OpenSC --
> > two branches are kept syncronized.
> >
> >
> > Andreas
> >
> >
> > Kind wishes,
> > Viktor.
> >
> >
> >
> >
> >
> > Am 17.09.2012 22:00, schrieb Viktor Tarasov:
> > > Hello,
> > >
> > > Le 15/09/2012 16:52, Kalev Lember a écrit :
> > >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
> > >>> Hello,
> > >>>
> > >>> current github 'staging' is tagged as v0.13.0-pre1.
> > >>>
> > >>> If no objection

Re: [opensc-devel] new release?

[Andreas Schwier]

Hi Viktor,

I've created a pull request into staging for adding SmartCard-HSM write
support.

Andreas

Am 25.09.2012 17:04, schrieb Viktor Tarasov:
> Hi Andreas,
>
> On Tue, Sep 25, 2012 at 9:14 AM, Andreas Schwier
>  > wrote:
>
> we've completed the development of write support for the SmartCard-HSM
> and are in the middle of testing and bug-fixing.
>
>
> Fine, 
> what part of the common OpenSC libraries are involved into your tests
> (pkcs11, minidriver, pkcs15, ...) ?
> What are the OSs?
>
>  
>
>
> The code is based on the latest version in OpenSC/staging and changes
> mostly apply to our own code.
>
> Is there a chance to get write support into the upcomin release ?
>
> If yes, I would prepare a pull request against the CardContact/staging
> branch.
>
>
> Ok, 
> you can make pull request to 'staging' or 'master' of OpenSC/OpenSC --
> two branches are kept syncronized.
>
>
> Andreas
>
>
> Kind wishes,
> Viktor.
>  
>
>
>
>
> Am 17.09.2012 22:00, schrieb Viktor Tarasov:
> > Hello,
> >
> > Le 15/09/2012 16:52, Kalev Lember a écrit :
> >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
> >>> Hello,
> >>>
> >>> current github 'staging' is tagged as v0.13.0-pre1.
> >>>
> >>> If no objections, I will merge this branch into github
> 'master' -- it will be base version to test
> >>> and to prepare the coming release candidate.
> >> Very good idea. I think it makes a lot of sense to have just one
> >> 'master' branch for development; this is what people coming
> over from
> >> other projects tend to expect.
> >
> > 'Master' and 'staging' are actually synchronized and for the new
> pull requests I propose to create them relative to the 'master'
> branch.
> > Until the end of this release the pull requests to 'staging' are
> also accepted.
> >
> > The tag name 'v0.13.0-pre1' has been changed (sorry) to
> '0.13.0pre1' -- still cannot understand which common set of characters
> > could be used for the release-version/tag-name to satisfy 'git',
> 'obs', 'dpkg-build', ...
> >
> > Commits to 'master' and new tags trigger the jenkins jobs of
> build, packaging and some rudimentary test of package and unit
> tests (for Suse).
> > https://opensc.fr/jenkins/view/Open
> SC-release/
> 
> >
> > The resulting packages are transfered to 'download' part of the
> opensc-project.org  file server:
> >  - commits to
> > http://www.opensc-project.org/downloads/projects/opensc/nightly/
> >  - releases to
> >
> http://www.opensc-project.org/downloads/projects/opensc/releases/
> >
> >
> > For a while there are only source tarballs, MSIs for x32 and x64
> and rpm i586 for opensSuSE 12.1 .
> > Hope that rapidly the building of releases packages for some
> debian/ubuntu distributions will be connected.
> >
> > It would be nice if you could look/test the tarball or packages
> of the release 0.13.0pre1.
> > Your remarks, proposals, contributions are heartily welcome.
> >
> > Kind regards,
> > Viktor.
> > ___
> > opensc-devel mailing list
> > opensc-devel@lists.opensc-project.org
> 
> > http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>
> --
>
> -CardContact Software & System Consulting
>|.##> <##.|   Andreas Schwier
>|#   #|   Schülerweg 38
>|#   #|   32429 Minden, Germany
>|'##> <##'|   Phone +49 571 56149 
> -http://www.cardcontact.de
>  http://www.tscons.de
>  http://www.openscdp.org
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> 
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>


-- 

-CardContact Software & System Consulting
   |.##> <##.|   Andreas Schwier
   |#   #|   Schülerweg 38
   |#   #|   32429 Minden, Germany
   |'##> <##'|   Phone +49 571 56149
-http://www.cardcontact.de
 http://www.tscons.de
 http://www.openscdp.org

___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

Hello Andreas.

On Tue, Sep 25, 2012 at 8:07 PM, Andreas Schwier <
andreas.schw...@cardcontact.de> wrote:

> we are testing on Windows XP SP3, Debian Lenny and a current Ubuntu
> version. Our focus is on PKCS#11 and integration with Firefox,
> Thunderbird and XCA. We already tested minidriver with IE and Outlook,
> but we do short regression tests with each new build.
>

Ok, thanks.


> We've set up automated tests using our Smart Card Shell, which
> interfaces with PKCS#11 using opensc-java. This way we test key
> generation of all kinds (RSA/EC), certificates issuance and storing as
> well as data element reading/writing. We also have a quick regression
> test using a script with various pkcs11-tool commands. We've also done
> tests using the IAIK PKCS#11 wrapper that worked well.
>

Your automated tests are triggered-by/pulled-from your-branch/opensc-opensc
github ?

Do you see any interest in connecting your automated tests to the common
OpenSC CI service ?
https://opensc.fr/jenkins/



> So far we're quite confident that the current code base is stable.
>
> We have three things left on our list, but they are not pressing:
>
> 1. Adding support to have domain parameter at the PKCS#11 interface for
> EC public keys after on card generation (i.e. serialize/ deserialize
> public keys as spki)
> 2. Adding support for explicit domain parameter in EC_PARAMS
> 3. Fast-track C_Initialize and C_SetPIN into the card-driver (The
> SmartCard-HSM uses a PKCS#11 like token initialization)
>
> Given the fact, that these changes touch core code, we would schedule
> this topics for the .14 release.
>
> Andreas
>
> Am 25.09.2012 17:04, schrieb Viktor Tarasov:
> > Hi Andreas,
> >
> > On Tue, Sep 25, 2012 at 9:14 AM, Andreas Schwier
> >  > > wrote:
> >
> > we've completed the development of write support for the
> SmartCard-HSM
> > and are in the middle of testing and bug-fixing.
> >
> >
> > Fine,
> > what part of the common OpenSC libraries are involved into your tests
> > (pkcs11, minidriver, pkcs15, ...) ?
> > What are the OSs?
> >
> >
> >
> >
> > The code is based on the latest version in OpenSC/staging and changes
> > mostly apply to our own code.
> >
> > Is there a chance to get write support into the upcomin release ?
> >
> > If yes, I would prepare a pull request against the
> CardContact/staging
> > branch.
> >
> >
> > Ok,
> > you can make pull request to 'staging' or 'master' of OpenSC/OpenSC --
> > two branches are kept syncronized.
> >
> >
> > Andreas
> >
> >
> > Kind wishes,
> > Viktor.
> >
> >
> >
> >
> >
> > Am 17.09.2012 22:00, schrieb Viktor Tarasov:
> > > Hello,
> > >
> > > Le 15/09/2012 16:52, Kalev Lember a écrit :
> > >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
> > >>> Hello,
> > >>>
> > >>> current github 'staging' is tagged as v0.13.0-pre1.
> > >>>
> > >>> If no objections, I will merge this branch into github
> > 'master' -- it will be base version to test
> > >>> and to prepare the coming release candidate.
> > >> Very good idea. I think it makes a lot of sense to have just one
> > >> 'master' branch for development; this is what people coming
> > over from
> > >> other projects tend to expect.
> > >
> > > 'Master' and 'staging' are actually synchronized and for the new
> > pull requests I propose to create them relative to the 'master'
> > branch.
> > > Until the end of this release the pull requests to 'staging' are
> > also accepted.
> > >
> > > The tag name 'v0.13.0-pre1' has been changed (sorry) to
> > '0.13.0pre1' -- still cannot understand which common set of
> characters
> > > could be used for the release-version/tag-name to satisfy 'git',
> > 'obs', 'dpkg-build', ...
> > >
> > > Commits to 'master' and new tags trigger the jenkins jobs of
> > build, packaging and some rudimentary test of package and unit
> > tests (for Suse).
> > > https://opensc.fr/jenkins/view/Open
> > SC-release/
> > 
> > >
> > > The resulting packages are transfered to 'download' part of the
> > opensc-project.org  file server:
> > >  - commits to
> > >
> http://www.opensc-project.org/downloads/projects/opensc/nightly/
> > >  - releases to
> > >
> > http://www.opensc-project.org/downloads/projects/opensc/releases/
> > >
> > >
> > > For a while there are only source tarballs, MSIs for x32 and x64
> > and rpm i586 for opensSuSE 12.1 .
> > > Hope that rapidly the building of releases packages for some
> > debian/ubuntu distributions will be connected.
> > >
> > > It would be nice if you could look/test the tarball or packages
> > of the release 0.13.0pre1.
> > > Your remarks, proposals, contributions are heartily welcome

Re: [opensc-devel] new release?

[Peter Stuge]

Jean-Michel Pouré - GOOZE wrote:
> I was quite busy and failed to do any work these last days.

Remember how much easier it is to write email with opinion.


//Peter


pgpNhpOSPqCvo.pgp
Description: PGP signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Andreas Schwier]

Hi Viktor,

we are testing on Windows XP SP3, Debian Lenny and a current Ubuntu
version. Our focus is on PKCS#11 and integration with Firefox,
Thunderbird and XCA. We already tested minidriver with IE and Outlook,
but we do short regression tests with each new build.

We've set up automated tests using our Smart Card Shell, which
interfaces with PKCS#11 using opensc-java. This way we test key
generation of all kinds (RSA/EC), certificates issuance and storing as
well as data element reading/writing. We also have a quick regression
test using a script with various pkcs11-tool commands. We've also done
tests using the IAIK PKCS#11 wrapper that worked well.

So far we're quite confident that the current code base is stable.

We have three things left on our list, but they are not pressing:

1. Adding support to have domain parameter at the PKCS#11 interface for
EC public keys after on card generation (i.e. serialize/ deserialize
public keys as spki)
2. Adding support for explicit domain parameter in EC_PARAMS
3. Fast-track C_Initialize and C_SetPIN into the card-driver (The
SmartCard-HSM uses a PKCS#11 like token initialization)

Given the fact, that these changes touch core code, we would schedule
this topics for the .14 release.

Andreas

Am 25.09.2012 17:04, schrieb Viktor Tarasov:
> Hi Andreas,
>
> On Tue, Sep 25, 2012 at 9:14 AM, Andreas Schwier
>  > wrote:
>
> we've completed the development of write support for the SmartCard-HSM
> and are in the middle of testing and bug-fixing.
>
>
> Fine, 
> what part of the common OpenSC libraries are involved into your tests
> (pkcs11, minidriver, pkcs15, ...) ?
> What are the OSs?
>
>  
>
>
> The code is based on the latest version in OpenSC/staging and changes
> mostly apply to our own code.
>
> Is there a chance to get write support into the upcomin release ?
>
> If yes, I would prepare a pull request against the CardContact/staging
> branch.
>
>
> Ok, 
> you can make pull request to 'staging' or 'master' of OpenSC/OpenSC --
> two branches are kept syncronized.
>
>
> Andreas
>
>
> Kind wishes,
> Viktor.
>  
>
>
>
>
> Am 17.09.2012 22:00, schrieb Viktor Tarasov:
> > Hello,
> >
> > Le 15/09/2012 16:52, Kalev Lember a écrit :
> >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
> >>> Hello,
> >>>
> >>> current github 'staging' is tagged as v0.13.0-pre1.
> >>>
> >>> If no objections, I will merge this branch into github
> 'master' -- it will be base version to test
> >>> and to prepare the coming release candidate.
> >> Very good idea. I think it makes a lot of sense to have just one
> >> 'master' branch for development; this is what people coming
> over from
> >> other projects tend to expect.
> >
> > 'Master' and 'staging' are actually synchronized and for the new
> pull requests I propose to create them relative to the 'master'
> branch.
> > Until the end of this release the pull requests to 'staging' are
> also accepted.
> >
> > The tag name 'v0.13.0-pre1' has been changed (sorry) to
> '0.13.0pre1' -- still cannot understand which common set of characters
> > could be used for the release-version/tag-name to satisfy 'git',
> 'obs', 'dpkg-build', ...
> >
> > Commits to 'master' and new tags trigger the jenkins jobs of
> build, packaging and some rudimentary test of package and unit
> tests (for Suse).
> > https://opensc.fr/jenkins/view/Open
> SC-release/
> 
> >
> > The resulting packages are transfered to 'download' part of the
> opensc-project.org  file server:
> >  - commits to
> > http://www.opensc-project.org/downloads/projects/opensc/nightly/
> >  - releases to
> >
> http://www.opensc-project.org/downloads/projects/opensc/releases/
> >
> >
> > For a while there are only source tarballs, MSIs for x32 and x64
> and rpm i586 for opensSuSE 12.1 .
> > Hope that rapidly the building of releases packages for some
> debian/ubuntu distributions will be connected.
> >
> > It would be nice if you could look/test the tarball or packages
> of the release 0.13.0pre1.
> > Your remarks, proposals, contributions are heartily welcome.
> >
> > Kind regards,
> > Viktor.
> > ___
> > opensc-devel mailing list
> > opensc-devel@lists.opensc-project.org
> 
> > http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>
> --
>
> -CardContact Software & System Consulting
>|.##> <##.|   Andreas Schwier
>|#   #|   Schülerweg 38
>|#   #|   32429 Minden, Germany
>|'##> <##'|   Phone +49 571 56149 
>   

Re: [opensc-devel] new release?

[Viktor Tarasov]

Hi Andreas,

On Tue, Sep 25, 2012 at 9:14 AM, Andreas Schwier <
andreas.schw...@cardcontact.de> wrote:

> we've completed the development of write support for the SmartCard-HSM
> and are in the middle of testing and bug-fixing.
>

Fine,
what part of the common OpenSC libraries are involved into your tests
(pkcs11, minidriver, pkcs15, ...) ?
What are the OSs?



>
> The code is based on the latest version in OpenSC/staging and changes
> mostly apply to our own code.
>
> Is there a chance to get write support into the upcomin release ?
>
> If yes, I would prepare a pull request against the CardContact/staging
> branch.
>

Ok,
you can make pull request to 'staging' or 'master' of OpenSC/OpenSC -- two
branches are kept syncronized.


> Andreas
>

Kind wishes,
Viktor.


>
>
>
> Am 17.09.2012 22:00, schrieb Viktor Tarasov:
> > Hello,
> >
> > Le 15/09/2012 16:52, Kalev Lember a écrit :
> >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
> >>> Hello,
> >>>
> >>> current github 'staging' is tagged as v0.13.0-pre1.
> >>>
> >>> If no objections, I will merge this branch into github 'master' -- it
> will be base version to test
> >>> and to prepare the coming release candidate.
> >> Very good idea. I think it makes a lot of sense to have just one
> >> 'master' branch for development; this is what people coming over from
> >> other projects tend to expect.
> >
> > 'Master' and 'staging' are actually synchronized and for the new pull
> requests I propose to create them relative to the 'master' branch.
> > Until the end of this release the pull requests to 'staging' are also
> accepted.
> >
> > The tag name 'v0.13.0-pre1' has been changed (sorry) to '0.13.0pre1' --
> still cannot understand which common set of characters
> > could be used for the release-version/tag-name to satisfy 'git', 'obs',
> 'dpkg-build', ...
> >
> > Commits to 'master' and new tags trigger the jenkins jobs of build,
> packaging and some rudimentary test of package and unit tests (for Suse).
> > https://opensc.fr/jenkins/view/Open <
> https://opensc.fr/jenkins/view/OpenSC-release/>SC-release/ <
> https://opensc.fr/jenkins/view/OpenSC-release/>
> >
> > The resulting packages are transfered to 'download' part of the
> opensc-project.org file server:
> >  - commits to
> > http://www.opensc-project.org/downloads/projects/opensc/nightly/
> >  - releases to
> > http://www.opensc-project.org/downloads/projects/opensc/releases/
> >
> >
> > For a while there are only source tarballs, MSIs for x32 and x64 and rpm
> i586 for opensSuSE 12.1 .
> > Hope that rapidly the building of releases packages for some
> debian/ubuntu distributions will be connected.
> >
> > It would be nice if you could look/test the tarball or packages of the
> release 0.13.0pre1.
> > Your remarks, proposals, contributions are heartily welcome.
> >
> > Kind regards,
> > Viktor.
> > ___
> > opensc-devel mailing list
> > opensc-devel@lists.opensc-project.org
> > http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>
> --
>
> -CardContact Software & System Consulting
>|.##> <##.|   Andreas Schwier
>|#   #|   Schülerweg 38
>|#   #|   32429 Minden, Germany
>|'##> <##'|   Phone +49 571 56149
> -http://www.cardcontact.de
>  http://www.tscons.de
>  http://www.openscdp.org
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

Thunderbird 13.0.1 can now sign e-mail.
I had forgot to uncomment in opensc.conf:

   pin_cache_ignore_user_consent = true;

a new feature of 0.13.0pre1

See:
http://www.opensc-project.org/pipermail/opensc-devel/2012-August/018282.html

--

 Douglas E. Engert  
 Argonne National Laboratory
 9700 South Cass Avenue
 Argonne, Illinois  60439
 (630) 252-5444





smime.p7s
Description: S/MIME Cryptographic Signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Andreas Schwier]

Hi Viktor,

we've completed the development of write support for the SmartCard-HSM
and are in the middle of testing and bug-fixing.

The code is based on the latest version in OpenSC/staging and changes
mostly apply to our own code.

Is there a chance to get write support into the upcomin release ?

If yes, I would prepare a pull request against the CardContact/staging
branch.


Andreas



Am 17.09.2012 22:00, schrieb Viktor Tarasov:
> Hello,
>
> Le 15/09/2012 16:52, Kalev Lember a écrit :
>> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
>>> Hello,
>>>
>>> current github 'staging' is tagged as v0.13.0-pre1.
>>>
>>> If no objections, I will merge this branch into github 'master' -- it will 
>>> be base version to test
>>> and to prepare the coming release candidate.
>> Very good idea. I think it makes a lot of sense to have just one
>> 'master' branch for development; this is what people coming over from
>> other projects tend to expect.
>
> 'Master' and 'staging' are actually synchronized and for the new pull 
> requests I propose to create them relative to the 'master' branch.
> Until the end of this release the pull requests to 'staging' are also 
> accepted.
>
> The tag name 'v0.13.0-pre1' has been changed (sorry) to '0.13.0pre1' -- still 
> cannot understand which common set of characters
> could be used for the release-version/tag-name to satisfy 'git', 'obs', 
> 'dpkg-build', ...
>
> Commits to 'master' and new tags trigger the jenkins jobs of build, packaging 
> and some rudimentary test of package and unit tests (for Suse).
> https://opensc.fr/jenkins/view/Open 
> SC-release/ 
> 
>
> The resulting packages are transfered to 'download' part of the 
> opensc-project.org file server:
>  - commits to
> http://www.opensc-project.org/downloads/projects/opensc/nightly/
>  - releases to
> http://www.opensc-project.org/downloads/projects/opensc/releases/
>
>
> For a while there are only source tarballs, MSIs for x32 and x64 and rpm i586 
> for opensSuSE 12.1 .
> Hope that rapidly the building of releases packages for some debian/ubuntu 
> distributions will be connected.
>
> It would be nice if you could look/test the tarball or packages of the 
> release 0.13.0pre1.
> Your remarks, proposals, contributions are heartily welcome.
>
> Kind regards,
> Viktor.
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel


-- 

-CardContact Software & System Consulting
   |.##> <##.|   Andreas Schwier
   |#   #|   Schülerweg 38
   |#   #|   32429 Minden, Germany
   |'##> <##'|   Phone +49 571 56149
-http://www.cardcontact.de
 http://www.tscons.de
 http://www.openscdp.org

___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Jean-Michel Pouré - GOOZE]

> Thunderbird 13.0.1 complains about the signing certificate usage, 

ePass2003 users also reported an issue about signing certificates:
www.gooze.eu/forums/support/epass2003-as-ca-with-openssl

Kind regards,
-- 
  Jean-Michel Pouré - Gooze - http://www.gooze.eu


smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

Duh, I see you have 32 and 64 bit msi files.

Since I was using 32 bit firefox and Thunderbird, I installed the 32 bit
version on W7 64. It install the clients in \Program Files (x86)\...
but not the Windows\system32\opensc-pkcs11.dll


If I then install the 64 bit msi, it installs the \Program Files\OpenSC\...
and installs Windows\system32\opensc-pkcs11.dll.


Is the intent that the 64 bit msi install 64 bit tools, and opensc.dll
and the 32 bit opensc-pkcs11.dll? Is there a 64 bit opensc-pkcs11.dll?

Firefox 8.0.1 works to a web site.

Thunderbird 13.0.1 complains about the signing certificate usage, but
appears to read the certificates, and TB says the certificate chain is valid
and all the CA certs are listed as trusted for signing e-mail.
This sounds like a Thunderbird bug. Will have to look some more.
but it looks like OpenSC is working.

I was able to sign using TB 13.0.1 on Solaris using a test account.


On 9/24/2012 2:43 PM, Douglas E. Engert wrote:
>
>
> On 9/24/2012 12:52 PM, Viktor Tarasov wrote:
>> On Wed, Sep 19, 2012 at 11:54 PM, Douglas E. Engert > > wrote:
>>
>>  I have been testing 0.13.0-pre1 from tarball listed below.
>>
>>  Builds on Solaris.
>>
>>  works with MIT Kerberos PKINIT and pam_krb5 to login to AD as the KDC.
>>
>>  Can sign Email using thunderbird 13.0.1.
>>
>>  The pkcs11-tool -derive using ECDH works using a PIV test card from NIST
>>  and a card I created. (i.e. using the key frome a card and the cert from
>>  the other card, will produce the same secret key.)
>>
>>
>> Ok, thanks for the testing.
>>
>> In 0.13.0-pre1 there is the bug that concerns the using of non-initialized 
>> OID data.
>> My non-regression tests were done with the current (*d525ca97e3*) 'master' 
>> version:
>>
>> For the OpenSC installed on Linux from tarball
>> the following tests of the where done using the pkcs15 and pkcs11 tools,
>> with the cards 'CardOS v4.3B', 'SetCOS 4.4.1 B', 'Athena', 'Aventra' and 
>> 'Feitian':
>> - erase card (pkcs15-init -E);
>> - initialize (ex. pkcs15-init -C --label "IDX-SCM" -P --auth-id 53434D 
>> --so-pin "12345678" --so-puk "123456" --pin "99" --puk "88");
>> - generate RSA 1024/2048 (depending on card);
>> - import PKCS#12 with user and CA certificates;
>> - get public key from imported or generated key;
>> - sign data using pkcs15-crypt and pkcs11-tool and verify it with openssl;
>> - decrypt the data encypted by openssl;
>>
>> Using Firefox 12.0 and Thunderbird 15.0.1, on Vista, with IAS/ECC card and 
>> OpenSC installed from MSI:
>> - generate key and sign certificate request;
>> - import certificate;
>> - authenticate to access protected web page.
>> - import PKCS#12;
>> - sign mail;
>> - decrypt mail.
>>
>> As for me, still to test are minidriver (IE and outlook), smartcard logon 
>> (windows) and SM (for the cards that support it).
>>
>> Do you have other suggestions for the non-regression tests?
>
> If you have a Windows build, I could test PKCS#11 on Windows 7 with Firefox 
> and Thinderbird.
>
>
>>
>> Kind regards,
>> Viktor.
>>
>>
>>  On 9/17/2012 3:00 PM, Viktor Tarasov wrote:
>>   > Hello,
>>   >
>>   > Le 15/09/2012 16:52, Kalev Lember a écrit :
>>   >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
>>   >>> Hello,
>>   >>>
>>   >>> current github 'staging' is tagged as v0.13.0-pre1.
>>   >>>
>>   >>> If no objections, I will merge this branch into github 'master' -- 
>> it will be base version to test
>>   >>> and to prepare the coming release candidate.
>>   >> Very good idea. I think it makes a lot of sense to have just one
>>   >> 'master' branch for development; this is what people coming over 
>> from
>>   >> other projects tend to expect.
>>   >
>>   >
>>   > 'Master' and 'staging' are actually synchronized and for the new 
>> pull requests I propose to create them relative to the 'master' branch.
>>   > Until the end of this release the pull requests to 'staging' are 
>> also accepted.
>>   >
>>   > The tag name 'v0.13.0-pre1' has been changed (sorry) to '0.13.0pre1' 
>> -- still cannot understand which common set of characters
>>   > could be used for the release-version/tag-name to satisfy 'git', 
>> 'obs', 'dpkg-build', ...
>>   >
>>   > Commits to 'master' and new tags trigger the jenkins jobs of build, 
>> packaging and some rudimentary test of package and unit tests (for Suse).
>>   > https://opensc.fr/jenkins/view/Open 
>> SC-release/ 
>> 
>>   >
>>   > The resulting packages are transfered to 'download' part of the 
>> opensc-project.org  file server:
>>   >   - commits to
>>   > http://www.opensc-project.org/downloads/projects/opensc/nightly/
>>   >   - releases to
>>   > http://www.opensc-project.org/downloads/projects/opensc/releases

Re: [opensc-devel] new release?

[Douglas E. Engert]

On 9/24/2012 12:52 PM, Viktor Tarasov wrote:
> On Wed, Sep 19, 2012 at 11:54 PM, Douglas E. Engert  > wrote:
>
> I have been testing 0.13.0-pre1 from tarball listed below.
>
> Builds on Solaris.
>
> works with MIT Kerberos PKINIT and pam_krb5 to login to AD as the KDC.
>
> Can sign Email using thunderbird 13.0.1.
>
> The pkcs11-tool -derive using ECDH works using a PIV test card from NIST
> and a card I created. (i.e. using the key frome a card and the cert from
> the other card, will produce the same secret key.)
>
>
> Ok, thanks for the testing.
>
> In 0.13.0-pre1 there is the bug that concerns the using of non-initialized 
> OID data.
> My non-regression tests were done with the current (*d525ca97e3*) 'master' 
> version:
>
> For the OpenSC installed on Linux from tarball
> the following tests of the where done using the pkcs15 and pkcs11 tools,
> with the cards 'CardOS v4.3B', 'SetCOS 4.4.1 B', 'Athena', 'Aventra' and 
> 'Feitian':
> - erase card (pkcs15-init -E);
> - initialize (ex. pkcs15-init -C --label "IDX-SCM" -P --auth-id 53434D 
> --so-pin "12345678" --so-puk "123456" --pin "99" --puk "88");
> - generate RSA 1024/2048 (depending on card);
> - import PKCS#12 with user and CA certificates;
> - get public key from imported or generated key;
> - sign data using pkcs15-crypt and pkcs11-tool and verify it with openssl;
> - decrypt the data encypted by openssl;
>
> Using Firefox 12.0 and Thunderbird 15.0.1, on Vista, with IAS/ECC card and 
> OpenSC installed from MSI:
> - generate key and sign certificate request;
> - import certificate;
> - authenticate to access protected web page.
> - import PKCS#12;
> - sign mail;
> - decrypt mail.
>
> As for me, still to test are minidriver (IE and outlook), smartcard logon 
> (windows) and SM (for the cards that support it).
>
> Do you have other suggestions for the non-regression tests?

If you have a Windows build, I could test PKCS#11 on Windows 7 with Firefox and 
Thinderbird.


>
> Kind regards,
> Viktor.
>
>
> On 9/17/2012 3:00 PM, Viktor Tarasov wrote:
>  > Hello,
>  >
>  > Le 15/09/2012 16:52, Kalev Lember a écrit :
>  >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
>  >>> Hello,
>  >>>
>  >>> current github 'staging' is tagged as v0.13.0-pre1.
>  >>>
>  >>> If no objections, I will merge this branch into github 'master' -- 
> it will be base version to test
>  >>> and to prepare the coming release candidate.
>  >> Very good idea. I think it makes a lot of sense to have just one
>  >> 'master' branch for development; this is what people coming over from
>  >> other projects tend to expect.
>  >
>  >
>  > 'Master' and 'staging' are actually synchronized and for the new pull 
> requests I propose to create them relative to the 'master' branch.
>  > Until the end of this release the pull requests to 'staging' are also 
> accepted.
>  >
>  > The tag name 'v0.13.0-pre1' has been changed (sorry) to '0.13.0pre1' 
> -- still cannot understand which common set of characters
>  > could be used for the release-version/tag-name to satisfy 'git', 
> 'obs', 'dpkg-build', ...
>  >
>  > Commits to 'master' and new tags trigger the jenkins jobs of build, 
> packaging and some rudimentary test of package and unit tests (for Suse).
>  > https://opensc.fr/jenkins/view/Open 
> SC-release/ 
> 
>  >
>  > The resulting packages are transfered to 'download' part of the 
> opensc-project.org  file server:
>  >   - commits to
>  > http://www.opensc-project.org/downloads/projects/opensc/nightly/
>  >   - releases to
>  > http://www.opensc-project.org/downloads/projects/opensc/releases/
>  >
>  >
>  > For a while there are only source tarballs, MSIs for x32 and x64 and 
> rpm i586 for opensSuSE 12.1 .
>  > Hope that rapidly the building of releases packages for some 
> debian/ubuntu distributions will be connected.
>  >
>  > It would be nice if you could look/test the tarball or packages of the 
> release 0.13.0pre1.
>  > Your remarks, proposals, contributions are heartily welcome.
>  >
>  > Kind regards,
>  > Viktor.
>  > ___
>  > opensc-devel mailing list
>  > opensc-devel@lists.opensc-project.org 
> 
>  > http://www.opensc-project.org/mailman/listinfo/opensc-devel
>  >
>  >
>
> --
>
>Douglas E. Engert  mailto:deeng...@anl.gov>>
>Argonne National Laboratory
>9700 South Cass Avenue
>Argonne, Illinois  60439
> (630) 252-5444 
>
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org 
> 

Re: [opensc-devel] new release?

[Viktor Tarasov]

On Wed, Sep 19, 2012 at 11:54 PM, Douglas E. Engert wrote:

> I have been testing 0.13.0-pre1 from tarball listed below.
>
> Builds on Solaris.
>
> works with MIT Kerberos PKINIT and pam_krb5 to login to AD as the KDC.
>
> Can sign Email using thunderbird 13.0.1.
>
> The pkcs11-tool -derive using ECDH works using a PIV test card from NIST
> and a card I created. (i.e. using the key frome a card and the cert from
> the other card, will produce the same secret key.)
>

Ok, thanks for the testing.

In 0.13.0-pre1 there is the bug that concerns the using of non-initialized
OID data.
My non-regression tests were done with the current (*d525ca97e3*) 'master'
version:

For the OpenSC installed on Linux from tarball
the following tests of the where done using the pkcs15 and pkcs11 tools,
with the cards 'CardOS v4.3B', 'SetCOS 4.4.1 B', 'Athena', 'Aventra' and
'Feitian':
- erase card (pkcs15-init -E);
- initialize (ex. pkcs15-init -C --label "IDX-SCM" -P --auth-id 53434D
--so-pin "12345678" --so-puk "123456" --pin "99" --puk "88");
- generate RSA 1024/2048 (depending on card);
- import PKCS#12 with user and CA certificates;
- get public key from imported or generated key;
- sign data using pkcs15-crypt and pkcs11-tool and verify it with openssl;
- decrypt the data encypted by openssl;

Using Firefox 12.0 and Thunderbird 15.0.1, on Vista, with IAS/ECC card and
OpenSC installed from MSI:
- generate key and sign certificate request;
- import certificate;
- authenticate to access protected web page.
- import PKCS#12;
- sign mail;
- decrypt mail.

As for me, still to test are minidriver (IE and outlook), smartcard logon
(windows) and SM (for the cards that support it).

Do you have other suggestions for the non-regression tests?

Kind regards,
Viktor.



>
> On 9/17/2012 3:00 PM, Viktor Tarasov wrote:
> > Hello,
> >
> > Le 15/09/2012 16:52, Kalev Lember a écrit :
> >> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
> >>> Hello,
> >>>
> >>> current github 'staging' is tagged as v0.13.0-pre1.
> >>>
> >>> If no objections, I will merge this branch into github 'master' -- it
> will be base version to test
> >>> and to prepare the coming release candidate.
> >> Very good idea. I think it makes a lot of sense to have just one
> >> 'master' branch for development; this is what people coming over from
> >> other projects tend to expect.
> >
> >
> > 'Master' and 'staging' are actually synchronized and for the new pull
> requests I propose to create them relative to the 'master' branch.
> > Until the end of this release the pull requests to 'staging' are also
> accepted.
> >
> > The tag name 'v0.13.0-pre1' has been changed (sorry) to '0.13.0pre1' --
> still cannot understand which common set of characters
> > could be used for the release-version/tag-name to satisfy 'git', 'obs',
> 'dpkg-build', ...
> >
> > Commits to 'master' and new tags trigger the jenkins jobs of build,
> packaging and some rudimentary test of package and unit tests (for Suse).
> > https://opensc.fr/jenkins/view/Open <
> https://opensc.fr/jenkins/view/OpenSC-release/>SC-release/ <
> https://opensc.fr/jenkins/view/OpenSC-release/>
> >
> > The resulting packages are transfered to 'download' part of the
> opensc-project.org file server:
> >   - commits to
> >  http://www.opensc-project.org/downloads/projects/opensc/nightly/
> >   - releases to
> >  http://www.opensc-project.org/downloads/projects/opensc/releases/
> >
> >
> > For a while there are only source tarballs, MSIs for x32 and x64 and rpm
> i586 for opensSuSE 12.1 .
> > Hope that rapidly the building of releases packages for some
> debian/ubuntu distributions will be connected.
> >
> > It would be nice if you could look/test the tarball or packages of the
> release 0.13.0pre1.
> > Your remarks, proposals, contributions are heartily welcome.
> >
> > Kind regards,
> > Viktor.
> > ___
> > opensc-devel mailing list
> > opensc-devel@lists.opensc-project.org
> > http://www.opensc-project.org/mailman/listinfo/opensc-devel
> >
> >
>
> --
>
>   Douglas E. Engert  
>   Argonne National Laboratory
>   9700 South Cass Avenue
>   Argonne, Illinois  60439
>   (630) 252-5444
>
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

I have been testing 0.13.0-pre1 from tarball listed below.

Builds on Solaris.

works with MIT Kerberos PKINIT and pam_krb5 to login to AD as the KDC.

Can sign Email using thunderbird 13.0.1.

The pkcs11-tool -derive using ECDH works using a PIV test card from NIST
and a card I created. (i.e. using the key frome a card and the cert from
the other card, will produce the same secret key.)

On 9/17/2012 3:00 PM, Viktor Tarasov wrote:
> Hello,
>
> Le 15/09/2012 16:52, Kalev Lember a écrit :
>> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
>>> Hello,
>>>
>>> current github 'staging' is tagged as v0.13.0-pre1.
>>>
>>> If no objections, I will merge this branch into github 'master' -- it will 
>>> be base version to test
>>> and to prepare the coming release candidate.
>> Very good idea. I think it makes a lot of sense to have just one
>> 'master' branch for development; this is what people coming over from
>> other projects tend to expect.
>
>
> 'Master' and 'staging' are actually synchronized and for the new pull 
> requests I propose to create them relative to the 'master' branch.
> Until the end of this release the pull requests to 'staging' are also 
> accepted.
>
> The tag name 'v0.13.0-pre1' has been changed (sorry) to '0.13.0pre1' -- still 
> cannot understand which common set of characters
> could be used for the release-version/tag-name to satisfy 'git', 'obs', 
> 'dpkg-build', ...
>
> Commits to 'master' and new tags trigger the jenkins jobs of build, packaging 
> and some rudimentary test of package and unit tests (for Suse).
> https://opensc.fr/jenkins/view/Open 
> SC-release/ 
> 
>
> The resulting packages are transfered to 'download' part of the 
> opensc-project.org file server:
>   - commits to
>  http://www.opensc-project.org/downloads/projects/opensc/nightly/
>   - releases to
>  http://www.opensc-project.org/downloads/projects/opensc/releases/
>
>
> For a while there are only source tarballs, MSIs for x32 and x64 and rpm i586 
> for opensSuSE 12.1 .
> Hope that rapidly the building of releases packages for some debian/ubuntu 
> distributions will be connected.
>
> It would be nice if you could look/test the tarball or packages of the 
> release 0.13.0pre1.
> Your remarks, proposals, contributions are heartily welcome.
>
> Kind regards,
> Viktor.
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>

-- 

  Douglas E. Engert  
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444


___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

Hello,

Le 15/09/2012 16:52, Kalev Lember a écrit :
> On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
>> Hello,
>>
>> current github 'staging' is tagged as v0.13.0-pre1.
>>
>> If no objections, I will merge this branch into github 'master' -- it will 
>> be base version to test
>> and to prepare the coming release candidate.
> Very good idea. I think it makes a lot of sense to have just one
> 'master' branch for development; this is what people coming over from
> other projects tend to expect.


'Master' and 'staging' are actually synchronized and for the new pull requests 
I propose to create them relative to the 'master' branch.
Until the end of this release the pull requests to 'staging' are also accepted.

The tag name 'v0.13.0-pre1' has been changed (sorry) to '0.13.0pre1' -- still 
cannot understand which common set of characters
could be used for the release-version/tag-name to satisfy 'git', 'obs', 
'dpkg-build', ...

Commits to 'master' and new tags trigger the jenkins jobs of build, packaging 
and some rudimentary test of package and unit tests (for Suse).
https://opensc.fr/jenkins/view/Open 
SC-release/ 


The resulting packages are transfered to 'download' part of the 
opensc-project.org file server:
 - commits to
http://www.opensc-project.org/downloads/projects/opensc/nightly/
 - releases to
http://www.opensc-project.org/downloads/projects/opensc/releases/


For a while there are only source tarballs, MSIs for x32 and x64 and rpm i586 
for opensSuSE 12.1 .
Hope that rapidly the building of releases packages for some debian/ubuntu 
distributions will be connected.

It would be nice if you could look/test the tarball or packages of the release 
0.13.0pre1.
Your remarks, proposals, contributions are heartily welcome.

Kind regards,
Viktor.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Kalev Lember]

On 09/06/2012 08:06 PM, Viktor Tarasov wrote:
> Hello,
> 
> current github 'staging' is tagged as v0.13.0-pre1.
> 
> If no objections, I will merge this branch into github 'master' -- it will be 
> base version to test
> and to prepare the coming release candidate.

Very good idea. I think it makes a lot of sense to have just one
'master' branch for development; this is what people coming over from
other projects tend to expect.

-- 
Kalev
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Andreas Schwier]

Hi Victor,

I'm fine with that. We still need more time for testing write support in
the SmartCard-HSM driver. So we rather take our time and put that
functionality into a later release.

Andreas

Am 06.09.2012 20:06, schrieb Viktor Tarasov:
> Hello,
>
> current github 'staging' is tagged as v0.13.0-pre1.
>
> If no objections, I will merge this branch into github 'master' -- it will be 
> base version to test
> and to prepare the coming release candidate.
>
> For the future (after this release), I think (and it was already suggested 
> here)
> that we don't really need two branches in github.
> We could use the unique 'master' branch, tag it as needed by release process,
> and to manage all proposals as pull requests to 'master'.
>
> For a while there is no packages (tarbals, MSIs, ...) labeled by tag name,
> only the packages automatically built on 'staging' branch and labeled by git 
> version.
>
> I will create the release dedicated jenkins jobs and will put thus prepared 
> packages onto the 'usual' places.
>
>
> Kind regards,
> Viktor.
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel


-- 

-CardContact Software & System Consulting
   |.##> <##.|   Andreas Schwier
   |#   #|   Schülerweg 38
   |#   #|   32429 Minden, Germany
   |'##> <##'|   Phone +49 171 8334920
-http://www.cardcontact.de
 http://www.tscons.de
 http://www.openscdp.org

___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

OK with me. I can not do any testing till early next week.


On 9/6/2012 1:06 PM, Viktor Tarasov wrote:
> Hello,
>
> current github 'staging' is tagged as v0.13.0-pre1.
>
> If no objections, I will merge this branch into github 'master' -- it will be 
> base version to test
> and to prepare the coming release candidate.
>
> For the future (after this release), I think (and it was already suggested 
> here)
> that we don't really need two branches in github.
> We could use the unique 'master' branch, tag it as needed by release process,
> and to manage all proposals as pull requests to 'master'.
>
> For a while there is no packages (tarbals, MSIs, ...) labeled by tag name,
> only the packages automatically built on 'staging' branch and labeled by git 
> version.
>
> I will create the release dedicated jenkins jobs and will put thus prepared 
> packages onto the 'usual' places.
>
>
> Kind regards,
> Viktor.
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>

-- 

  Douglas E. Engert  
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444


___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

Hello,

current github 'staging' is tagged as v0.13.0-pre1.

If no objections, I will merge this branch into github 'master' -- it will be 
base version to test
and to prepare the coming release candidate.

For the future (after this release), I think (and it was already suggested here)
that we don't really need two branches in github.
We could use the unique 'master' branch, tag it as needed by release process,
and to manage all proposals as pull requests to 'master'.

For a while there is no packages (tarbals, MSIs, ...) labeled by tag name,
only the packages automatically built on 'staging' branch and labeled by git 
version.

I will create the release dedicated jenkins jobs and will put thus prepared 
packages onto the 'usual' places.


Kind regards,
Viktor.

___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

I have sent a pull request to github, wich includes 3 different commits
but all listed under the same pull request. (I would have suspected it
let be do 3 pull requests.)

https://github.com/dengert/OpenSC/commit/1542022a6aefb86de95c734bb3923f2b3b59490e
   Needed to get code to compile.


https://github.com/dengert/OpenSC/commit/d36b8fc45e8e77cd620976cb5c21c08baecd0480
  Updates some comments and removes the "PIN Always" from the PIV 9D key.


https://github.com/dengert/OpenSC/commit/8052e2f940810f3010542933619d18b98488e84a
  Implements a solution to the problem described in my message
"[opensc-devel] OpenSC, CK_ALWAYS_AUTHENTICATE and Thunderbird" from 8/6/2012


I would like to see these in 0.13.0 if possible as
there are users with these problems.


On 8/6/2012 9:34 AM, Douglas E. Engert wrote:
> I am going to send shortly, under a different subject, a problem dealing with 
> user_consent,
> CK_ALWAYS_AUTHENTICATE, OpenSC and Thunderbird. I would like to see it 
> addressed in
> the next release.
>
>
> On 8/5/2012 12:48 PM, Viktor Tarasov wrote:
>> Hello,
>>
>> Le 22/07/2012 17:44, Viktor Tarasov a écrit :
>>> I would like to start preparation of the new release based on the 'staging' 
>>> branch of GitHub OpenSC .
>>> Your suggestions proposals are heartily welcome.
>>>
>>> As far as I see all 'essential' proposals,
>>> that have be committed into the 'staging' branch of OpenSC git repository 
>>> hosted in opensc-project.org (git://www.opensc-project.org/OpenSC.git),
>>> are present in github OpenSC.
>>>
>>> Unfortunately there is no access to the code review service (gerrit) of 
>>> opensc-project.org and it's not currently possible to pick-up the 
>>> 'interesting' requests.
>>> So, if anybody interested to see these proposals in the next release,
>>> please, do pull request to 'staging' branch of GitHub OpenSC 
>>> (git://github.com/OpenSC/OpenSC.git) .
>>
>> If anyone has more or less significant proposals, especially the ones that 
>> touch the common framework,
>> please, create the pull requests for github OpenSC.git/staging until the 
>> next weekend .
>> Don't worry if you will not arrive until this term -- I hope to make 
>> automatic the essential part of release process and so,
>> to make releases more frequents.
>>
>> The next weekend I hope to start the advanced non-regression tests of the 
>> current 'staging' and to tag the candidate for release.
>>
>> Look also if something essential is missing in the current 'NEWS' of 
>> 'staging'.
>> Sorry, 'NEWS' do not reflects in details all the contributions that have 
>> been made during the last year -- they are too numerous.
>>
>> 'Codereview' service of opensc-project.org is still not accessible and so 
>> there is no possibility to pick-up
>> the 'useful' proposals that have been made there.
>>
>> Kind regards,
>> Viktor.
>> ___
>> opensc-devel mailing list
>> opensc-devel@lists.opensc-project.org
>> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>>
>>
>

-- 

  Douglas E. Engert  
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444


___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Frank Morgner]

With SM enabled, I encountered the following warnings, that could be fixed:

pkcs15-iasecc.c: In function 'iasecc_file_convert_acls':
pkcs15-iasecc.c:327:30: warning: initialization discards 'const' qualifier from 
pointer target type [enabled by default]
card-jcop.c: In function 'jcop_set_security_env':
card-jcop.c:645:35: warning: passing argument 1 of 'memcpy' discards 'const' 
qualifier from pointer target type [enabled by default]
In file included from card-jcop.c:23:0:
/usr/include/string.h:44:14: note: expected 'void * __restrict__' but argument 
is of type 'const struct sc_security_env_t *'
card-authentic.c: In function 'authentic_sm_get_wrapped_apdu':
card-authentic.c:2327:3: warning: passing argument 1 of 'memcpy' discards 
'const' qualifier from pointer target type [enabled by default]
In file included from card-authentic.c:29:0:
/usr/include/string.h:44:14: note: expected 'void * __restrict__' but argument 
is of type 'const u8 *'
card-iasecc.c: In function 'iasecc_keyset_change':
card-iasecc.c:2218:25: warning: assignment discards 'const' qualifier from 
pointer target type [enabled by default]
card-iasecc.c:2223:25: warning: assignment discards 'const' qualifier from 
pointer target type [enabled by default]

-- 
Frank Morgner

Virtual Smart Card Architecture http://vsmartcard.sourceforge.net
OpenPACEhttp://openpace.sourceforge.net
IFD Handler for libnfc Devices  http://sourceforge.net/projects/ifdnfc


pgp3laSrBzirK.pgp
Description: PGP signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

I am going to send shortly, under a different subject, a problem dealing with 
user_consent,
CK_ALWAYS_AUTHENTICATE, OpenSC and Thunderbird. I would like to see it 
addressed in
the next release.


On 8/5/2012 12:48 PM, Viktor Tarasov wrote:
> Hello,
>
> Le 22/07/2012 17:44, Viktor Tarasov a écrit :
>> I would like to start preparation of the new release based on the 'staging' 
>> branch of GitHub OpenSC .
>> Your suggestions proposals are heartily welcome.
>>
>> As far as I see all 'essential' proposals,
>> that have be committed into the 'staging' branch of OpenSC git repository 
>> hosted in opensc-project.org (git://www.opensc-project.org/OpenSC.git),
>> are present in github OpenSC.
>>
>> Unfortunately there is no access to the code review service (gerrit) of 
>> opensc-project.org and it's not currently possible to pick-up the 
>> 'interesting' requests.
>> So, if anybody interested to see these proposals in the next release,
>> please, do pull request to 'staging' branch of GitHub OpenSC 
>> (git://github.com/OpenSC/OpenSC.git) .
>
> If anyone has more or less significant proposals, especially the ones that 
> touch the common framework,
> please, create the pull requests for github OpenSC.git/staging until the next 
> weekend .
> Don't worry if you will not arrive until this term -- I hope to make 
> automatic the essential part of release process and so,
> to make releases more frequents.
>
> The next weekend I hope to start the advanced non-regression tests of the 
> current 'staging' and to tag the candidate for release.
>
> Look also if something essential is missing in the current 'NEWS' of 
> 'staging'.
> Sorry, 'NEWS' do not reflects in details all the contributions that have been 
> made during the last year -- they are too numerous.
>
> 'Codereview' service of opensc-project.org is still not accessible and so 
> there is no possibility to pick-up
> the 'useful' proposals that have been made there.
>
> Kind regards,
> Viktor.
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>

-- 

  Douglas E. Engert  
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444


___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Jean-Michel Pouré - GOOZE]

Le dimanche 05 août 2012 à 19:48 +0200, Viktor Tarasov a écrit :
> The next weekend I hope to start the advanced non-regression tests of
> the current 'staging' and to tag the candidate for release.

I will open access to the development server and regression test server
tonight. I was quite busy and failed to do any work these last days.
Sorry!

Kind regards,
-- 
  Jean-Michel Pouré - Gooze - http://www.gooze.eu


smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Ludovic Rousseau]

Hello,

2012/8/5 Viktor Tarasov :
> If anyone has more or less significant proposals, especially the ones that 
> touch the common framework,
> please, create the pull requests for github OpenSC.git/staging until the next 
> weekend .
> Don't worry if you will not arrive until this term -- I hope to make 
> automatic the essential part of release process and so,
> to make releases more frequents.

Someone just reported [1] a crash on Mountain Lion (OS X 10.8).
I don't think I will have time to work on it.

> The next weekend I hope to start the advanced non-regression tests of the 
> current 'staging' and to tag the candidate for release.
>
> Look also if something essential is missing in the current 'NEWS' of 
> 'staging'.
> Sorry, 'NEWS' do not reflects in details all the contributions that have been 
> made during the last year -- they are too numerous.

I fixed some typos in the NEWS file. Available as a pull-request on github.

> 'Codereview' service of opensc-project.org is still not accessible and so 
> there is no possibility to pick-up
> the 'useful' proposals that have been made there.

I asked Martin to restart it. The Codereview service is now up and running.

Bye

[1] 
http://ludovicrousseau.blogspot.com/2012/08/mac-os-x-mountain-lion-and-smart-card.html?showComment=1344198899128#c8343187550094818437

-- 
 Dr. Ludovic Rousseau
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

Hello,

Le 22/07/2012 17:44, Viktor Tarasov a écrit :
> I would like to start preparation of the new release based on the 'staging' 
> branch of GitHub OpenSC .
> Your suggestions proposals are heartily welcome.
>
> As far as I see all 'essential' proposals,
> that have be committed into the 'staging' branch of OpenSC git repository 
> hosted in opensc-project.org (git://www.opensc-project.org/OpenSC.git),
> are present in github OpenSC.
>
> Unfortunately there is no access to the code review service (gerrit) of 
> opensc-project.org and it's not currently possible to pick-up the 
> 'interesting' requests.
> So, if anybody interested to see these proposals in the next release,
> please, do pull request to 'staging' branch of GitHub OpenSC 
> (git://github.com/OpenSC/OpenSC.git) .

If anyone has more or less significant proposals, especially the ones that 
touch the common framework,
please, create the pull requests for github OpenSC.git/staging until the next 
weekend .
Don't worry if you will not arrive until this term -- I hope to make automatic 
the essential part of release process and so,
to make releases more frequents.

The next weekend I hope to start the advanced non-regression tests of the 
current 'staging' and to tag the candidate for release.

Look also if something essential is missing in the current 'NEWS' of 'staging'.
Sorry, 'NEWS' do not reflects in details all the contributions that have been 
made during the last year -- they are too numerous.

'Codereview' service of opensc-project.org is still not accessible and so there 
is no possibility to pick-up
the 'useful' proposals that have been made there.

Kind regards,
Viktor.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

OK, sent pull request to fix a regression where some code in piv-tool.c was 
inadvertently remove
in 2011.


On 7/22/2012 10:44 AM, Viktor Tarasov wrote:
> Hello,
>
>
> I would like to start preparation of the new release based on the 'staging' 
> branch of GitHub OpenSC .
> Your suggestions proposals are heartily welcome.
>
> As far as I see all 'essential' proposals,
> that have be committed into the 'staging' branch of OpenSC git repository 
> hosted in opensc-project.org (git://www.opensc-project.org/OpenSC.git),
> are present in github OpenSC.
>
> Unfortunately there is no access to the code review service (gerrit) of 
> opensc-project.org and it's not currently possible to pick-up the 
> 'interesting' requests.
> So, if anybody interested to see these proposals in the next release,
> please, do pull request to 'staging' branch of GitHub OpenSC 
> (git://github.com/OpenSC/OpenSC.git) .



>
> Kind regards,
> Viktor.
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
>

-- 

  Douglas E. Engert  
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444


___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Jean-Michel Pouré - GOOZE]

Le dimanche 22 juillet 2012 à 17:44 +0200, Viktor Tarasov a écrit :
> So, if anybody interested to see these proposals in the next release,
> please, do pull request to 'staging' branch of GitHub OpenSC
> (git://github.com/OpenSC/OpenSC.git) . 

Dear Viktor,

Thank you very much for handling this new release, these are great
news. 

As we now have most smartcards on the regression test server, I will try
to organize automatic testing. But I am quite busy and I will try to do
my best in this way.

On the ePass2003 driver, it seems that the number of left tries is not
displayed. And there may be several issues with other cards that we may
discover using automatic testing.

Kind regards,
-- 
  Jean-Michel Pouré - Gooze - http://www.gooze.eu


smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Peter Stuge]

Viktor Tarasov wrote:
> I would like to start preparation of the new release based on the
> 'staging' branch of GitHub OpenSC .
> Your suggestions proposals are heartily welcome.

I suggest, as always, to not release anything without good review.


//Peter
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

Hello,


I would like to start preparation of the new release based on the 'staging' 
branch of GitHub OpenSC .
Your suggestions proposals are heartily welcome.

As far as I see all 'essential' proposals,
that have be committed into the 'staging' branch of OpenSC git repository 
hosted in opensc-project.org (git://www.opensc-project.org/OpenSC.git),
are present in github OpenSC.

Unfortunately there is no access to the code review service (gerrit) of 
opensc-project.org and it's not currently possible to pick-up the 'interesting' 
requests.
So, if anybody interested to see these proposals in the next release,
please, do pull request to 'staging' branch of GitHub OpenSC 
(git://github.com/OpenSC/OpenSC.git) .

Kind regards,
Viktor.

___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Alon Bar-Lev]

On Sun, May 27, 2012 at 7:38 PM, Peter Stuge  wrote:
> Ludovic Rousseau wrote:
>> 2012/5/27 Jean-Michel Pouré - GOOZE :
>> > Sufficient privileges in GIThub should be granted to a group of people.
>> > Trust is enough to agree on commits. FOAS means "Free" and "Open".
>>
>> FOAS = ?
>
> I guess FOSS.
>
> The "open" does however not mean that the entire world must have
> write access, it's about read access.
>
> "Trust is enough to agree on commits." makes no sense whatsoever to me.
>
> The closest that makes sense to me would be:
>
> Trust comes from agreeing on commits.
>
> Of course everyone has different priorities. It makes me sad that
> quality isn't the top priority for everyone in the project.

Peter, quality is not absolute term.
It can be mathematic definition of the best algorithm, which can lead
to infinite theoretical discussion for each line of code.
It might be physical definition of what is "good enough", and even
then, the border is also not absolute, as what good enough for one is
not good enough to other.
And it can be the service provided to users and the responsive to user's issues.

I, personally, for (3), providing a great service and responsiveness
while perfecting the code as 2nd priority (exception are interfaces).
I think this approach was taken at opensc in the past.

I also like the (2) approach, while trusting the active core
developers to define what is "good enough", and if someone thinks
otherwise he is free to become core developer or show the code of his
alternatives to the point it is accepted by the core developers.

Agree on commits is not something that can become reality as without
someone who can actually DECIDE, there can be non-ending arguments for
each change. We have this exact issue at OpenVPN project, which also
reached a complete stop as it does not have core developers and clear
responsibility for subsystems.

I am sad as this project (as it seems) reached a complete stop.

Programming is human creative work, there can be N^^N ways to acquire
a goal, very hard to evaluate what is "correct" or "better" in most of
the cases, it depends on the people involved and the people who
actually review at specific point in time... Same change can be
accepted at week X and rejected at week Y as other people review.
Because of that trust in the "core developers" of a project is
essential, as it is the only constant factor in the process.

Not sure what this discussion was, but I wanted to comment your statement.

Regards,
Alon.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Peter Stuge]

Ludovic Rousseau wrote:
> 2012/5/27 Jean-Michel Pouré - GOOZE :
> > Sufficient privileges in GIThub should be granted to a group of people.
> > Trust is enough to agree on commits. FOAS means "Free" and "Open".
> 
> FOAS = ?

I guess FOSS.

The "open" does however not mean that the entire world must have
write access, it's about read access.

"Trust is enough to agree on commits." makes no sense whatsoever to me.

The closest that makes sense to me would be:

Trust comes from agreeing on commits.

Of course everyone has different priorities. It makes me sad that
quality isn't the top priority for everyone in the project.


//Peter
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Ludovic Rousseau]

2012/5/27 Jean-Michel Pouré - GOOZE :
> Sufficient privileges in GIThub should be granted to a group of people.
> Trust is enough to agree on commits. FOAS means "Free" and "Open".

FOAS = ?

According to http://acronyms.thefreedictionary.com/FOAS we have:

FOASFuture Offensive Air System
FOASFiber Optic Acoustic Sensors (Northrop Grumman)
FOASFirst Order Abstract Syntax (computing)
FOASFall of Autumn Skies (band; Australia)
FOASFriends of Albert Schweitzer (England, UK)
FOASFootsteps of a Stranger (song)
FOASFriends of the Animal Shelter of St. Bernard, Inc. (Chalmette, LA)

Is it one of them? :-)

Bye

-- 
 Dr. Ludovic Rousseau
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Jean-Michel Pouré - GOOZE]

Le samedi 26 mai 2012 à 23:13 +0200, Viktor Tarasov a écrit :
> Before, I propose to gather into the github staging all pending
> proposals.
> After use this branch as the base for the next release:
> test this branch as far as possible, firstly using the automated
> packaging and tests,
> then extended manual tests with number of cards.

I agree with that. Also:

Sufficient privileges in GIThub should be granted to a group of people.
Trust is enough to agree on commits. FOAS means "Free" and "Open".

Kind regards,
-- 
  Jean-Michel Pouré - Gooze - http://www.gooze.eu


smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

Le 25/05/2012 18:09, Douglas E. Engert a écrit :
>
> On 5/25/2012 6:04 AM, Martin Paljak wrote:
>> Hello,
>>
>> On Wed, May 2, 2012 at 5:31 PM, Douglas E. Engert  wrote:
>>> The SM branch has pulled in many other changes (including
>>> my C_Derive changes) that I would like to see in the next release.
>>> If the SM branch is not going to be the bases for the next release,
>>> then we need to look at what change in the SM branch can be pulled in
>>> to the release.
>>>
>>> Martin, I would like to hear your comments.
>> Obviously Viktor and others have had way more time in their hands to
>> work on OpenSC than me :)
>>
>> Also obvious is that the most active branch is supposed to be merged
>> as the basis for next release, which was more or less the idea of Git
>> in the first place.
>>
>> As the recovery option, the sync problem between Gerrit and github
>> needs to be cleared. Too much integration is probably not a good idea,
>> two-way syncing between github pull request and Gerrit has brought no
>> obvious benefits...
>>
>> The most straightforward approach would probably be forcing the github
>> tree into opensc-project.org and clearing Gerrit...

Before, I propose to gather into the github staging all pending proposals.
After use this branch as the base for the next release:
test this branch as far as possible, firstly using the automated packaging and 
tests,
then extended manual tests with number of cards.

For the future use the github OpenSC as the main repository for development and 
packaging.
Connected to CI service, GitHub gives similar possibilities to analyze and 
validate proposals
as Gerrit do. (I do not yet tried to connect github pull request to Jenkins, 
but I think it's possible.)

By the way, Martin,
will it be possible to add to the github OpenSC/OpenSC the web-hook with URL of 
my jenkins service?
I need it for the 'staging' of OpenSC/OpenSC,
where I would like to use trigger by commit and also to try the build of pull 
requests.


>> Martin
> Sounds reasonable, but how do we avoid these types of problems in the future?
> No two-way syncing, with Gerrit or GitHub as the master?


Kind regards,
Viktor.

___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

On 5/25/2012 6:04 AM, Martin Paljak wrote:
> Hello,
>
> On Wed, May 2, 2012 at 5:31 PM, Douglas E. Engert  wrote:
>> The SM branch has pulled in many other changes (including
>> my C_Derive changes) that I would like to see in the next release.
>> If the SM branch is not going to be the bases for the next release,
>> then we need to look at what change in the SM branch can be pulled in
>> to the release.
>>
>> Martin, I would like to hear your comments.
>
> Obviously Viktor and others have had way more time in their hands to
> work on OpenSC than me :)
>
> Also obvious is that the most active branch is supposed to be merged
> as the basis for next release, which was more or less the idea of Git
> in the first place.
>
> As the recovery option, the sync problem between Gerrit and github
> needs to be cleared. Too much integration is probably not a good idea,
> two-way syncing between github pull request and Gerrit has brought no
> obvious benefits...
>
> The most straightforward approach would probably be forcing the github
> tree into opensc-project.org and clearing Gerrit...
>
> Martin

Sounds reasonable, but how do we avoid these types of problems in the future?
No two-way syncing, with Gerrit or GitHub as the master?


>
>

-- 

  Douglas E. Engert  
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Martin Paljak]

Hello,

On Wed, May 2, 2012 at 5:31 PM, Douglas E. Engert  wrote:
> The SM branch has pulled in many other changes (including
> my C_Derive changes) that I would like to see in the next release.
> If the SM branch is not going to be the bases for the next release,
> then we need to look at what change in the SM branch can be pulled in
> to the release.
>
> Martin, I would like to hear your comments.

Obviously Viktor and others have had way more time in their hands to
work on OpenSC than me :)

Also obvious is that the most active branch is supposed to be merged
as the basis for next release, which was more or less the idea of Git
in the first place.

As the recovery option, the sync problem between Gerrit and github
needs to be cleared. Too much integration is probably not a good idea,
two-way syncing between github pull request and Gerrit has brought no
obvious benefits...

The most straightforward approach would probably be forcing the github
tree into opensc-project.org and clearing Gerrit...

Martin
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Jean-Michel Pouré - GOOZE]

> There hasn't been very much review.

Dear Peter. 

I hope that we will be switching from peer-review to
community-assisted-review, which means automatic testing tools.

As  Viktor wrote, we have to take into account that there is limited
Human Resources for OpenSC and that we need to go fast to reach a large
audience.

Kind regards,
-- 
  Jean-Michel Pouré - Gooze - http://www.gooze.eu


smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

On Thu, May 3, 2012 at 12:35 AM, Peter Stuge  wrote:

> Viktor Tarasov wrote:
> > I still propose to merge the SM branch into the github:OpenSC-staging
> > and prepare it as candidate for release . It should not be difficult,
> > recently both branches has been synchronized.
>
> The difficulty lies not in making something that builds, the
> difficulty lies in understanding every single changed line of code.
>
> There hasn't been very much review.
>

You've already told this months ago.
Something has been changed?
Have you something else to propose, taking into account the available human
resources ?

Reviewer, the one that can review something more than 'trailing
whitespaces', needs some motivation.
This motivation is stimulated by responsiveness of the project to his
aspirations.

There was unusual period of absence of dialogue in the OpenSC project,
so, I suggest the unusual means to restore the normal dialogue.



> //Peter
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Peter Stuge]

Viktor Tarasov wrote:
> I still propose to merge the SM branch into the github:OpenSC-staging
> and prepare it as candidate for release . It should not be difficult,
> recently both branches has been synchronized.

The difficulty lies not in making something that builds, the
difficulty lies in understanding every single changed line of code.

There hasn't been very much review.


//Peter
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Viktor Tarasov]

On Wed, May 2, 2012 at 4:31 PM, Douglas E. Engert  wrote:

> On 5/2/2012 8:22 AM, Jean-Michel Pouré - GOOZE wrote:
> > Le mardi 01 mai 2012 à 21:00 +0300, Kalev Lember a écrit :
> >>
> >> What I am looking for is an official release, something that Linux
> >> distributions could pick up. A snapshot of another development branch
> >> wouldn't really help me here, but I appreciate the suggestion.
> >
> > At some point, the SM branch will deprecate other branches:
> > * This is where most development is done.
> > * We have a complete approach of a quality circle, starting with
> > frequent updates and ending with package releases and automatic testing.
> >
> > OpenSC hackers are encouraged to switch to SM branch.
>
> That still does not answer the questions: What will be in the next
> "Official" release and when?
>
> Will SM be in it?
>
> The SM branch has pulled in many other changes (including
> my C_Derive changes) that I would like to see in the next release.
> If the SM branch is not going to be the bases for the next release,
> then we need to look at what change in the SM branch can be pulled in
> to the release.
>
> Martin, I would like to hear your comments.
>


Also do I.
I still propose to merge the SM branch into the github:OpenSC-staging and
prepare it as candidate for release . It should not be difficult, recently
both branches has been synchronized.
One more argument is that the alternative CI server should soon be ready
for the automatic packaging and later for the automatic testing. It could
be useful when preparing new release.


> Kind regards,
>


Kind wishes,
Viktor.
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Douglas E. Engert]

On 5/2/2012 8:22 AM, Jean-Michel Pouré - GOOZE wrote:
> Le mardi 01 mai 2012 à 21:00 +0300, Kalev Lember a écrit :
>>
>> What I am looking for is an official release, something that Linux
>> distributions could pick up. A snapshot of another development branch
>> wouldn't really help me here, but I appreciate the suggestion.
>
> At some point, the SM branch will deprecate other branches:
> * This is where most development is done.
> * We have a complete approach of a quality circle, starting with
> frequent updates and ending with package releases and automatic testing.
>
> OpenSC hackers are encouraged to switch to SM branch.

That still does not answer the questions: What will be in the next
"Official" release and when?

Will SM be in it?

The SM branch has pulled in many other changes (including
my C_Derive changes) that I would like to see in the next release.
If the SM branch is not going to be the bases for the next release,
then we need to look at what change in the SM branch can be pulled in
to the release.

Martin, I would like to hear your comments. 

>
> Kind regards,
>
>
>
> ___
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel

-- 

  Douglas E. Engert  
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Jean-Michel Pouré - GOOZE]

Le mardi 01 mai 2012 à 21:00 +0300, Kalev Lember a écrit :
> 
> What I am looking for is an official release, something that Linux
> distributions could pick up. A snapshot of another development branch
> wouldn't really help me here, but I appreciate the suggestion.

At some point, the SM branch will deprecate other branches:
* This is where most development is done. 
* We have a complete approach of a quality circle, starting with
frequent updates and ending with package releases and automatic testing.

OpenSC hackers are encouraged to switch to SM branch.

Kind regards,
-- 
  Jean-Michel Pouré - Gooze - http://www.gooze.eu


smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Kalev Lember]

On 04/30/2012 12:06 PM, Jean-Michel Pouré - GOOZE wrote:
> Most of the development is happening in the secure messaging branch and
> installers are released from the compilation farm.
[...]
> We will soon release a testing farm with smarcards and USB tokens
> attached. So you can safely go with the secure messaging branch.

Hi Jean-Michel,

Thanks for your reply.

What I am looking for is an official release, something that Linux
distributions could pick up. A snapshot of another development branch
wouldn't really help me here, but I appreciate the suggestion.

I'm sure there's a lot of nice work going into the secure messaging
branch, but that shouldn't stop the 0.12.3 release. There will always be
some great new stuff to merge, but it's also important to be able to get
regular releases out, based on the already merged code.

-- 
Thanks,
Kalev
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] new release?

[Jean-Michel Pouré - GOOZE]

Le dimanche 29 avril 2012 à 23:50 +0300, Kalev Lember a écrit :
> The staging branch has some nice changes, in particular I'm interested
> in Stef's mlock fixes. Would it be possible to have a new opensc
> tarball
> release off the staging branch, please?

Most of the development is happening in the secure messaging branch and
installers are released from the compilation farm.

You may download tarballs and installers from there:
http://www.opensc-project.org/downloads/nightly/sm/

We will soon release a testing farm with smarcards and USB tokens
attached. So you can safely go with the secure messaging branch.

Kind regards,
-- 
  Jean-Michel Pouré - Gooze - http://www.gooze.eu


smime.p7s
Description: S/MIME cryptographic signature
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel