Dear Martin,
opensc-project.org SSL certificate expired (kind of suddenly, there
should have been a reminder but that did not arrive for some reason),
the checksums of the new one are:
MD5: 68786c3e0cfe44e31d6c789e767605d5
SHA1: d7af30e8dfd9b6433353999f24e5dbb74132a988
Nice to see you on
2012/3/22 Anders Rundgren anders.rundg...@telia.com
Somewhat related to the OpenSC organization discussions:
http://www.globalplatform.org/documents/Consumer_Centric_Model_White_PaperMar2012.pdf
I must confess I don't understand a thing of this, neither the business
model,
the consumer
Dear all,
Here is outlined a PINPAD fix (read second comment):
http://sourceforge.net/tracker/?func=detailatid=2247688aid=3489002group_id=553887
I would like to know your opinion about the proposed solution.
Kind regards,
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
Jean-Michel,
Le 23 mars 2012 08:58, Jean-Michel Pouré - GOOZE jmpo...@gooze.eu a écrit :
Dear Martin,
opensc-project.org SSL certificate expired (kind of suddenly, there
should have been a reminder but that did not arrive for some reason),
the checksums of the new one are:
MD5:
Dear Ludovic and all,
You have to understand that free software projects (in a large part)
are do-ocracy and not democracy. The people doing things decide how
they do it.
If you want to get a commit write access you shall first provide good
patches and work. It does not work in the reverse
What exactly are you trying to achieve?
Dear Emanuelle,
In the past, main OpenSC developers used to have write access to the
main trunk or at least to their development.
This is no longer the case. The new collaboration tools like GIT are
used to limit the power of the main developers.
Over
Hello,
On Mon, Mar 19, 2012 at 13:08, Jean-Michel Pouré - GOOZE
jmpo...@gooze.eu wrote:
OpenSC copyright belongs to the group of people who wrote OpenSC,
which is all of us. It does not belong to any company and an individual
granting rights to other individuals.
In legal terms, *copyright*
Le vendredi 23 mars 2012 à 13:19 +0200, Martin Paljak a écrit :
In legal terms, *copyright* on OpenSC belongs to the authors who have
contributed code, and/or marked it down in source code.
The fact that other, unknown persons (not established in source code
as copyright owners) have code in
Simple End User Joe here,
A suggestion for all concerned:
Please try to forget personal differences, and solve the problem ahead.
You are all very bright, you do awesome work, we all endlessly admire
you and thank you for all you have achieved so far. But.
For me it seems that there IS a problem
2012/3/23 Jean-Michel Pouré - GOOZE jmpo...@gooze.eu:
In the past, main OpenSC developers used to have write access to the
main trunk or at least to their development.
Even minor ones, such as myself.
This is no longer the case. The new collaboration tools like GIT are
used to limit the
Although OpenSC may be in a bit of s*** right now, that's a gentle breeze
compared to what is happening in the outside world.
There will be a war between a set of very divided European SC-vendors against
three gaint US corportations who are rolling out virtual smart cards like:
Dear Emanuele,
Please understand that nobody needs to be a committer in order to be a
reviewer. Anyone can be a reviewer, and Gerrit is meant to make that
easier.
Sure. If all developers had the ability to vote on Gerrit and apply
patches, this would solve many problems. Is that the case
Dear Martin,
Last time I checked, it worked flawlessly on fresh/clean 10.6 with the
given instructions.
You are right, this is better than my way compiling by hand. We
installed a dedicated Mac OS X station for Jenkins and I just switched
back from 10.7 to 10.6 (Snow Leopard). This should
Hello,
On Fri, Mar 23, 2012 at 15:17, Magosányi, Árpád m4g...@gmail.com wrote:
And you simultaneously don't have enough time to review patches.
Both are correct and understandable. And there is a way out of this
situation.
Require assurance of the stuff is working before even taking a look at
Hello,
On Sun, Mar 18, 2012 at 00:30, Viktor Tarasov viktor.tara...@gmail.com wrote:
- replication in gerrit do not working.
Should we manually push the perfect commits from gerrit's repo to staging?
(In the github's pull requests the commits are also perfects, almost perfect.)
Fetching github
Hi,
On 03/23/2012 05:48 PM, Martin Paljak wrote:
The trick is having a system that works and also helps to achieve the
target of having more people *actually* looking at code and some
testing (like automatic building) done before even considering ack-ing
something. But lagging on processing
Magosányi, Árpád wrote:
6 months worth of patches which cannot be reviewed
This is simply not true. *Anyone* can register on Gerrit and review,
and *all* review is a helpful contribution!
The problem is not that the code can not be reviewed, but that noone
is doing review. Anyone can do it.
On 03/23/2012 07:10 PM, Peter Stuge wrote:
Magosányi, Árpád wrote:
6 months worth of patches which cannot be reviewed
This is simply not true. *Anyone* can register on Gerrit and review,
and *all* review is a helpful contribution!
The problem is not that the code can not be reviewed, but
Hello,
On Tue, Feb 21, 2012 at 16:46, Douglas E. Engert deeng...@anl.gov wrote:
It does not define a load key or any finalize
commands which would be needed by a production card management system.
I don't know about PIV internals, but maybe the finalize step is
automatic or not needed at all
Hello Anders,
On Tue, Feb 21, 2012 at 19:40, Anders Rundgren
anders.rundg...@telia.com wrote:
I have played with the idea of creating a secure stack-machine for
performing arbitrary cryptographic operations on result-data but I couldn't
figure out how this would work without introducing
On Fri, Mar 23, 2012 at 10:44, Jean-Michel Pouré - GOOZE
jmpo...@gooze.eu wrote:
Here is outlined a PINPAD fix (read second comment):
http://sourceforge.net/tracker/?func=detailatid=2247688aid=3489002group_id=553887
I would like to know your opinion about the proposed solution.
The comment
On 3/23/2012 11:48 AM, Martin Paljak wrote:
Hello,
On Fri, Mar 23, 2012 at 15:17, Magosányi, Árpádm4g...@gmail.com wrote:
And you simultaneously don't have enough time to review patches.
Both are correct and understandable. And there is a way out of this
situation.
Require assurance of
On 3/23/2012 2:59 PM, Martin Paljak wrote:
Hello,
On Tue, Feb 21, 2012 at 16:46, Douglas E. Engertdeeng...@anl.gov wrote:
It does not define a load key or any finalize
commands which would be needed by a production card management system.
Martin, You really are catching up on your mail!
On Fri, Mar 23, 2012 at 22:16, Douglas E. Engert deeng...@anl.gov wrote:
ECDH/C_Derive - One needs a smart card that can do ECC key derivation.
I have some test cards and some demo cards from NIST that can do this,
The NIST people were using the mods for testing with thunderbird,
On 03/23/2012 09:16 PM, Douglas E. Engert 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.
I am more optimistic than that. If it is made clear that the patch
I have registered to gerrit, because saying stuff is one thing, doing it
is another. I guess I am supposed to verify and/or review. Which is
what, and how?
I have choosen Change I1e6f787d to experiment with, which is a nice
oneliner. Some guy have changed an email address in a comment to his own.
On 3/23/2012 3:29 PM, Martin Paljak wrote:
On Fri, Mar 23, 2012 at 22:16, Douglas E. Engertdeeng...@anl.gov wrote:
ECDH/C_Derive - One needs a smart card that can do ECC key derivation.
I have some test cards and some demo cards from NIST that can do this,
The NIST people
Martin,
Le 23 mars 2012 18:17, Martin Paljak mar...@martinpaljak.net a écrit :
Hello,
On Sun, Mar 18, 2012 at 00:30, Viktor Tarasov viktor.tara...@gmail.com
wrote:
- replication in gerrit do not working.
Should we manually push the perfect commits from gerrit's repo to staging?
(In the
Dear all,
SM - I don't have any cards that can use this, others may.
ePass2300 - GOOZE was willing to sending them out to developers, I
don't
know how many may have them, and if they do have they voted?
It worked for me and I voted +1. (I think I voted.)
We really welcome
Dear Douglas,
What this means is that you are not going to get many votes because
in some cases only the author can test the code. A +1 from the author
may be the most you will get!
If we look at GIThub, there is a limited numbers of OpenSC forks, which
means a relatively small workforce.
Hello,
Le 23 mars 2012 21:53, Magosányi, Árpád m4g...@gmail.com a écrit :
I have registered to gerrit, because saying stuff is one thing, doing it
is another. I guess I am supposed to verify and/or review. Which is
what, and how?
I have choosen Change I1e6f787d to experiment with, which is a
On 23/03/2012 19:10, Peter Stuge wrote:
The problem is not that the code can not be reviewed, but that noone
is doing review. Anyone can do it.
I'd do reviews, but the last time I tried to really understand OpenSC's
flow, all I got was an headache (a big one...) :(
So it's not a will issue,
On 03/23/2012 11:10 PM, NdK wrote:
I'd do reviews, but the last time I tried to really understand OpenSC's
flow, all I got was an headache (a big one...) :(
So it's not a will issue, it's more an understandig issue. At least for
me. And I'd really like to be able to help, but it seems only a
Looking at https://www.opensc-project.org/codereview/#/c/150/ , which is
a patch which is overwritten by a later patch in gerrit, I started to
wonder again about quality standards. And this:
http://lwn.net/Articles/328438/
And there should be others. This is what I have gathered so far:
-
34 matches
Mail list logo
