On 03/27/2012 03:19 AM, Peter Stuge wrote:
>
> Graeme did some rework of the patch, but generally did not seem to
> agree with the review. The new solution included the addition of new
> API calls, however without any documentation. As anyone who has
> looked at the code and doxygen output, libusb
Ludovic Rousseau wrote:
> I think you are doing the good thing. Thanks.
I agree!
> I encourage every user of the opensc-devel list to:
> - create a gerrit account
> - subscribe to the Email notifications. Go in Settings -> Watched
> Projects and check the 3 notifications boxes for the OpenSC pro
Jean-Michel Pouré - GOOZE wrote:
> Just remember there was a peer discussing about a 60 second timeout bug
> in libusb/pcscd. The first peer says "the bug is in libusb". The second
> peer says "the bug is in libccid". And the bug never gets fixed. And ALL
> tokens may suffer from this 60 seconds ti
On Saturday, March 24 at 07:07AM, Anders Rundgren wrote:
>
> http://www.globalplatform.org/specifications/review/GPD_SE_Access_Control_v0_10_0.pdf
>
> By adding ACL information to keys during enrollment you can limit key
> "misuse" by bad apps.
>
> Although GP specifies a generic scheme not limi
Dear Peter,
> http://en.wikipedia.org/wiki/Peer_review which I guess you may
> already be familiar with.
Yes, I have heard about peer review.
Just remember there was a peer discussing about a 60 second timeout bug
in libusb/pcscd. The first peer says "the bug is in libusb". The second
peer says
I have a little concern about the review procedure.
If I go to the point in the code review comment, it will be short and
not too encouraging.
However the guys submitting the patches do the Right Thing, they are
important ones, and some encouragement would be in place.
Should I also include some "t
Would https://www.opensc-project.org/codereview/#/c/263/ also fall to
the "Commits that obviously should be bundled with some other change"
category?
Half of the changes needed is at
https://www.opensc-project.org/codereview/#/c/262/1, and the two or
three lines being the main point has been change
Here it is, so no need to reply:
cd /tmp/
wget
http://www.opensc-project.org/downloads/nightly/viktor/macosx/OpenSC-0.12.3-pre1-10.6.dmg
sudo hdiutil mount /tmp/OpenSC-0.12.3-pre1-10.6.dmg
sudo installer -pkg "/Volumes/OpenSC 0.12.3-pre1 for Mac OS X 10.6
(2012.03.26)/OpenSC-0.12.3-pre1-10.6.pkg"
On Monday, March 26 at 09:17AM, helpcrypto helpcrypto wrote:
>
> > Another issues with this project is many of the modifications can only be
> > tested
> > by a subset of developers (maybe only one) who have the cards that can use
> > the modification.
>
> Maybe its an stupid idea (or already do
Dear Friends,
OpenSC-SM packages for MacOSX are now available from Viktor's branch:
http://www.opensc-project.org/downloads/nightly/viktor/macosx/
Is there a way to install MacOSX packages automatically using command
lines. This would allow to run simple testing.
We've attached a Feitian R-301
On 2012-03-26 09:17, helpcrypto helpcrypto wrote:
>> Another issues with this project is many of the modifications can only be
>> tested
>> by a subset of developers (maybe only one) who have the cards that can use
>> the modification.
>
> Maybe its an stupid idea (or already done), but can't we
> Another issues with this project is many of the modifications can only be
> tested
> by a subset of developers (maybe only one) who have the cards that can use
> the modification.
Maybe its an stupid idea (or already done), but can't we virtualize
(and use it in Jenkins) smartcards?
___
12 matches
Mail list logo
