On Mar 10, 2010, at 01:40 , Peter Stuge wrote:
> Andreas Jellinghaus wrote:
>> I would like the usual email verification thing to keep out spammer
>> and have some working email address to contact. trac doesn't do
>> that,
>
> It can with a plugin. And OpenID works well too. It's pretty neat.
>
>
On Mar 5, 2010, at 11:04 , Viktor TARASOV wrote:
> Hi Martin,
>
> Martin Paljak wrote:
>> At the same time, I was not able to delete cryptoflex with current trunk, it
>> seems that it tries to cache as a PIN the transport keys and crashes. Will
>> investigate
>
> Have you still problems with cr
On Mar 9, 2010, at 23:37 , Andreas Jellinghaus wrote:
> Am Dienstag 09 März 2010 14:58:41 schrieb Martin Paljak:
>> I'm not talking about a revolution here but simple short term evolution of
>> the current situation.
>
> well, if we change things, we can discuss svn or git or ... too,
> if people
On Mar 9, 2010, at 23:41 , Andreas Jellinghaus wrote:
> Am Dienstag 09 März 2010 22:28:29 schrieb Ludovic Rousseau:
>> Exactly. Maybe we should "hide" some projects to not confuse users.
>> OpenCT should not be installed in many cases.
>
> I agree for users with CCID drivers. But if you have an al
On Mar 9, 2010, at 23:28 , Ludovic Rousseau wrote:
> 2010/3/9 Martin Paljak :
>> Hello.
>
> Hi Martin,
>
>> Here are some plans that should make opensc-project.org more attractive to
>> both users and developers and also ease the administration burden. Lets
>> collect feedback for a week: pleas
I want to voice my support for git. I use it for all my projects and love it.
Has anyone looked into project hosting on Github? I think it's free
for open-source projects, well-supported, and a large and growing user
community.
I'm new to the project so I don't know how much this project really
ma
On Tue, Mar 9, 2010 at 1:16 AM, Martin Paljak wrote:
> On Mar 9, 2010, at 03:34 , Greg Mefford wrote:
>> Thanks for your thoughts. I have since spent some time debugging with
>> Windows as suggested and made some headway.
>> I believe I ran into some of the same non-standard problems you
>> mentio
Andreas Jellinghaus wrote:
> I would like the usual email verification thing to keep out spammer
> and have some working email address to contact. trac doesn't do
> that,
It can with a plugin. And OpenID works well too. It's pretty neat.
> so what do we want exactly?
I think the idea is to cons
François Pérou wrote:
> * Use DNSBL on your email server.
Personally I really dislike blacklists because they are quite
arbitrary. I've seen too many false positives, causing problems
for users.
//Peter
___
opensc-devel mailing list
opensc-devel@lists.
Am Dienstag 09 März 2010 22:28:29 schrieb Ludovic Rousseau:
> Exactly. Maybe we should "hide" some projects to not confuse users.
> OpenCT should not be installed in many cases.
I agree for users with CCID drivers. But if you have an aladdin etoken
or rainbow ikey 3000, you can use them with opens
Am Dienstag 09 März 2010 14:58:41 schrieb Martin Paljak:
> One option, as said, was "direct people to opensc-devel from some time
> onwards". OpenSC et al don't have such a huge userbase and a solid
> development/user separation that the artificial separation between two
> lists would do any goo
2010/3/9 Martin Paljak :
> Hello.
Hi Martin,
> Here are some plans that should make opensc-project.org more attractive to
> both users and developers and also ease the administration burden. Lets
> collect feedback for a week: please let me know which you feel would be
> useful or what would a
Am Dienstag 09 März 2010 20:44:23 schrieb Andreas Jellinghaus:
> Am Dienstag 09 März 2010 17:07:10 schrieb Viktor TARASOV:
> > I forgot to commit.
> >
> > Should I make default as 'true', as it was before ? I've had some doubts
> > on this.
>
> I have no clue on this. Did the current behaviour cau
Am Dienstag 09 März 2010 17:07:10 schrieb Viktor TARASOV:
> I forgot to commit.
>
> Should I make default as 'true', as it was before ? I've had some doubts
> on this.
I have no clue on this. Did the current behaviour cause problems?
if not, we should keep it. But if it caused problems, and they
On Mar 9, 2010, at 18:07 , Viktor TARASOV wrote:
> I forgot to commit.
>
> Should I make default as 'true', as it was before ? I've had some doubts
> on this.
I don't see any requirements for this to be true in the PKCS#11 spec. I'd say
no, don't give zero by default.
--
Martin Paljak
http:/
Andreas Jellinghaus wrote:
>> pkcs11: configuration option to report as zero the CKA_ID of CA
>> certificates
>>
>> In fact, the middleware of the manufacturer of the gemalto (axalto,
>> gemplus) cards reports the CKA_ID of CA certificates as '0'.
>>
>> But it's not true for the others middleware
> pkcs11: configuration option to report as zero the CKA_ID of CA
> certificates
>
> In fact, the middleware of the manufacturer of the gemalto (axalto,
> gemplus) cards reports the CKA_ID of CA certificates as '0'.
>
> But it's not true for the others middlewares (Oberthur), NSS (afais) and
>
Hello,
On Mar 9, 2010, at 15:22 , Andreas Jellinghaus wrote:
> here is my position on each issue:
> * mailing lists: I don't see a big benefit from having one list
> instead of two. Thus I would like to keep thinks as they are,
> as it will confuse users and require lots of reconfiguration
> if
Martin Paljak wrote:
> On Mar 9, 2010, at 14:44 , Viktor TARASOV wrote:
>
>> Hi,
>>
>> it seems that the internal API 'framework' of the pkcs11 module can be
>> simplified and be made more flexible
>> for the pkcs11 framework level.
>>
>> My initial motivation is to give the access to the 'sc_
Hi Martin,
in general I agree, opensc-project.org could use an overhaul.
here is my position on each issue:
* mailing lists: I don't see a big benefit from having one list
instead of two. Thus I would like to keep thinks as they are,
as it will confuse users and require lots of reconfiguratio
On Mar 9, 2010, at 14:44 , Viktor TARASOV wrote:
>
> Hi,
>
> it seems that the internal API 'framework' of the pkcs11 module can be
> simplified and be made more flexible
> for the pkcs11 framework level.
>
> My initial motivation is to give the access to the 'sc_pkcs11_slot' inside
> the fra
>so we could revert this check, and instead add a
>/* windows.h required before winreg.h*/
>#include
>#include
>inside the #ifdef _WIN32 ?
>looks cleaner to me...
Ok for me, I will do the test and make the change if you are ok?
François.
smime.p7s
Description: S/MIME cryptographic signatu
Am Dienstag 09 März 2010 13:57:23 schrieb François Leblanc:
> >so we could revert this check, and instead add a
> >/* windows.h required before winreg.h*/
> >#include
> >#include
> >
> >inside the #ifdef _WIN32 ?
> >looks cleaner to me...
>
> Ok for me, I will do the test and make the change if
Am Dienstag 09 März 2010 10:11:25 schrieb François Pérou:
> Le mardi 09 mars 2010 à 11:01 +0200, Martin Paljak a écrit :
> > Ideas, feedback?
>
> * Add a TXT spf anti-spam key on opensc-project.org
> to avoid people spamming using OpenSC discussions
not a big problem, as our lists are subscribe o
Am Dienstag 09 März 2010 09:21:30 schrieb François Leblanc:
> >hmm, why move internal.h? what is in internal.h that changes the winreg.h
> >include?
>
> Winreg.h depends of definition in windows.h witch is included in
> internal.h...
so we could revert this check, and instead add a
/* windows.h r
Hi,
it seems that the internal API 'framework' of the pkcs11 module can be
simplified and be made more flexible
for the pkcs11 framework level.
My initial motivation is to give the access to the 'sc_pkcs11_slot'
inside the framework operation 'login'.
And so I would like to change its proto
On Mar 9, 2010, at 11:35 , François Pérou wrote:
> Sorry, I though you we discussing about spam.
I don't think there has been a huge problem with e-mail spam getting to the
list or too many bounces because of fake sender addresses.
But there's always room for improvement!
--
Martin Paljak
http
Le mardi 09 mars 2010 à 11:18 +0200, Martin Paljak a écrit :
> This is a bit out of scope of the original goal (which is structural
> changes to make development and usage of OpenSC simpler and easier)
Sorry, I though you we discussing about spam.
Kind regards,
François Pérou
http://www.gooze.eu
On Mar 9, 2010, at 11:11 , François Pérou wrote:
> Le mardi 09 mars 2010 à 11:01 +0200, Martin Paljak a écrit :
>> Ideas, feedback?
>
> * Add a TXT spf anti-spam key on opensc-project.org
> to avoid people spamming using OpenSC discussions
>
> dig -t TXT opensc-project.org
> returns no value.
>
Thanks!
Please update link on the main page from 008 to 009.
Regards.
Cyril.
-Original Message-
From: Alon Bar-Lev [mailto:alon.bar...@gmail.com]
Sent: Friday, March 05, 2010 12:45 AM
To: Aktiv Co. Kirill Mescheryakov
Cc: opensc-devel@lists.opensc-project.org
Subject: Re: [opensc-devel]
Le mardi 09 mars 2010 à 11:01 +0200, Martin Paljak a écrit :
> Ideas, feedback?
* Add a TXT spf anti-spam key on opensc-project.org
to avoid people spamming using OpenSC discussions
dig -t TXT opensc-project.org
returns no value.
This will avoid people forging false emails.
This may be really ur
Hello.
As some of you noticed, opensc-commits got spammed yesterday from openct trac
(result: lots of e-mails to opensc-commits). This reminded me that there are
some maintenance issues that could be improved.
Here are some plans that should make opensc-project.org more attractive to both
user
>hmm, why move internal.h? what is in internal.h that changes the winreg.h
>include?
Winreg.h depends of definition in windows.h witch is included in
internal.h...
>usually it is not internal.h that has some special define, but config.h,
>and we have that as first include everywhere. so if th
hmm, why move internal.h? what is in internal.h that changes the winreg.h
include?
usually it is not internal.h that has some special define, but config.h,
and we have that as first include everywhere. so if there is something
special in internal.h that I missed, I would like to know :)
also it
34 matches
Mail list logo
