smartsign-devel Mailing List for Smart Sign
Status: Pre-Alpha
Brought to you by:
kefren
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(9) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2003 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Tommaso C. <cuc...@ss...> - 2003-08-14 15:12:35
|
Hi all, the Smart Sign projects now hosts a new package, namely QSign, a Qt-based application for managing smart-card based digital signatures. The first package release is available for free download from the Smart Sign web site: http://smartsign.sourceforge.net (still missing some info in the web pages, so go straight to the Download->Download SF subsection). The program interacts with an external device such as a smart-card by the use of the PKCS#11 interface. Signatures are formatted in PEM-encoded PKCS#7 format. More details follow. Please, submit any comments, suggestions, bugs and any other kind of feedback to the Smart Sign mailing lists: mailto:sma...@li... mailto:sma...@li... Bye, Tommaso. ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <cuc...@ss...> - 2003-08-07 13:03:06
|
Rama Kristipati wrote: > hello, > > Nice to meet you. I want to work on JC-Emulator. Because I have been > thinking about similar application. > Similar to JC-Emulator I wrote a virtual pcsc driver which reads an xml > file for the configuration and > responds to the APDUs. But if there is some thing else challenging I > would love to work on it. I guess the first thing you should do is looking at JC-Emulator as it is right now. I already know a couple of tasks that need to be done. This is a short list: - change behavior of the virtual reader (possibly move it from Java into the C code) - maybe here your driver can help . the problem is that the emulator must already be up when you start PCSC-Lite, so that pcscd can detect a new serial reader. otherwise, initialization fails, and pcscd discards it forever. - finish serialization. It seems to have troubles, yet. Of course the idea is to have multiple image-files, corresponding to multiple virtual smart-cards that can be inserted/removed from the virtual reader. This has been done with Java serialization, but needs to be finished. - test/debug transactionality of operations JC transactionality is emulated with the same mechanism. The idea is to serialize at every command APDU that terminates succesfully, and to reload the previous image-file if a rollback is needed. - emulate memory limitations, as it happens onto a real JC device. The Applet can even allocate 1GB so far, if the host-machine VM allows it. I have no idea weather JVM has a way to limit the amount of memory that can be allocated to an Applet, or not. I'm quite sure you'll find smth. else by trying the emulator. Bye, T. -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <cuc...@ss...> - 2003-08-06 17:51:59
|
Tommaso Cucinotta wrote: > More details follow below. Sorry, I forgot details. Here they are. ====================================================================== JC-Emulator - Emulator for JavaCard 2.1.x smart cards. ====================================================================== Main developers: Paolo Grimaccia, Matteo Ferrari Coordinator: Tommaso Cucinotta <cuc...@ss...> Organization: Scuola Superiore Sant'Anna, Pisa - Italy ---------------------------------------------------------------------- DESCRIPTION ---------------------------------------------------------------------- JC-Emulator is an emulation environment for running, testing and debugging JavaCard Applets and JavaCard based solutions. Applets can be run within the emulator, without any need for real smart-cards. Morover, smart-card aware applications don't see any difference between an Applet running onto a real smart-card, and the one running in the emulator. This is achieved by integrating the emulation environment directly within the PCSC-Lite middleware layers. Specifically, JC-Emulator is composed of a virtual reader driver, namely libVirtualSCReader1.so, and the JavaCard emulator itself, that interacts with and runs user-written JavaCard Applets. Once installed inside PCSC-Lite, the virtual reader gives to the system a view of a "fake" smart-card serial reader, that actually gateways command APDUs to the emulator itself, which in turn passes them to the user Appplets. ---------------------------------------------------------------------- LICENSE ---------------------------------------------------------------------- This software is released under the GNU GENERAL PUBLIC LICENSE. See the file 'COPYING' for details. ---------------------------------------------------------------------- REQUIREMENTS ---------------------------------------------------------------------- - A Java CSP with RSA/DES/3DES Crypto capabilities. This needs to be statically installed into your Java installation tree. - IAIK Java CSP (a copy is contained in emulator/lib dir, at the moment). This does not need static installation, as it is dynamically loaded by the emulator. This software has been developed and tested using the "The Legion of Bouncy-Castle Java CSP". ---------------------------------------------------------------------- COMPILATION ---------------------------------------------------------------------- Go to ifd-handler. Type make. Go to main jc-emulator folder. Type make. ---------------------------------------------------------------------- USE ---------------------------------------------------------------------- 1. Copy compiled code of your JavaCard Applet into the 'applets' directory 2. Stop your pcscd daemon, if it is running 3. Install the virtual serial reader. Edit /etc/reader.conf, adding a reference to the ifd-handler/libVirtualSCReader1.so library. Specify '4000' as CHANNEL ID. This is the port number the server listens to. Check out the 'reader.conf' example file. 4. Launch the 'server.sh' script. This will emulate connection of a virtual serial reader to your PC. Note: this script will give several log messages on its STDOUT. 5. Start your pcscd daemon. 6. Launch the 'installer.sh' script. Just select the classes you want to install. 7. Use the server GUI interface to virtually insert a card. 8. Use your own smart-card aware application and enjoy. For further information, check out the 'doc' directory. ---------------------------------------------------------------------- DOCUMENTATION ---------------------------------------------------------------------- This project has been developed as part of a Thesis in Computer Engineering. The docs folder contains the original thesis in italian english only, sorry. And, there is this README file. ---------------------------------------------------------------------- NOTES ON SERIALIZATION ---------------------------------------------------------------------- Serialization is still experimental. Don't rely on it. In order to make it work with a JavaCard Applet, you must modify every class that is not derived from Applet, adding 'implements java.io.Serializable' into the class definition. Bye, Tommaso Cucinotta. -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <cuc...@ss...> - 2003-08-06 17:48:28
|
Hi all, a new package, JC-Emulator, has been published on the Smart Sign web site, allowing to emulate JavaCard Applets onto a host machine: it is integrated within the PCSC-Lite middleware layers, so that smart-card aware applications do not need any change in order to work with an Applet running into the emulator (vs. working with an Applet running onto a real JavaCard smart-card). More details follow below. Note that this project allows to emulate also Applets while using cryptographic facilities (JavaCard API). You can download the source code pointing your browser to the Smart Sign web page: http://smartsign.sourceforge.net then following the link to the SourceForge Download area. Please, note that the package is in its very early release, is not documented at all (just italian documentation is available, sorry), and really needs feedback/comments. Feel free to submit any comment to the Smart Sign mailing lists: mailto:sma...@li... mailto:sma...@li... Bye, Tommaso Cucinotta. -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2003-07-23 19:18:32
|
Hi all, a JNI port of the MuscleCard API has been developed, allowing Java applications and Applets to access MuscleCard supported smart-card services directly from the Java language. See bottom for further details. The package sources are available for download from the Smart Sign web site: http://smartsign.sourceforge.net Please, follow the links to the SF Download area, then download the JMuscleCard-0.0.1.tar.gz tarball. Please, submit any comments to the Smart Sign mailing lists: mailto:sma...@li... mailto:sma...@li... Bye, Tommaso. ============================================================ JMUSCLECARD - MuscleCard API for Java ============================================================ Main developer: Alessandro Pieroni - api...@ti... Coordinator: Tommaso Cucinotta - cuc...@ss... Organization: Scuola Superiore Sant'Anna, Pisa - Italy ------------------------------------------------------------ DESCRIPTION ------------------------------------------------------------ JMuscleCard is a JNI bridge allowing Java applications and Applets to use MuscleCard API. By using JMuscleCard it is possible to use, directly from the Java language, all the smart-card devices that are supported by the MuscleCard project (e.g. JavaCard compliant devices, Cyberflex, ...). The bridge has been kept as simple as possible, so it almost maps one-to-one the C functions of the MuscleCard API to Java. The two main classes are: - the JMuscleCard class, that manages smart-card connections and allows listing of devices and connecting to the card. - the MSCTokenConnection class, that handles a single connection to a smart-card device, allowing to manage on board PINs, objects and cryptographic keys. ------------------------------------------------------------ REQUIREMENTS ------------------------------------------------------------ Software - PCSC-Lite with MuscleCard enabled - the PCSC-Lite driver for your smart-card reader - the MuscleCard driver for your smart-card - Note: JavaCard cards need a MuscleCard Applet instance on-board, and it must already have been formatted - Java Development Kit (J2SDK) - Java CSP (only required for the tests) Hardware - a smart-card reader supported by PCSC-Lite - a smart-card supported by the MuscleCard project ------------------------------------------------------------ LICENSE OF USE ------------------------------------------------------------ This project is distributed under the terms of the GNU GPL license. See the file COPYING for details. ------------------------------------------------------------ COMPILATION ------------------------------------------------------------ Download the package tarball, unpack it, switch to sources directory, arrange paths in Makefile, then type 'make': [~] tar -xzf JMuscleCard-0.0.1.tar.gz [~] cd JMuscleCard [~/JMuscleCard] emacs Makefile [~/JMuscleCard] make ------------------------------------------------------------ SELF TEST ------------------------------------------------------------ There is a test program that you can launch with 'make test'. It requires a cryptographic Java CSP to be installed on your machine, otherwise crypto tests will fail. WARNING: The test program creates resources on the smart card, such as cryptographic keys. If a JavaCard device is used, with the MuscleCard Applet, then the created keys can only be removed by deleting and re-instantiating the Applet. [~/JMuscleCard] make test You should start seeing a set of 'OK'. ------------------------------------------------------------ INSTALLATION ------------------------------------------------------------ Just type 'make install'. The two dynamic libraries and the JAR class archive are copied in the path specified on the Makefile (defaults to /usr/local/lib). ------------------------------------------------------------ USE ------------------------------------------------------------ Just insert the "JMuscleCard.jar" archive into the classpath when compiling an application using JMuscleCard. A line like this: import JMuscleCard.*; shall suffice to make all JMuscleCard functionalities available to your application. ------------------------------------------------------------ DOCUMENTATION ------------------------------------------------------------ Sorry, no documentation is available at the moment. Please, refer to the MuscleCard API specification, available on the MUSCLE project web page: http://www.musclecard.com -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2003-02-06 21:02:08
|
Hi all, a new release of the Sign-MCard package is available for download from the Smart Sign web site: http://smartsign.sourceforge.net In the new release, the loadkey_mcard utility can load both a private key and a public key certificate on the card at once. Further details follow. Please, submit any comments to the Smart Sign mailing lists: mailto:sma...@li... mailto:sma...@li... Bye, T. -- Sign/verify command line utilities for M.U.S.C.L.E. Cards ============================================================ This package provides a couple of command line utilities that allow you to calculate a digital signature of a generic file using the key and public key certificate stored on your smart card, and verify it against the original file. Actually the verify utility does not need any smartcard. An additional utility, `loadkey_mcard', is provided in order to easily transfer an already generated private key from your host machine to the smartcard. REQUIREMENTS ------------------------------------------------------------ This package requires PCSC-Lite from M.U.S.C.L.E. project and MuscleCard framework (release 1.0.1, actually) with proper smartcard reader's driver installed for your reader and card's plugin for your card. It also requires a MuscleCard supported card, that is a card for which a MuscleCard plugin has been developed (Schlumberger's Cyberflex 32K MuscleCard Applet or Gemplus' 211/PK with MuscleCard Applet or Cryptoflex 16K, actually). Please, check out the MuscleCard web site for an up-to-date list of supported cards: http://www.musclecard.com. This utility compiles correctly on RedHat 6.x based systems, but not on a RedHat 7.2 system, because on these systems OpenSSL comes in the "Engine" flavour. Compilation is still possible on such systems by using a custom OpenSSL installation without the "Engine" capability. The custom installation path can be specified with the `--with-openssl=' switch to the configure script. This utility can also work without smartcards at all, if the user's private key and certificate are stored on the hard disk as files in standard OpenSSL format. In this case, MuscleCard and PCSC Lite are still required to be installed on your system in order to link the executables. USAGE ------------------------------------------------------------ Just type: user > sign_mcard --help user > verify_mcard --help Here is an example usage: user > sign_mcard -in file.txt -out file.p7 -sc Please, enter smartcard PIN: ******* ... In order to load an already existing private key from your host machine to your smartcard, type: user > loadkey_mcard <keyfile.der> -kn <key_nb> -pn <pin_nb> Key file must be DER-encoded. In order to use digital signatures, you also have to load onto your smartcard your public key certificate, DER-encoded. You can do it by using XCardII from the MuscleCard site. Now you can also use loadkey_mcard to load a DER-encoded certificate on your card. Type: user > loadkey_mcard <keyfile.der> -kn <key_nb> -pn <pin_nb> \ -cf <certfile.der> -co <certOID> The certOID argument must match the "-cert sc:oid" argument to sign_mcard. PKCS#11 COMPATIBILITY ----------------------------------------------------------- Sign-MCard can be used in a compatible way with both the PKCS#11 module from the Smart Sign project, (Card-Edge-Token), and the PKCS#11 module from the MuscleCardFramework package. You only need to supply proper certificate-oid and key-num parameters to the sign_mcard program. ** Card-Edge-Token from Smart Sign ** The certificate object ID, supplied to sign_mcard by means of the "-cert sc:oid" option, must be the same as specified in the [SC_TOKEN] section of the gpkcs11.rc configuration file, in a line that looks like: CertificateOID cert Private key number, supplied to sign_mcard by means of the "-sc:num" option, must be the same as specified in the [SC_TOKEN] section of the gpkcs11.rc configuration file, in a line that looks like: # Key numbers to be used as user keys PrivateKeyNumber 0 ** PKCS#11 Module from MuscleCardFramework ** This module allows storage of multiple keys/certificates onto a same card. Key pairs 0-1,2-3,4-5,6-7 correspond to certificates object IDs "c0", "c1", "c2", "c3". The certificate object ID and key numbers at sign_mcard invokation must be set accordingly. Please, note that you can only use with sign_mcard keypairs and certificates generated with this PKCS#11 module, but you cannot use with the same module a keypair/certificate loaded with the loadkey_mcard utility. LICENSE ------------------------------------------------------------ This package has been obtained as a modification of the OpenSSL utility "sign" by Eric Young. Changes have been done by Tommaso Cucinotta as part of the SmartSign project (http://smartsign.sourceforge.net). Before compiling and using this package, please assure to agree with the terms stated into the LICENSE file. All of the additional modules that were necessary to integrate the MUSCLE Card framework into this package, provided as separate files, are part of the SmartSign project and retain the original SmartSign software license. As a further note, please note that redistribution of this package is only allowed if the original authors, enumerated in the AUTHORS file, are clearly cited in every documentation and advertising material that is eventually added to the package itself. INSTALLATION ------------------------------------------------------------ (see also the REQUIREMENTS section) user > ./configure user > make root # make install TECHNICAL NOTES ------------------------------------------------------------ The signing utility relies on the user's private key being stored onto the smartcard. Use of such key should be PIN protected. The PIN number of the required PIN for using the key is deduced from the key ACL. It also supports an ACL requiring no PIN at all. In this case, the user is not prompted for a PIN, but a warning message is printed. It also relies on the user's public key certificate to be stored DER-encoded into an object. This object does not need to be PIN protected. Default key number, object identifier and PIN number are customizable by editing the proper section of Makefile.in, then (re-)configuring. The default values are also overridable by using command line options. See the help message from sign_mcard for details. The verify utility does not require the smartcard at all. It only needs the original data, the root public key cert and the PKCS#7 signature of the data. The signature is stored as a PKCS#7 blob and includes the user's public key certificate. |
From: Tommaso C. <ke...@ti...> - 2003-02-04 16:55:51
|
Hi all, the latest release of OpenSSH-MCard is now available as an RPM package. It's been built and tested on a RedHat-7.3 Linux system. You can download it from the Download section of the SmartSign site: http://smartsign.sourceforge.net Please, note that the RPM package only contains the modified programs, that have been renamed to scssh-agent, scssh-add, scssh-keygen, so they can coexist with your original OpenSSH installation with no problems. This binary distribution is statically linked with the right OpenSSL library, so you don't have to care about that. The only requirement is PCSC-Lite with MuscleCard support enabled. Try it out and submit any comments to the SmartSign mailing lists: mailto:sma...@li... mailto:sma...@li... Bye, Tommaso. |
From: Tommaso C. <ke...@ti...> - 2003-01-24 15:30:53
|
Hi all, a new OpenSSH-MCard package has been released, by integrating latest OpenSSH package for Linux (3.5p1) with latest PCSC-Lite / MuscleCard smart card middleware (v1.1.1), within the SmartSign project. It can be downloaded at the URL: http://smartsign.sourceforge.net Differences with previous release include: -) update to latest MuscleCard and Applet -) ability to use more keys onto a same card -) ability to specify the key numbers at run-time, by providing optional command-line options to ssh-add and ssh-keygen -) URI-like syntax in ssh-add allows mixed loading of file-keys and card-keys -) better separation of the MuscleCard support with respect to the original OpenSSH package Further details follow at the bottom of this message. Please, try out the package and post comments to the Smart Sign mailing lists: mailto:sma...@li... mailto:sma...@li... Bye, Tommaso. -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2003-01-15 09:17:37
|
I'm posting this message again because it had a wrong subject. I apologize for the repetition. -- Tommaso Cucinotta wrote: > > Hi all, > > I'm currently working on an update to the OpenSSH-CardEdge package, > the modified OpenSSH with MuscleCard smart card support (i.e. JavaCard > with MuscleCard Applet, Cryptoflex, etc...). > > Please, check out the unofficial URL: > > http://feanor.sssup.it/~tommaso/openssh3-mcard.tgz > > and submit comments to the Smart Sign mailing list: > > mailto:sma...@li... > > It has been compiled with RedHat7.3, OpenSSL 0.9.6g (yes, it still > requires a separate OpenSSL installation) and PCSC-Lite-1.x. > > Please, read the README, as there are syntax changes w/respect to > previous release. Now you can choose at invokation-time the MuscleCard > key numbers to use, both during key generation and usage. Also a few > tests with multiple keypairs have been done. > > In short (go to message bottom for furhter details): > > > eval `./ssh-agent` > > ./ssh-keygen -t rsa-sc[:prv_key_num[:pub_key_num]] > > ./ssh-add sc:[prv_key_num[:pub_key_num]] > > I'm gathering feedback/comments so to come up with a new release for > the next week. > > Bye, > T. > > -- > > ************************************************************ > This is a modified version of the OpenSSH-3.5p1 source tree for > Linux. It contains an experimental version of a smartcard module for > use with MuscleCard supported smart cards. This package has been > modified and adapted as a part of the Smart Sign project: > > http://smartsign.sourceforge.net > > SUMMARY OF CHANGES: > > - Requires PCSC-Lite, a smart card reader and its driver for PCSC-Lite, > a MuscleCard supported smart card and its Plugin > > - Enabling Muscle Card module during configuration > > ./configure --with-musclecard[=path] --with-ssl-dir=/usr/local/ssl > If path is omitted, default is /usr/local. > If you are using a RedHat release >= 7.0, you need to recompile the > OpenSSL > library with NO ENGINE SUPPORT, place it somewhere in your system > (default is /usr/local/ssl), and tell to OpenSSH-MCard where it is. > > - Building modified programs > > . make > > Please, use and install **ONLY** ssh-agent, ssh-keygen and ssh-add. > Other OpenSSH programs get compiled exactly the same, but with more > link > dependencies. > > - ssh-agent > > . Launch as usual, here you don't need anything special > . EXAMPLE: eval `./ssh-agent` > > - ssh-keygen > > . Launch with the '-t rsa-sc' option to generate a > keypair and store it on the smartcard. > Try a 'eval `./ssh-agent`; ssh-add -L' to view > new identity public information. > . Launch with '-t rsa-sc[:prv[:pub]]' with optional > private and public key number(s) to customize the > MuscleCard key numbers to be used during generation. > . Launch as usual to generate file-based key pairs. > . EXAMPLE: ./ssh-keygen -t rsa-sc > . EXAMPLE: ./ssh-keygen -t rsa-sc:3:2 > > - ssh-add > > . Launch using the special sc:[prv_nb[:pub_nb]] URI-like notation to > add > a smartcard identity. You will be prompted for the smartcard PIN > protecting the key (usage of the private key). > . The optional prv_nb and pub_nb parameters specify key numbers > identifying a keypair onto the smart-card. These numbers must be the > same as provided in the ssh-keygen program when generating the keys. > . You can also use keys generated or imported using other programs > (i.e. XCardII); you just need to know their numbers. Public key > should > be always readable. > . Launch as usual to add other (file) identities > . Use 'ssh-add -L' to view all the loaded identities, > both file and smart card ones. > . After adding the identity, you can use the normal ssh > client to connect to a remote server using the smartcard > . EXAMPLE: ./ssh-add sc: > . EXAMPLE: ./ssh-add sc:3:2 > > - Customizing behaviour > > This module uses default card PIN, public and private key > numbers as specified in the file muscle-card/Makefile.in, > under the "Customization options" section. You can change > the default values, if you need it. > The provided default value for the PIN number is compatible > with the MuscleCard release coming with PCSC-Lite v1.1.1. > Default key numbers to be used during key generation can be > overriden with the '-t rsa-sc[:prv[:pub]]' ssh-keygen syntax > and the 'sc:[prv[:pub]]' URI-like ssh-add notation. > > - Note > > This module does not use any certificates for key > management. > > - For further information, please, refer to the SmartSign > mailing list: > > sma...@li... > > TODO > > - Allow selection of the smartcard reader / token in case of multiple > ones available > - Ameliorate syntax > ************************************************************ > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Smartsign-users mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartsign-users -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: <ke...@ti...> - 2002-10-29 16:20:21
|
Hi all, due to a few postings to the Smart Sign lists with some "advertisement" contents I've been forced to change the privacy settings of the lists to be more restrictive. Specifically, from now on only members will be able to post messages to the lists. Furthermore the e-mail addresses which previous "advertisment" messages came from have been held for approval. I hope this is enough to avoid repetition of such message posts in the future. Bye, Tommaso Cucinotta |
From: <jam...@et...> - 2002-09-13 22:00:19
|
Dear smartsign-devel =2C =3CBODY bgColor=3D#ffccff=3E =3CTABLE border=3D0 cellPadding=3D0 cellSpacing=3D0 width=3D475=3E =3CTBODY=3E =3CTR=3E =3CTD align=3Dmiddle vAlign=3Dtop=3E=3C=2FTD=3E=3C=2FTR=3E=3C=2FTBODY=3E=3C=2FTABLE=3E=3CBR=3E =3CTABLE=3E =3CTBODY=3E =3CTR=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E =3CTD bgColor=3D#b8ecff borderColor=3D#0000ff width=3D=2290%=22=3E=3CFONT color=3D#ff0000 face=3D=22Arial Black=22 size=3D6=3E =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B Want To Harvest A Lot Of Email =3B =3B Addresses In A Very Short Time=3F=3C=2FFONT=3E =3CP=3E=3CB=3E=3CFONT color=3D#0000ff face=3DArial size=3D4=3EEasy Email Searcher=3C=2FFONT=3E=3CFONT color=3D#ff00ff face=3DArial size=3D4=3E =3B is =3B a =3B powerful =3B Email =3B software =3B =3B that =3B harvests general Email lists from mail servers =3B =3B =3C=2FFONT=3E=3CFONT color=3D#0000ff face=3DArial size=3D4=3EEasy Email Searcher =3C=2FFONT=3E=3CFONT color=3D#ff00ff face=3DArial size=3D4=3Ecan get 100=2C000 Email=3C=2FFONT=3E=3C=2FB=3E =3CFONT color=3D#ff00ff face=3DArial size=3D4=3E=3CB=3Eaddresses directly from the Email servers in only one hour! =3B=3C=2FB=3E=3C=2FFONT=3E=3C=2FP=3E =3CUL=3E =3CLI=3E=3CFONT face=3DArial size=3D2=3E=3CB=3E=3CFONT color=3D#0000ff=3EEasy Email Searcher=3C=2FFONT=3E=3C=2FB=3E is a 32 bit Windows Program for e-mail marketing=2E It is intended for easy and convenient search large e-mail address lists from mail servers=2E The program can be operated on Windows 95=2F98=2FME=2F2000 and NT=2E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial size=3D2=3E=3CB=3E=3CFONT color=3D#0000ff=3EEasy Email Searcher=3C=2FFONT=3E =3C=2FB=3Esupport multi-threads =28up to 512 connections=29=2E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial size=3D2=3E=3CB=3E=3CFONT color=3D#0000ff=3EEasy Email Searcher=3C=2FFONT=3E=3C=2FB=3E has the ability =3B to reconnect to the mail server if the server has disconnected and continue the searching at the point where it has been interrupted=2E=3C=2FFONT=3E =3CLI=3E=3CFONT face=3DArial size=3D2=3E=3CB=3E=3CFONT color=3D#0000ff=3EEasy Email Searcher=3C=2FFONT=3E=3C=2FB=3E has an ergonomic interface that is easy to set up and simple to use=2E=3C=2FFONT=3E =3C=2FLI=3E=3C=2FUL=3E =3CP=3E=A1=A1=3CB=3E=3CFONT color=3D#0000ff face=3DArial=3EEasy Email Searcher is an email address searcher and bulk e-mail sender=2E It can verify more than 5500 email addresses per minute at only 56Kbps speed=2E It even allows you send email to valid email address while searching=2E You can save the searching progress and load it to resume work at your convenience=2E All you need to do is just input an email address=2C and press the =22Search=22 button=2E=3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E =3CP=3E=3CB=3E=3CFONT color=3D#0000ff face=3DArial=3E=3CBR=3E=3C=2FFONT=3E=3CFONT color=3D#ff0000 face=3DArial size=3D4=3E=3CI=3EClick The Following Link To Download The Demo =3A=3C=2FI=3E=3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E =3CP=3E=3CB=3E=3CFONT color=3D#ff0000 face=3DArial size=3D4=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fdownload=2Femail=2Fnewees=2Ezip=22=3EDownload Site 1=3C=2FA=3E =3B =3B =3B =3B =3B=3C=2FFONT=3E=3Cfont face=3D=22Trebuchet MS=22=3E=3CFONT color=3D#ff0000 size=3D4=3E =28 OR You Can Send Email To =3B =3C=2FFONT=3E=3C=2Ffont=3E=3Cfont size=3D=224=22 color=3D=22#0000FF=22 face=3D=22Arial=22=3E130=4095951=2Ecom=3C=2Ffont=3E=3CFONT color=3D#ff0000 face=3DArial size=3D4=3E =3B For More Information About =3B This Program =29=3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E =3CP=3E=3CB=3E=3CFONT color=3D#ff0000 face=3DArial size=3D4=3E=3CA href=3D=22http=3A=2F=2Fbestsoft=2E3322=2Eorg=2Fonlinedown=2Fnewees=2Ezip=22=3EDownload Site 2=3C=2FA=3E =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B =3C=2FFONT=3E=3C=2FB=3E=A1=A1=3CFONT color=3D#0000a0 face=3DArial size=3D3=3E=3CSTRONG=3EIf =3B you can not download this program =2C =3B please copy the following link into your URL =2C and then click =22 Enter=22 on your Computer Keyboard=2E=3C=2FSTRONG=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT size=3D2=3E=3CFONT color=3D#0000a0 face=3DArial size=3D3=3E=3CSTRONG=3EHere is the download links=3A=3C=2FSTRONG=3E=3C=2FFONT=3E=3C=2FP=3E =3CDIV=3E =3CP=3Ehttp=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fdownload=2Femail=2Fnewees=2Ezip=3C=2FP=3E =3CP=3Ehttp=3A=2F=2Fbestsoft=2E3322=2Eorg=2Fonlinedown=2Fnewees=2Ezip=3C=2FP=3E=3C=2FFONT=3E=3C=2FDIV=3E =3CP=3E=3C=2FP=3E=3C=2FTD=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E=3C=2FTR=3E =3CTR=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E =3CTD bgColor=3D#0f95de width=3D=2290%=22=3E=3CFONT color=3D#ffffff face=3D=22Verdana=2C Tahoma=2C Helvetica=2C SansSerif=22 size=3D1=3E=3CB=3EDisclaimer=3A=3C=2FB=3E=3CBR=3EWe are strongly against continuously sending unsolicited emails to those who do not wish to receive our special mailings=2E We have attained the services of an independent 3rd party to overlook list management and removal services=2E This is not unsolicited email=2E If you do not wish to receive further mailings=2C please click this link =3CA href=3D=22 mailto=3Aremoval=40btamail=2Enet=2Ecn =22 target=3D=5Fblank=3E=3CFONT color=3D#fdd32a=3E=3CB=3Emailto=3Aremoval=40btamail=2Enet=2Ecn =3C=2FB=3E=3C=2FFONT=3E=3C=2FA=3E=2E =3B=3C=2FFONT=3E=3CB=3E=3CFONT class=3Ddisclaimer color=3D#000080 face=3DArial=3E=3CBR=3EThis message is a commercial advertisement=2E It is compliant with all federal and state laws regarding email messages including the California Business and Professions Code=2E We have provided the subject line =22ADV=22 to provide you notification that this is a commercial advertisement for persons over 18yrs old=2E=3C=2FFONT=3E=3C=2FB=3E=3C=2FTD=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E=3C=2FTR=3E=3C=2FTBODY=3E=3C=2FTABLE=3E =3CBR=3E |
From: Tommaso C. <ke...@ti...> - 2002-07-25 07:52:39
|
Hi all, if you are planning to try the MUSCLE Card versions of various Smart Sign packages and utilities (like card_edge_token, openssh-ce, sign-mcard), you will surely find really interesting this message, that reports information on how to load the MUSCLE Card Applet on a Schlumberger Cyberflex Access 32K card without the original SDK from SLB itself. T. -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2002-07-25 07:48:58
|
-- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2002-07-25 07:47:44
|
Martin Büchler wrote: > > Hello Dottore Cucinotta, > > I am stuck to use the _wonderful_ smartsign package under Win32, that's > why I dared to adapt the sctoken sources. My results are attached, hope > you find it useful. The GPKC11 library is written really portable, while > sctoken is not (yet). > I had to insert some wait states in order to avoid protocol errors, > while personalizing the card. I removed(!) most of the memory > management, which is a very bad idea, I know, but I am not a real C > programmer and would be very glad if someone could review. > > Regards > -- > Martin Buechler > Rotherstr. 8 . 10245 Berlin . Germany > phone: +49 30 5058 - 1891 fax: - 1600 > > ------------------------------------------------------------------------ > Name: sctoken.diff > sctoken.diff Type: application/x-unknown-content-type-diff_auto_file > Encoding: base64 > Download Status: Not downloaded with message -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2002-06-12 12:30:01
|
I apologize if you already got this... -------------------------------------- Hi all, I've built an RPM package of the Sign-MCard signing utility for the MUSCLE Card Framework. A new release, 0.1.4, has been released with minor changes to support the RPM packaging process and the new 1.1.1 release of pcsc-lite. Both the sources and an i386-compiled RPM are available from the Smart Sign web site (go straight to the download area, as usual). http://smartsign.sourceforge.net Please, submit any comments to the Smart Sign mailing lists: mailto://sma...@li... mailto://sma...@li... Bye, Tommaso. -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2002-05-28 15:49:07
|
I don't know if this message went through. Sorry if you get a duplicate. -- Hi all, in the latest published Sign-MCard beta I didn't remember to include these few lines in the "--help" message: " -cert file - Certificate file on file system\n", " -cert sc:name - Certificate file on smart card, in 'name'", With the 1st syntax, you specify a path to the certificate on your filesystem. With the 2nd syntax ('sc:' prefix), you specify a MuscleCard Object ID (a string) that contains your DER-encoded X.509 certificate on the card. Bye, T. -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: <ro...@ch...> - 2002-05-09 23:32:31
|
=3CHTML=3E=3CHEAD=3E =3CBODY bgColor=3D#ffccff=3E =3CTABLE border=3D0 cellPadding=3D0 cellSpacing=3D0 width=3D475=3E =3CTBODY=3E =3CTR=3E =3CTD align=3Dmiddle vAlign=3Dtop=3E=3C=2FTD=3E=3C=2FTR=3E=3C=2FTBODY=3E=3C=2FTABLE=3E=3CBR=3E =3CTABLE=3E =3CTBODY=3E =3CTR=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E =3CTD bgColor=3D#b8ecff borderColor=3D#0000ff width=3D=2290%=22=3E=3CFONT color=3D#ff0000 face=3D=22Arial Black=22 size=3D6=3E =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B Want To Harvest A Lot Of =3CFONT color=3D#0000ff=3ETarget =3C=2FFONT=3EEmail =3B =3B Addresses In A Very Short Time=3F=3C=2FFONT=3E =3CP=3E=3CB=3E=3CFONT face=3DArial size=3D4=3E=3C=2FFONT=3E=3CFONT color=3D#ff00ff face=3DArial size=3D4=3E=3CFONT color=3D#0000ff=3ETarget Email Extractor =3C=2FFONT=3Eis =3B a =3B powerful =3B Email =3B Software that =3B harvests Target Email Addresses from search engines=2C any specified starting URLs =2C including cgi =2C asp pages etc=2E=3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E =3CP=3E=3CFONT color=3D#000000 face=3D=CB=CE=CC=E5 size=3D2=3E =3B It Quickly and automatically search and spider from search engine=2C any specified starting URLs to find and extract e-mail addresses=3CBR=3E=3C=2FP=3E =3CLI=3EPowerful targeting ability=2E Only extract the specific email addresses that directly related to your business=2E=3CBR=3E =3CLI=3EIntegrated with 18 top popular search engines=3A Yahoo=2C Google=2C MSN=2C AOL=3CBR=3E =3CLI=3EFast Search Ability=2E Nearly can find thousands of e-mail addresses in an hour=2C allowing up to 500 simultaneous search threads!=3CBR=3E =3CLI=3EHelpful for anyone for internet Email marketing purposes=2E=3CBR=3E =3CLI=3EFree version updates=2E=3CBR=3E=3CBR=3E=3C=2FFONT=3E=3CFONT color=3D#ff0000 face=3DArial size=3D4=3E=3CI=3E=3CSTRONG=3EClick The Following Link To Download This Program=3A=3C=2FSTRONG=3E=3C=2FI=3E=3C=2FFONT=3E=3C=2FLI=3E =3CP=3E=3CB=3E=3CFONT color=3D#ff0000 face=3DArial size=3D4=3E=3CA href=3D=22http=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fdownload=2Femail=2FESE=2Ezip=22=3EDownload Site 1=3C=2FA=3E=3C=2FFONT=3E=3C=2FB=3E=3C=2FP=3E =3CP=3E=3CB=3E=3CFONT color=3D#ff0000 face=3DArial size=3D4=3E=3CA href=3D=22http=3A=2F=2Fbestsoft=2E3322=2Eorg=2Fonlinedown=2FESE=2Ezip=22=3EDownload Site 2=3C=2FA=3E =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B =3B =3C=2FFONT=3E=3C=2FB=3E=A1=A1=3CFONT size=3D2=3E=3CFONT color=3D#0000a0 face=3DArial size=3D3=3E=3CSTRONG=3EIf =3B you can not download this program =2C =3B please copy the following link into your URL =2C and then click =22 Enter=22 on your Computer Keyboard=2E=3C=2FSTRONG=3E=3C=2FFONT=3E=3C=2FFONT=3E=3C=2FP=3E =3CP=3E=3CFONT size=3D2=3E=3CFONT color=3D#0000a0 face=3DArial size=3D3=3E=3CSTRONG=3EHere is the download links=3A=3C=2FSTRONG=3E=3C=2FFONT=3E=3C=2FP=3E =3CDIV=3E =3CP=3Ehttp=3A=2F=2Fwww=2Ewldinfo=2Ecom=2Fdownload=2Femail=2FESE=2Ezip=3C=2FP=3E =3CP=3Ehttp=3A=2F=2Fbestsoft=2E3322=2Eorg=2Fonlinedown=2FESE=2Ezip=3C=2FP=3E=3C=2FFONT=3E=3C=2FDIV=3E =3CP=3E=3C=2FP=3E=3C=2FTD=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E=3C=2FTR=3E =3CTR=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E =3CTD bgColor=3D#0f95de width=3D=2290%=22=3E=3CFONT color=3D#ffffff face=3D=22Verdana=2C Tahoma=2C Helvetica=2C SansSerif=22 size=3D1=3E=3CB=3EDisclaimer=3A=3C=2FB=3E=3CBR=3EWe are strongly against continuously sending unsolicited emails to those who do not wish to receive our special mailings=2E We have attained the services of an independent 3rd party to overlook list management and removal services=2E This is not unsolicited email=2E If you do not wish to receive further mailings=2C please click this link =3CA href=3D=22 http=3A=2F=2Fwww=2Eautoemailremoval=2Ecom=2Fcgi-bin=2Fremove=2Epl =22 target=3D=5Fblank=3E=3CFONT color=3D#fdd32a=3E=3CB=3Ehttp=3A=2F=2Fwww=2Eautoemailremoval=2Ecom=2Fcgi-bin=2Fremove=2Epl =3C=2FB=3E=3C=2FFONT=3E=3C=2FA=3E=2E Auto Email Removal Company=2E Ref# 01222263545=3C=2FFONT=3E=3CB=3E=3CFONT class=3Ddisclaimer color=3D#000080 face=3DArial=3E=3CBR=3EThis message is a commercial advertisement=2E It is compliant with all federal and state laws regarding email messages including the California Business and Professions Code=2E We have provided the subject line =22ADV=22 to provide you notification that this is a commercial advertisement for persons over 18yrs old=2E=3C=2FFONT=3E=3C=2FB=3E=3C=2FTD=3E =3CTD width=3D=225%=22=3E=3C=2FTD=3E=3C=2FTR=3E=3C=2FTBODY=3E=3C=2FTABLE=3E =3CSTYLE=3E=3C=2FSTYLE=3E =3CBR=3E=3CBR=3E=3CBR=3E=3CBR=3E=3CA href=3D=22=22=3E=3C=2FA=3E=3CBR=3E=3CBR=3E=3CBR=3E=3CBR=3E=3CBR=3E=3CA href=3D=22=22=3E=3C=2FA=3E=3CBR=3E=3C=2FBODY=3E=3C=2FHTML=3E |
From: Tommaso C. <ke...@ti...> - 2002-03-22 16:05:11
|
Hi all, The new package Sign-MCard has just been released on the Smart Sign web-site. You can download it from: http://smartsign.sourceforge.net It basically allows to calculate and verify digital signatures in PKCS#7 format on generic files, using command line utilities. It is built upon the MuscleCard framework, so it works with all the smartcards that are supported by the MuscleCard project (examples are all JavaCard enabled smartcards and the SLB Cryptoflex card). The utilities have default configuration options that allow it to interoperate with the CardEdge-Token PKCS#11 module from the SmartSign project. Please, submit any comment, suggestion or request to the SmartSign mailing lists: mailto:sma...@li... mailto:sma...@li... Detailed information about the package follows. Bye, Tommaso. ********************************************************* Sign/verify command line utilities for M.U.S.C.L.E. Cards ============================================================ This package provides a couple of command line utilities that allow you to calculate a digital signature of a generic file using the key and public key certificate stored on your smart card, and verify it against the original file. Actually the verify utility does not need any smartcard. An additional utility, `loadkey_mcard', is provided in order to easily transfer an already generated private key from your host machine to the smartcard. REQUIREMENTS ------------------------------------------------------------ This package requires PCSC-Lite from M.U.S.C.L.E. project and MuscleCard framework (release 1.0.1, actually) with proper smartcard reader's driver installed for your reader and card's plugin for your card. It also requires a MuscleCard supported card, that is a card for which a MuscleCard plugin has been developed (Schlumberger's Cyberflex 32K MuscleCard Applet or Gemplus' 211/PK with MuscleCard Applet or Cryptoflex 16K, actually). Please, check out the MuscleCard web site for an up-to-date list of supported cards: http://www.musclecard.com. This utility compiles correctly on RedHat 6.x based systems, but not on a RedHat 7.2 system, because on these systems OpenSSL comes in the "Engine" flavour. Compilation is still possible on such systems by configuring the package with a custom OpenSSL installation obtained compiling without the "Engine" capability. The custom installation can be specified with the `--with-openssl=' switch to the configure script. This utility can also work without smartcards at all, if the user's private key and certificate are stored on the hard disk as files in standard OpenSSL format. In this case, MuscleCard and PCSC Lite are still required to be installed on your system in order to link the executables. USAGE ------------------------------------------------------------ Just type: user > sign_mcard --help user > verify_mcard --help Here is an example usage: user > sign_mcard -in file.txt -out file.p7 -sc Please, enter smartcard PIN: ******* ... In order to load an already existing private key from your host machine to your smartcard, type: user > loadkey_mcard <keyfile.der> <key_nb> <pin_nb> Key file must be DER-encoded. In order to use digital signatures, you also have to load onto your smartcard your public key certificate, DER-encoded. You can do it by using XCardII from the MuscleCard site. LICENSE ------------------------------------------------------------ This package has been obtained as a modification of the OpenSSL utility "sign" by Eric Young. Changes have been done by Tommaso Cucinotta as part of the SmartSign project (http://smartsign.sourceforge.net). Before compiling and using this package, please assure to agree with the terms stated into the LICENSE file. All of the additional modules that were necessary to integrate the MUSCLE Card framework into this package, provided as separate files, are part of the SmartSign project and retain the original SmartSign software license. As a further note, please note that redistribution of this package is only allowed if the original authors, enumerated in the AUTHORS file, are clearly cited in every documentation and advertising material that is eventually added to the package itself. INSTALLATION ------------------------------------------------------------ (see also the REQUIREMENTS section) user > ./configure user > make root # make install TECHNICAL NOTES ------------------------------------------------------------ The signing utility relies on the user's private key being stored onto the smartcard. Use of such key should be PIN protected. It also relies on the user's public key certificate to be stored DER-encoded into an object. This object does not need to be PIN protected. Default key number, object identifier and PIN number are customizable by editing the proper section of Makefile.in, then (re-)configuring. The default values are also overridable by using command line options. See the help message from sign_mcard for details. The verify utility does not require the smartcard at all. It only needs the original data, the root public key cert and the PKCS#7 signature of the data. The signature is stored as a PKCS#7 blob and includes the user's public key certificate. ********************************************************* -- ,------------------------------------------------. | Dr. Tommaso Cucinotta <t.c...@ss...> | >------------------------------------------------< ! Scuola Superiore di Studi Universitari ! ! e Perfezionamento S.Anna ! ! Pisa Italy ! `------------------------------------------------' |
From: Tommaso C. <ke...@ti...> - 2002-02-05 17:57:23
|
Hi all, I'd like to announce the new package Sign-CFlex, that contains command line utilities for calculating a PKCS#7 digital signature on a generic file and afterwards to verify it against the original data. It uses the old Cyberflex 16K cards w/out MuscleCard (MuscleCard utility is in development, don't worry). You can download the package from the SmartSign web site: http://smartsign.sourceforge.net (please, go directly to the download section, as the site is not up-to-date yet). This is an example usage: > sign_cflex -in file.txt -out file.p7 -sc The program load the p.k. certificate directly from the smartcard, then asks the user to enter the PIN, and calculates the PKCS#7 signature, that is stored in file.p7. If you don't have a certificate on your card, you can also give the "-cert" parameter specifying its location on your hard drive. Default key number, cert location and PIN number are the same as for the PKCS#11 CardEdge Token, so you can use OpenCA to store key & cert on the card itself. Please, return any feedback to: mailto:sma...@li... Bye, Tommaso. -- /------------------------------------------------\ | Dr. Tommaso Cucinotta <t.c...@ss...> | +------------------------------------------------+ | Scuola Superiore di Studi Universitari | | e Perfezionamento S.Anna | | Pisa Italy | \------------------------------------------------/ |
From: Tommaso C. <ke...@ti...> - 2002-01-18 14:48:42
|
Raghuram Sripada wrote: > > The model of the card is GPK8000. I was talking baout the same smartsign > bundle I submitted to you. > I am planning to create a VC project for this. I hope to send it to you > soon. Please, pay attention to licenses before including winscard.dll or any other third party's libraries or utilities into your project (your prev package contained winscard.dll, i.e.), as sometimes even ridistribution of free software is not allowed. > Now I am considering MuscleCard implementation for a Gemplus JavaCard. You should be able to use card-edge-token as it is for a Gemplus JavaCard card (GemXPresso 211-PK). Just load the applet from linuxnet on-board. > The refwrence errors are from GPKCS#11 library. I wanted to check with you > the stability of GPKCS#11 as you percieve. It's not mature and it's not stable. And, most of all, it's not maintained anymore, as far as I know. I didn't know this when I first decided to use it. For a new project, I would suggest using IBM's pkcs#11 framework. It seems to be much better, but I was told this. > My problem is exactly related to generating keypair using OpenSSL's > RSAGenerateKeyPair(). Now, I am in the process of moving this onto card. I > hope to fix this soon. Are you falling into the name-collision hole ? Remember to always link against ceay-libcryto. Bye, T. -- /------------------------------------------------\ | Dr. Tommaso Cucinotta <t.c...@ss...> | +------------------------------------------------+ | Scuola Superiore di Studi Universitari | | e Perfezionamento S.Anna | | Pisa Italy | \------------------------------------------------/ |
From: Tommaso C. <ke...@ti...> - 2002-01-17 17:40:48
|
Scott Noble wrote: > [...] > Actually I did have another question, since I have been doing testing > of the winscard API calls today. Most of the functions seem to be > working (including establish context, connect) and the SCardStatusA > returns the proper ATR and stat. However, when I actually try to > transmit to the smart card using SCardTransmit, I get a failure and an > error code of 0xE which is undefined in MS documentation. Did you have > any trouble getting this to work? Nope. When I finally understood how to link with that dll, everything worked (for what I can remember). Bye, T. -- /------------------------------------------------\ | Dr. Tommaso Cucinotta <t.c...@ss...> | +------------------------------------------------+ | Scuola Superiore di Studi Universitari | | e Perfezionamento S.Anna | | Pisa Italy | \------------------------------------------------/ |
From: Scott N. <sno...@ya...> - 2002-01-17 16:16:49
|
Well I tried the .def file that you initially sent, and I also tried using the Borland impdef.exe included in their free C++ Builder compiler ( http://www.borland.com/bcppbuilder/freecompiler/ ) - both methods worked (turns out I previously had an outdated .def file). Actually I did have another question, since I have been doing testing of the winscard API calls today. Most of the functions seem to be working (including establish context, connect) and the SCardStatusA returns the proper ATR and stat. However, when I actually try to transmit to the smart card using SCardTransmit, I get a failure and an error code of 0xE which is undefined in MS documentation. Did you have any trouble getting this to work? Regards, Scott --- Tommaso Cucinotta <ke...@ti...> wrote: > Scott Noble wrote: > > > > Tommaso, > > > > Thank you for your help - my application is successfully using > Microsoft's > > winscard.dll now. I just regenerated the .def file and it worked > fine after > > linking with the options you gave me. > > That's great ! Please, could you specify how did you generate the > .def > file ? > > Lemme know if you get any problems with card_edge-token. > > Bye, > T. > > > ===== Scott Noble sno...@ya... 408-586-8947 (home) 214-893-6981 (cell) __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ |
From: Tommaso C. <ke...@ti...> - 2002-01-17 13:51:46
|
Raghuram Sripada wrote: > > Tommaso, > > I am still trying to run SmartSign with Gemplus cards (No card_edge-token > yet) with Netscape under Win2K. What model of card ? So you embedded that card's commands, right ? Is this the SmartSign-Raghuda you submitted to me so far ? Do you want it to be published on the "contrib" section of the web site ? Did you ever consider implementing MuscleCard API for that card ? > I am facing problems (Memory reference errors emanating from GPKCS#11). It Are they from the token library or from the gpkcs#11 core itself ? Please, note that gpkcs11 core assumes all of the structures to be statically allocated, and this is one of the main troubles with that framework. I've added some check & workaround in the modified-gpkcs11 package, but it's very far to be comprehensive of all of the problems that could arise when structures are allocated/dealloated dynamically. This happens basically on card's removal, otherwise all should work fine. > Are you using GPKCS#11 to generate Key Pair under Card-Edge Token or are you > using Card based crypto engine to generate key pair? CardEdge-Token uses the GenerateKeyPair command of the Card Edge protocol to generate a key pair on the card itself (onboard generation), then it exports the public one with the ExportKey command. The older SCToken generates a keypair on the host with OpenSSL's RSAGenerateKeyPair() function then loads it into the card by overwriting the key file on the card. > Is this new token > working under Win2k/NT? CardEdge-Token has been tested with Win2K/CygWin, used with Netscape Communicator 6.1. > Are you able to use SmartSign (not CardEdge) with netscape under Win2K? If not the SmartPKCS11, what else would you like to use with Netscape from the SmartSign project ? Hope this helps. Bye, T. -- /------------------------------------------------\ | Dr. Tommaso Cucinotta <t.c...@ss...> | +------------------------------------------------+ | Scuola Superiore di Studi Universitari | | e Perfezionamento S.Anna | | Pisa Italy | \------------------------------------------------/ |
From: Tommaso C. <ke...@ti...> - 2002-01-17 11:33:40
|
Scott Noble wrote: > > Tommaso, > > Thank you for your help - my application is successfully using Microsoft's > winscard.dll now. I just regenerated the .def file and it worked fine after > linking with the options you gave me. That's great ! Please, could you specify how did you generate the .def file ? Lemme know if you get any problems with card_edge-token. Bye, T. |
From: Scott N. <sn...@tr...> - 2002-01-16 17:19:22
|
Tommaso, Thank you for your help - my application is successfully using Microsoft's winscard.dll now. I just regenerated the .def file and it worked fine after linking with the options you gave me. Regards, Scott ----- Original Message ----- From: "Tommaso Cucinotta" <cuc...@ss...> To: "Scott Noble" <sn...@tr...> Cc: <Sma...@li...>; <sma...@li...> Sent: Monday, January 14, 2002 8:54 AM Subject: Re: [Smartsign-users] Re: question on winscard.dll import library > Scott Noble wrote: > > > > Hi Tommaso, > > > > Thanks for the quick response. I tried adding the --add-stdcall-alias > > and --kill-at options when creating the import library, but the linker is > > still giving me a slew of "undefined reference" errors. I was also > > wondering what tool you use to generate your .def file, as the link to > > impdef.exe on the Cygwin page is bad. > > You can either try this (it seems an official and the right one): > > http://programming.ccp14.ac.uk/ftp-mirror/programming/mingw32/home/janjaap/m ingw32/platform-SDK/def/winscard.def > > or the one I included in a previous email of mine, or use impgen.exe or > some other tool from the Internet to generate it. > > I don't exactly remember which one gave me the right .def file, sorry. > > Please, let me know how this story ends so I can eventually > include it in the FAQ page on Smart Sign. > > > Once you got > > your application to link to winscard.dll, did you have any more problems? > > Nope. Just pay attention with gpkcs11.ini (gpkcs11.rc) for > Windows, as it requires all of the paths to be specified > in the Windows style (C:\xxx\yyy\...). And check the position > of the file itself, of course. I've put some note in the README > in the card-edge-token package itself. > > Bye, > T. > > -- > /------------------------------------------------\ > | Dr. Tommaso Cucinotta <t.c...@ss...> | > +------------------------------------------------+ > | Scuola Superiore di Studi Universitari | > | e Perfezionamento S.Anna | > | Pisa Italy | > \------------------------------------------------/ > |