I see security as "journey" with no absolute end-destination.
I'm sure that there will be screw-ups but it seems that iPhone and Android
have fewer OS-level security breaches than Windows in spite of phones being
"always connected".
The #1 security issue appears to be how to give apps the "right"
Le 27 mars 2012 10:50, "Magosányi, Árpád" a écrit :
> Hi!
>
> We have the following symptoms:
> - some modifications come as a set of patches. Gerrit lets you review a
> patch a time.
> - sometimes it is not even clear what are really the changes
> - sometimes approved patches fail to apply
>
> It
Hi!
We have the following symptoms:
- some modifications come as a set of patches. Gerrit lets you review a
patch a time.
- sometimes it is not even clear what are really the changes
- sometimes approved patches fail to apply
It would be nice if
- all patches in gerrit would be shown as relative
Le 27 mars 2012 10:14, Peter Stuge a écrit :
> Ludovic Rousseau wrote:
>> > Whenever I start pcscd manually:
>> > sudo pcscd --foreground --debug
>>
>> Use:
>> sudo /usr/sbin/pcscd --foreground --debug
>
> Is it re-executing? Suggest do like sshd and refuse to start without
> full path in that cas
Ludovic Rousseau wrote:
> > Whenever I start pcscd manually:
> > sudo pcscd --foreground --debug
>
> Use:
> sudo /usr/sbin/pcscd --foreground --debug
Is it re-executing? Suggest do like sshd and refuse to start without
full path in that case.
//Peter
Ludovic Rousseau wrote:
> > automatically send notifications for all new patches to the
> > opensc-devel mailing list,
>
> Peter, can you explain how to setup gerrit for that? I think only
> Martin can do that change as the gerrit admin.
It requires adding a patchset-created hook into the magic h
Le mardi 27 mars 2012 à 09:40 +0200, Ludovic Rousseau a écrit :
> Use:
> sudo /usr/sbin/pcscd --foreground --debug
>
> with the complete pcscd path. Or you get the error:
> pcscd: posix_spawn: pcscd: No such file or directory
Nice shot, you are right, this works now!
Many thanks.
--
Peter Stuge wrote:
> > So I would be in favor of letting main developers commit their
> > changes to ONE SINGLE git staging branch directly and let
> > developers/users fix the code.
>
> It's an interesting idea, but it places a significantly higher
> workload on the developers if there is more th
Many thanks for coming back on topic for OpenSC! :)
Jean-Michel Pouré - GOOZE wrote:
> In bazar development, we should agree to release unperfect code in
> one "unstable" branch and let the community fix it.
I don't oppose having stable and unstable development processes per
se. But usually it's
Le 27 mars 2012 09:19, Jean-Michel Pouré - GOOZE a écrit :
> Dear all,
>
> I am building MacOSX packages for Viktor's Jenkins. Building packages
> works. But after installing packages, OpenSC does not work.
>
> To reproduce the problem:
> * Mac OS X 10.6
> * OpenSC packages from opensc-project.org
Le mardi 27 mars 2012 à 09:14 +0200, Ludovic Rousseau a écrit :
>
> Peter, can you explain how to setup gerrit for that? I think only
> Martin can do that change as the gerrit admin.
This has to change.
We cannot have one admin on important software. On reason is that each
of us can have an ac
Dear all,
I am building MacOSX packages for Viktor's Jenkins. Building packages
works. But after installing packages, OpenSC does not work.
To reproduce the problem:
* Mac OS X 10.6
* OpenSC packages from opensc-project.org
I seems to be a problem with my MacOSX station, but I don't know which:
Le 27 mars 2012 07:01, Peter Stuge a écrit :
> Ludovic Rousseau wrote:
>> If you want to follow the OpenSC development is very important to
>> subscribe to gerrit notifications (I think).
>
> I agree with this as well. It would of course be possible for gerrit
> to automatically send notifications
"Magosányi, Árpád" 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 is quite we
Le mardi 27 mars 2012 à 03:19 +0200, Peter Stuge a écrit :
> There was always a way for the ccid package to work around the
> problem, I don't know why this wasn't done, but I guess that it would
> have required too much effort, and noone contributed such effort to
> the ccid project. I guess that
Hello,
Le 26 mars 2012 18:01, "Magosányi, Árpád" a écrit :
> 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,
Le 26 mars 2012 17:27, "Magosányi, Árpád" a écrit :
> 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,
17 matches
Mail list logo
