Re: [opensc-devel] some build questions about OpenSC/pam_pkcs11 module

2008-03-31 Thread Huie-Ying Lee
Huie-Ying Lee wrote: > Peter Stuge wrote: >> On Wed, Mar 26, 2008 at 06:27:02PM -0700, Huie-Ying Lee wrote: >>> I found that Solaris doesn't support "automake", "aclocal" and >>> "libtoolize" commands currently >> >> I suggest that you install automake, autoconf and libtool in order to >> work more

[opensc-devel] OpenSC truck and uses of separate source and build directories

2008-03-31 Thread Douglas E. Engert
I normally build with a common source directory and separate build directories. That is not working with the current SVN. Many of the Makefile.am files are pointing at the source directories, when they should point at the build directories for the src/opensc/include. They should also point at the

Re: [opensc-devel] Externally generated keys

2008-03-31 Thread Douglas E. Engert
Timothy J Miller wrote: > On Mar 31, 2008, at 9:49 AM, Douglas E. Engert wrote: > >> PIV is really an application on a card, and there are currently 4 >> NIST approved cards. 800-73 defines the application that needs to be >> stanadardized for end user use. > > I've heard that there's at least

Re: [opensc-devel] Externally generated keys

2008-03-31 Thread Timothy J Miller
On Mar 31, 2008, at 9:42 AM, Andreas Jellinghaus wrote: I thought: both. thanks for letting me know there is a way to convert public key files at least. secsh is the ssh 1 format? openssh has a different format these days, I guess that will be version 2? To be honest, I have no idea. I t

Re: [opensc-devel] Externally generated keys

2008-03-31 Thread Timothy J Miller
On Mar 31, 2008, at 9:49 AM, Douglas E. Engert wrote: PIV is really an application on a card, and there are currently 4 NIST approved cards. 800-73 defines the application that needs to be stanadardized for end user use. I've heard that there's at least one card provider that's going to impl

Re: [opensc-devel] Externally generated keys

2008-03-31 Thread Douglas E. Engert
Timothy J Miller wrote: > I should point out that this is bad practice for keys used for data > encryption, as loss or damage of the card can result in loss of the > protected data. US DoD, for example, generates the signature keys on > card, but encryption keys off-card and securely inje

Re: [opensc-devel] Externally generated keys

2008-03-31 Thread Andreas Jellinghaus
Am Montag, 31. März 2008 15:46:28 schrieb Timothy J Miller: > Public or private? The req command will happily read secsh format, > e.g.: > > openssl req -key ~/.ssh/id_rsa -new | openssl req -pubkey > > This will convert a secsh formatted pubkey into PEM (you can just give > the default responses

Re: [opensc-devel] Externally generated keys

2008-03-31 Thread Timothy J Miller
On Mar 29, 2008, at 4:56 AM, Andreas Jellinghaus wrote: > RSA is not a format. openssh has a format (actually two different > ones, check > your .ssh/authorized_keys file for public keys for example), and PEM > is a > format (from the x.509/openssl world). there is no tool to convert > opens

Re: [opensc-devel] some build questions about OpenSC/pam_pkcs11 module

2008-03-31 Thread Ludovic Rousseau
On Wed, Mar 26, 2008 at 3:13 AM, Huie-Ying Lee <[EMAIL PROTECTED]> wrote: > We are porting the version 0.6.0 of the pam_pkcs11 source officially, > however, I would like to take a look at the latest revision of source. How > can I see the revision 319 and 320 ? Use subversion $ svn checkout h