On 06/06/2010 11:17 PM, Aleksey Samsonov wrote:
Hello,
Aleksey Samsonov wrote:
martin, do you want to create new releases?
Need to test 0.11 branch with the openssl engine fix.
Could you wait a few days? I'm try to find more clean solution. We have
problem under the stipulation that load
On Mon, 2010-07-12 at 09:30 +0300, Kalev Lember wrote:
How about making a tarball 0.12 beta release from trunk too?
IMHO this would be the preferred solution. If 0.11.14 is released along
0.12, OpenSC will end-up like OpenSSL with noone using the latest
version. So let's trash 0.11.14 and go for
On May 26, 2010, at 23:21 , Andreas Jellinghaus wrote:
are there any plans for new version?
* what happend to opensc 0.11.*? I thought the problem with
gost / engine_pkcs11 is so big, it should be fixed in
the 0.11 line to help normal users, and so distributions
can backport that fix if
Hello,
Aleksey Samsonov wrote:
martin, do you want to create new releases?
Need to test 0.11 branch with the openssl engine fix.
Could you wait a few days? I'm try to find more clean solution. We have
problem under the stipulation that load gost engine before loading
engine_pkcs11 (which
Hello,
Martin Paljak wrote:
* what happend to opensc 0.11.*? I thought the problem with
gost / engine_pkcs11 is so big, it should be fixed in
the 0.11 line to help normal users, and so distributions
can backport that fix if they want.
Apparently Jean-Michel has some specific bugfixes in
On May 26, 2010, at 23:21 , Andreas Jellinghaus wrote:
are there any plans for new version?
* openct could use a new release once juergens imx
code works well and is commited. at least a pre-release
or rc, and later a full release.
Sure. I don't know/use OpenCT, so no idea about it.
* what
Hi Andreas,
Andreas Jellinghaus wrote:
are there any plans for new version?
* openct could use a new release once juergens imx
code works well and is commited. at least a pre-release
or rc, and later a full release.
* what happend to opensc 0.11.*? I thought the problem with
gost /
On 05/26/2010 11:21 PM, Andreas Jellinghaus wrote:
* what happend to opensc 0.11.*? I thought the problem with
gost / engine_pkcs11 is so big, it should be fixed in
the 0.11 line to help normal users, and so distributions
can backport that fix if they want.
* is it time for a release
Am Donnerstag 27 Mai 2010, um 11:01:53 schrieb Kalev Lember:
What API/ABI stability are you talking about?
right. since only the tools inside opensc source code use
libopensc, there is no need to worry about ABI/API any more.
so let me rephrase the question:
can we target a new stable release
On Thu, 2010-05-27 at 20:38 +0200, Andreas Jellinghaus wrote:
can we target a new stable release now, or are there current
plans for major changes, and should we wait for those before
aiming for new releases?
Really, it seems that a new stable version should be released before
anything.
--
On Tuesday 14 August 2007 09:13:06 Ludovic Rousseau wrote:
What version of libassuan are you using?
updated it to the latest ubuntu libassuan-dev file:
1.0.0-1build1
Thanks, RAndreas
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
On Tuesday 14 August 2007 19:25:22 Alon Bar-Lev wrote:
This is the reason why it is bad idea to include it...
Alon, I think the libassuan.m4 file is similar to your --disable-nsplugin
code: extra code that is not necessary, because you can easily work around.
but it makes live easier for some
On 14/08/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
I added the _CFLAGS variable whever the ltdl.h file is searched so it will be
found and added back the libassuan.m4 file, as I think without we will annoy
quite a number of users (it hit already two active developer - jpz and me on
On 8/14/07, Ludovic Rousseau [EMAIL PROTECTED] wrote:
On 14/08/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
I added the _CFLAGS variable whever the ltdl.h file is searched so it will
be
found and added back the libassuan.m4 file, as I think without we will annoy
quite a number of
On 8/14/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
thanks Alon and Ludovic!
I added the _CFLAGS variable whever the ltdl.h file is searched so it will be
found and added back the libassuan.m4 file, as I think without we will annoy
quite a number of users (it hit already two active
On 8/9/07, Ludovic Rousseau [EMAIL PROTECTED] wrote:
Any other comment?
No... :)
There are just too many weird things in configure...
I am afraid to touch...
Best Regards,
Alon Bar-Lev.
___
opensc-devel mailing list
On Wednesday 08 August 2007 17:44:00 Alon Bar-Lev wrote:
Hmmm
nl use ltdl
-#AC_LIB_LINKFLAGS(ltdl)
+AC_CHECK_LIB([ltdl],lt_dlopen)
Solves this issue.
Anyone know why the AC_LIB_LINKFLAGS was used and not AC_CHECK_LIB?
would be nice to get this working, but we need to set LTLIBLTDL or
On Thursday 09 August 2007 08:46:53 Alon Bar-Lev wrote:
After another quick look...
Some thoughts...
1. Rename configure.in into configure.ac
fine with me. I think Antti was against it or something. but I don't remember
the details, and whatever old plattform had problems with the rename is
On Thursday 09 August 2007 09:27:02 Ludovic Rousseau wrote:
3. Why configure has AM_MAINTAINER_MODE? It is best to go without.
I do not agree. AM_MAINTAINER_MODE will prevent make to try to rebuild
Makefile.in if it detects Makefile.am is more recent.
end-users should not have to have
On Friday 10 August 2007, Andreas Jellinghaus wrote:
would be nice to get this working, but we need to set LTLIBLTDL or similar
(or adjust the autoconf makefiles - I prefer not setting LIBS so we can
add -lltdl only where needed and not on a global scale).
Attached.
also we need to
check
On Friday 10 August 2007, Andreas Jellinghaus wrote:
2. Why do you store the following: aclocal/pkg.m4, aclocal/libassuan.m4?
The should be provided and maintained by the packages installed at
your system...
I don't want to force people into installing libassuan-dev. they would if we
On 09/08/07, Alon Bar-Lev [EMAIL PROTECTED] wrote:
On 8/9/07, Ludovic Rousseau [EMAIL PROTECTED] wrote:
This patch works for me. Any objection to commit it?
After another quick look...
Some thoughts...
1. Rename configure.in into configure.ac
No objection
2. Why do you store the
On 8/9/07, Ludovic Rousseau [EMAIL PROTECTED] wrote:
2. Why do you store the following: aclocal/pkg.m4, aclocal/libassuan.m4?
The should be provided and maintained by the packages installed at
your system...
They should be removed from svn.
Exact. I also suggested (and committed) that
On 09/08/07, Alon Bar-Lev [EMAIL PROTECTED] wrote:
On 8/9/07, Ludovic Rousseau [EMAIL PROTECTED] wrote:
3. Why configure has AM_MAINTAINER_MODE? It is best to go without.
I do not agree. AM_MAINTAINER_MODE will prevent make to try to rebuild
Makefile.in if it detects Makefile.am is more
On Sunday 05 August 2007 13:33:45 Ludovic Rousseau wrote:
The real problem I have is with configure.in. It does _not_ work for me.
which version of automake? can you try the older automake packages?
(debian has several packages IIRC and one of them works, the other doesn't
and I don't know what
On 08/08/2007, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
On Sunday 05 August 2007 13:33:45 Ludovic Rousseau wrote:
The real problem I have is with configure.in. It does _not_ work for me.
which version of automake? can you try the older automake packages?
(debian has several packages IIRC
On 8/8/07, Ludovic Rousseau [EMAIL PROTECTED] wrote:
I have the problem with automake 1.10
$ ./autogen.sh
+ aclocal -I aclocal
+ libtoolize --copy --force --automake
+ autoheader --force
+ autoconf --force
+ automake-1.10 --add-missing --copy --force --foreign
configure.in:198: required
Hello,
On 28/07/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
On Monday 23 July 2007 14:03:42 Jean-Pierre Szikora wrote:
I can not run anymore ./bootstrap for any version of opensc-trunk 3204.
I'm working with a Fedora Core 6. Installed autoconf is 2.59 and m4 is
1.4.8. Are the changes
Andreas Jellinghaus a écrit :
On Monday 23 July 2007 14:03:42 Jean-Pierre Szikora wrote:
I can not run anymore ./bootstrap for any version of opensc-trunk 3204.
I'm working with a Fedora Core 6. Installed autoconf is 2.59 and m4 is
1.4.8. Are the changes introduced in svn 3202-3203-3204
Andreas Jellinghaus a écrit :
but we also have quite some turnover rate at opensc, everyone of the
people that started opensc is no longer interested in it. to keep it
maintainable we also have to keep the code small and readable.
thus I don't want to blow up the configure code to add every
On Friday 20 July 2007 22:17:00 Klaus Heinz wrote:
This is the same issue I have with openct and the automatic detection
of pcsc-lite. If it's possible to use openct without pcsc-lite and this
is a supported configuration I prefer to have a switch to explicitly
enable/disable this option.
On 7/21/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
On Friday 20 July 2007 22:17:00 Klaus Heinz wrote:
This is the same issue I have with openct and the automatic detection
of pcsc-lite. If it's possible to use openct without pcsc-lite and this
is a supported configuration I prefer to
Hello Andreas,
On 7/17/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
OpenSC - new version 0.11.3
In next version, can you please add --enable-plugin so that the plugin
will be built/installed only if requested?
I don't see many people using it, and the libassuan, pinentry
dependency can be
On 7/20/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
if you don't have libassuan installed, then opensc should compile
fine (and not create the plugin). does that work for you?
Yes it does.
But if I have gnupg install, I already have libassuan, it does not
suggest I want to use it with
On Friday 20 July 2007 16:15:29 Alon Bar-Lev wrote:
Yes it does.
ok, good.
what happends if you run LIBASSUAN_CONFIG=/bin/false ./configure
?
I get an ugly warning from configure output, but it seems to work fine.
Thus I can disable libassuan without any need for special options.
does it work
On 7/20/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
what happends if you run LIBASSUAN_CONFIG=/bin/false ./configure
?
Oh...
For now, I've used --with-libassuan-prefix=tmp
document this hack and good? very few people have the problem you mention
so I think it is good enough?
No...
On Friday 20 July 2007 20:41:52 Alon Bar-Lev wrote:
No...
Please explicitly add --enable-nsplugin or something.
So that if you add dependency no additional hacks will be nessesery.
ok. thanks, commited.
sorry, I have little clue about the plugin, I even think I never used it
myself nor do
On 7/20/07, Andreas Jellinghaus [EMAIL PROTECTED] wrote:
On Friday 20 July 2007 20:41:52 Alon Bar-Lev wrote:
No...
Please explicitly add --enable-nsplugin or something.
So that if you add dependency no additional hacks will be nessesery.
ok. thanks, commited.
There is another issue...
At
Andreas Jellinghaus wrote:
document this hack and good? very few people have the problem you mention
so I think it is good enough?
This is the same issue I have with openct and the automatic detection
of pcsc-lite. If it's possible to use openct without pcsc-lite and this
is a supported
Hello,
pcsc-lite [1] and my CCID driver [2] now support extended APDU out of
the box. You can send and receive up to 64KB of data if your card (and
reader) supports it.
The extended APDUs are supported only for T=1 cards and if the reader
is in TPDU mode or extended APDU mode (not in character
40 matches
Mail list logo