Re: MUSCLE 61XX in Microsoft PC/SC implementation

p. I recommend a little layer on top of > > SCardTransmit to hide the pecularities of T=0 (vs > T=1). > > I think the the MUSCLE implementation should > be compatible to this, too. > Not if the driver implements IFD Hanlder as a layer over CT-API (as most MUSCLE drivers do). CT-API sa

Re: MUSCLE 61XX in Microsoft PC/SC implementation

Hello, Maybe then the ICC Service Proviver should be intelligent enough to send a Get Response when a 61 XX is returned and carry on with other transactions when the full data is returned. Dave *** Unix Smart Card Developers - M.U.S.C.

Re: MUSCLE Re: 61 XX

On Thu, 02 Aug 2001 09:19:53 +0200 Laurent Boulard <[EMAIL PROTECTED]> wrote: > David Corcoran wrote: > > >Hello, > > > >Points well taken. It seems unanimous that the driver should take care > of > >Get Response. I shall update the IFD Handler documentation to > reflect > >this. Thank you so

MUSCLE Reflex 72 problem (additional info)

>Hello! >I have just compiled and installed new Reflex 72 driver with pcsc-lite-0.9.3. (I use >Mindrake 7.2 Linux) >I connected to card normally, but when I transmit to the card any command I get >status code 64A0 (undocumented). >Where is problem? >Thank you! >Nikolay Stanchenko >JSC TKK A

MUSCLE Reflex 72 drivers

Hello! I have just compiled and installed new Reflex 72 driver with pcsc-lite-0.9.3. (I use Mindrake 7.2 Linux) I connected to card normally, but when I transmit to the card any command I get status code 64A0 (undocumented). Where is problem? Thank you! Nikolay Stanchenko JSC TKK **

MUSCLE 61XX in Microsoft PC/SC implementation

k the the MUSCLE implementation should be compatible to this, too. -- With best regards Axel Heider Towitoko AG Haidgraben 2 85521 Ottobrunn Tel: +49-89-66683-0 Fax: +49-89-66683-222 *** Unix Smart Card Developers - M.U.S.C.L.E. (Mov

Re: MUSCLE Is 61xx handled in your driver?

river, but its going to be true for some time to come. Regards, Peter T Bristol UK - Original Message - From: "Laurent Boulard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 01, 2001 8:08 AM Subject: Re: MUSCLE Is 61xx handled in your driver? >

Re: MUSCLE GPR400 ifd and T=0 vs T=1 from the driver perspective

>driver found in the card-0.9.6.tar.gz file found on the MUSCLE website. > >By 'mostly working' I mean that I've used formaticc to send a few APDUs >to a card and received the expected results. > >I'm having troubles understanding what the differences are between

Re: MUSCLE Is 61xx handled in your driver?

CLA INS P1 P2 Lc Le in 7816-4 speak (section 5.3.1 Fig 3) Peter T Bristol UK - Original Message - From: "David Corcoran" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 31, 2001 9:26 PM Subject: Re: MUSCLE Is 61xx handled in your driver? >

AW: MUSCLE Re: 61 XX

> > One question: How does the reader know which CLA byte to use? > In our driver for the ECO5000 we use the CLA byte of the former used command apdu. For example: The command apdu looks like this: 0x00 0xC0 0x00 0x01 0x02 0x3f 0x00 If the driver recognizes that a "Get Reponse" is neccessary he

Re: MUSCLE Is 61xx handled in your driver?

> In the perfect world yes ! but, sadly, people sometimes doesn't follow > correctly the ISO7816 or misunderstood it. I have cards (W4SC as an > example) which send back a GET RESPONSE even for a APDU without data. > This is really annoying as I have to modify my application to take care > of this

Re: MUSCLE Re: 61 XX

David Corcoran wrote: >Hello, > >Points well taken. It seems unanimous that the driver should take care of >Get Response. I shall update the IFD Handler documentation to reflect >this. Thank you so much for your suggestions. > Jim rees said: I agree that the application should not hav

Re: MUSCLE GPR400 ifd and T=0 vs T=1 from the driver perspective

t;[EMAIL PROTECTED]> Sent: Thursday, August 02, 2001 3:43 AM Subject: MUSCLE GPR400 ifd and T=0 vs T=1 from the driver perspective > > I've got a mostly working GPR400 PCSC IFD. It's based on the PCMCIA > driver found in the card-0.9.6.tar.gz file found on the MUSCLE website. &

MUSCLE GPR400 ifd and T=0 vs T=1 from the driver perspective

I've got a mostly working GPR400 PCSC IFD. It's based on the PCMCIA driver found in the card-0.9.6.tar.gz file found on the MUSCLE website. By 'mostly working' I mean that I've used formaticc to send a few APDUs to a card and received the expected results. I'm

Re: MUSCLE Re: 61 XX

Mahlzeit On Wed, Aug 01, 2001 at 08:34:06AM -0700, David Corcoran wrote: > Points well taken. It seems unanimous that the driver should take care of > Get Response. I shall update the IFD Handler documentation to reflect > this. Thank you so much for your suggestions. One question: How does

MUSCLE Re: 61 XX

Hello, Points well taken. It seems unanimous that the driver should take care of Get Response. I shall update the IFD Handler documentation to reflect this. Thank you so much for your suggestions. Regards, Dave *** Linux Smart Card

MUSCLE unsubscribe

unsubscribe Ranjeet Singh Malhotra Senior Hardware Design Engineer Trintech Technologies ( Nasdaq:TTPANeur Markt:TTP ) Trintech Building South County Business Park Leopardstown, Dublin 18 Ireland Phone : +353 1 207 4053 Fax : +353 1 207 4015 email : [EMAIL PROTECTED] http://www.trint

MUSCLE unsubscribe

unsubscribe *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***

Re: MUSCLE Is 61xx handled in your driver?

David Corcoran wrote: >I think you should handle the Get Response if your APDU looks like the >following: > >CLA INS p1 p2 p3 lentx xx xx xx xx xx lenrx > >Is this correct ? > In the perfect world yes ! but, sadly, people sometimes doesn't follow correctly the ISO7816 or misunderstood it. I hav

Re: MUSCLE Is 61xx handled in your driver?

I think you should handle the Get Response if your APDU looks like the following: CLA INS p1 p2 p3 lentx xx xx xx xx xx lenrx Is this correct ? Dave *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards i

Re: MUSCLE Is 61xx handled in your driver?

I agree that the application should not have to deal with this. But I don't think the driver should either. Anything that every driver must do in the same way really belongs at a higher level, in pc/sc. *** Linux Smart Card Developers -

Re: MUSCLE Is 61xx handled in your driver?

Hi, I completly agree with Andreas. Get Response is dependant on T=0 transport protocol and must not be handled at application level. This is at least what ISO 7816 says. Towitoko driver 2.0.X handles authomatically the Get Response when the command is Case 3 or Case 4. Also the issues athomatic

Re: MUSCLE Is 61xx handled in your driver?

When a card returns 61.xx, it means that the card has xx byte to return to host. Does a smartcard reader driver handle this, usually? My Todos driver does. It seemed useful at the time. I would like to know whether this is correct or not. Most other reader drivers I have looked at do n

Re: MUSCLE VerifyKey using OCF

ly 31, 2001 5:07 AM Subject: Re: MUSCLE VerifyKey using OCF > > > Hi All, > > > > Does anybody here use Cyberflex Access cards with OCF? > > > > If so, could you help me with the doubt below? > > > > In the Cyberflex Access card we have t

Re: MUSCLE Is 61xx handled in your driver?

> Most of the drivers pass the 61 XX back to the application to handle. I > think it is bad practice to handle this in the driver since it is a card > specific ISO function. GET RESPONSE is a transport level command. It should therefore be invisible for the application. The problem arises if you

Re: MUSCLE Is 61xx handled in your driver?

Hi Naomaru Our driver for the ORGA ECO 5000 automatically sends GET_RESPONSE; if the card returns '61 xx' or '9F xx' and the application passed a case 4 command APDU to the reader. The class byte for GET_RESPONSE is copied from the class byte used for the original command. IMHO this is the way i

Re: MUSCLE Is 61xx handled in your driver?

Hello, Most of the drivers pass the 61 XX back to the application to handle. I think it is bad practice to handle this in the driver since it is a card specific ISO function. This should happen above the reader abstraction where the card abstraction layer occurs. BTW - has anyone done an OSI l

RE: MUSCLE Is 61xx handled in your driver?

: [EMAIL PROTECTED] Subject:MUSCLE Is 61xx handled in your driver? When a card returns 61.xx, it means that the card has xx byte to return to host. Does a smartcard reader driver handle this, usually? Does it automatically send get_response APDU and get the return data, or does it pass

Re: MUSCLE VerifyKey using OCF

> Hi All, > > Does anybody here use Cyberflex Access cards with OCF? > > If so, could you help me with the doubt below? > > In the Cyberflex Access card we have the idea of identity such as AUT0, > AUT1, etc. In OCF to verify a Card Holder we must use the sendVerifyCommand. > Now w

MUSCLE Is 61xx handled in your driver?

When a card returns 61.xx, it means that the card has xx byte to return to host. Does a smartcard reader driver handle this, usually? Does it automatically send get_response APDU and get the return data, or does it pass the status code 61.xx to the application? I am not trying to find out whi

Re: MUSCLE VerifyKey using OCF

Does your OCF have a PassThru API? (Sun's OCF does.) If it does, PassThru allows you to send an APDU directly to the card, so you could try that. -- Concentration .. Naomaru Itoi, coding @ home *** Linux Smart Card Developers - M.U.S

MUSCLE DumbMouse Driver needed

Hi, Could someone tell me which driver I can use for my Dummouse Reader? Is there such a driver at all? greeting, Steffen Pfendtner *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environm

MUSCLE Cyberflex Access IC

Hi, i need to know some information about the IC used by Cyberflex Access: -manufacturer of the chip. -type of the chip. -(eventually) some datasheet about the performance of the cryptographic functions. Excuse me if this argument is (maybe) a little bit off-topic. Thanking you in advance, Emilian

MUSCLE Beta 1 14 days

Hello, I will release pcsc-lite beta 1 in 14 days complete with new documentation, a full test suite to test Windows compatibility, and test documentation. Beta 1 will be out for 3 weeks and then final 1 will be released. The testing has been done to test multi thread, multi readers, multi appl

Re: MUSCLE drivers

On Wed, 25 Jul 2001, Priit Randla wrote: > For some strange reason, my Reflex 72 does not work with this driver. > pcscd (0.9.3) registers card insertion/removal, reports ATR but does > not poll > the card, as other readers do. SEstablishContext, SCardListReaders, > SCardConnect all succ

Re: MUSCLE drivers

David Corcoran wrote: > > Hello, > > Due to popular demand. I re-released the Reflex 72 driver with the > IFDHANDLER 2.0 wrapper for CT-API. The driver is available on the website > now. All the card insertion/removal bugs have been solved. > > Regards, > Dave > For some strange reason,

RE: MUSCLE drivers

; Do you have plan to have the ReflexUSB driver for linux ? > > Thanks for any help and suggestions > Fabien > > > > > -Original Message- > From: David Corcoran [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 23, 2001 11:09 PM > To: [EMAIL PROTECTED] > Subject: MUSCLE

RE: MUSCLE drivers

to have the ReflexUSB driver for linux ? Thanks for any help and suggestions Fabien -Original Message- From: David Corcoran [mailto:[EMAIL PROTECTED]] Sent: Monday, July 23, 2001 11:09 PM To: [EMAIL PROTECTED] Subject: MUSCLE drivers Hello, Due to popular demand. I re-released

MUSCLE drivers

Hello, Due to popular demand. I re-released the Reflex 72 driver with the IFDHANDLER 2.0 wrapper for CT-API. The driver is available on the website now. All the card insertion/removal bugs have been solved. Regards, Dave *** Linux S

MUSCLE Olaf Jonkers, Utimaco, is on holiday, and out of the office...

I will be out of the office starting 14/07/2001 and will not return until 06/08/2001. Dear E-mail Respondent, At the moment I am not able to respond directly to your e-mail. I will respond to your message ASAP when I return (as of 6-08). In the meanwhile, send all urgent messages to the [EMAIL

Re: MUSCLE Schlumberger Cards with Gemplus reader

Apparently, at least with the Cyberflex, the card responds with its maximum speed and the Gemplus driver interprets this as the requested speed. If so, that would be a bug in the reader driver. The card remains at default timings until the reader sends it a PPS. By the way, the Cyberflex

Re: MUSCLE Gemplus PC410 new driver

Hi, I will run tests on Monday night to determine the status of the new Gemplus driver. Dave On Sat, 21 Jul 2001, Francois ARNAULT wrote: > Hello, > > Did somebody tried the Gemplus serial reader NEW driver ? > I did not succeed make it work. The pcscd daemons die whenever > I put a card in

MUSCLE Gemplus PC410 new driver

Hello, Did somebody tried the Gemplus serial reader NEW driver ? I did not succeed make it work. The pcscd daemons die whenever I put a card in the reader. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smar

Re: MUSCLE Schlumberger Cards with Gemplus reader

On Fri, 20 Jul 2001, Rich Wareham wrote: > I think I had a similar problem when trying to make the Cambridge > University smartcard (an IBM MFC) work with a GemCore reader. Eventually, > after tracing through long sniffer logs of communication with a Windows > PC, I managed to hack the existing l

Re: MUSCLE Schlumberger Cards with Gemplus reader

On Fri, Jul 20, 2001 at 01:30:35AM +0200, Francois ARNAULT wrote: > Hello, > > I'm trying to use Schlumberger Cryptoflex 8K and Cyberflex Access > smart cards in a Gemplus 410 reader driven by pcsc-lite-0.9.3, and I > have some trouble. I have the same combination. I ran into some trouble wi

Re: MUSCLE Schlumberger Cards with Gemplus reader

On Fri, 20 Jul 2001, Francois ARNAULT wrote: > Does anyone encountered the same problem and/or can help me to solve > it ? I think I had a similar problem when trying to make the Cambridge University smartcard (an IBM MFC) work with a GemCore reader. Eventually, after tracing through long snif

MUSCLE Schlumberger Cards with Gemplus reader

Hello, I'm trying to use Schlumberger Cryptoflex 8K and Cyberflex Access smart cards in a Gemplus 410 reader driven by pcsc-lite-0.9.3, and I have some trouble. The testpcsc (test.c) program shipped with pcsc-lite runs successfully. Things go wrong when I try to send APDU command to a S

Re: MUSCLE PKCS#11 for linux

Hi, I'm assuming from this message that the Cyberflex for Linux Starter's Kit 2.1 includes a PKCS#11 library/module? Is this correct? Thanks, Shelby Sebastien abdi wrote: > > Le Tuesday Jul 17, 2001 at 10:45:27AM +0200, Schalamonek Henrik a écrit : > > Hi there, > > > > I'm looking for a PKCS#1

MUSCLE Smart Card Development Team Available

Hello, I don't normally do this since I like to keep this list 100% technical but I would like to see if there is anyone out in sclinux land in need of a spectacular jump start software development team called Seilevel. These guys have done some marvelous work and are some of my friends so I'm p

Re: MUSCLE PKCS#11 for linux

Mahlzeit On Tue, Jul 17, 2001 at 10:45:27AM +0200, Schalamonek Henrik wrote: > I'm looking for a PKCS#11 implementation for linux that works with > Crpyptoflex smart cards but could not find any. I would really > appreciate if anyone could help me out. I'm also interested in other > cards if it

Re: MUSCLE PKCS#11 for linux

Le Tuesday Jul 17, 2001 at 10:45:27AM +0200, Schalamonek Henrik a écrit : > Hi there, > > I'm looking for a PKCS#11 implementation for linux that works with > Crpyptoflex smart cards but could not find any. I would really > appreciate if anyone could help me out. I'm also interested in other > ca

MUSCLE PKCS#11 for linux

Hi there, I'm looking for a PKCS#11 implementation for linux that works with Crpyptoflex smart cards but could not find any. I would really appreciate if anyone could help me out. I'm also interested in other cards if it has a PKCS#11 library for linux. Thanks in advance, Henrik Schalamonek ***

MUSCLE new drivers

Hello, Gemplus has released an updated version of the driver for the GemPC-410 serial reader. It can be found under the drivers section of the website "Source Drivers" Dave *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for

Re: MUSCLE check for pinpad

Hello, Erwann ABALEA wrote: > I don't think that the current release of the PC/SC standard > supports card readers with 'expansions', like PIN pads, screens, etc. > > Maybe the next version of the standard? When OCF was split into "core" and "opt" parts, it has been decided to move this functio

Re: MUSCLE check for pinpad

On 10 Jul 2001, Stephan Heinze wrote: > I have a question about card readers. How can I check (via > pcsc-lite-api) if the reader is a simple card reader or if it has a > pinpad to supply safe pin validation? I don't think that the current release of the PC/SC standard supports card readers with

MUSCLE check for pinpad

hallo, I have a question about card readers. How can I check (via pcsc-lite-api) if the reader is a simple card reader or if it has a pinpad to supply safe pin validation? Thanks in advance for any suggestions. Kind regards, Stephan Heinze

Re: MUSCLE GemPlus MPCOS-EMV

> "Pauley, John" wrote: > > All, > > First, sorry for the long post. > > My problem is that I have to authenticate the terminal with a GemPlus > MPCOS-EMV smart card using the following algorithm (this is in the G+ > MPCOS-EMV manual): > [description deleted] I'm not sure what your problem is

MUSCLE GemPlus MPCOS-EMV

Title: GemPlus MPCOS-EMV All, First, sorry for the long post. My problem is that I have to authenticate the terminal with a GemPlus MPCOS-EMV smart card using the following algorithm (this is in the G+ MPCOS-EMV manual): Known by both the card and the terminal: The "System" key, K, a 16-b

Re: MUSCLE man pages

If you mean the CT-API man pages, you can get them from the towitoko-2.0.4 source package from http://www.geocities.com/cprados or from the Debian mirror nearest to you, f.i: http://http.us.debian.org/debian/pool/main/t/towitoko (note that I'm not native english-speaker and there may be imperfect

MUSCLE man pages

Hello, I saw the wonderful man pages which were part of the debian distribution - could someone email them to me at: [EMAIL PROTECTED] ? Also, would anyone mind if I put them in the standard distribution ? Dave *** Linux Smart Card De

MUSCLE Infineer drivers

Hello, I have released the drivers for the Infineer DT3500, DT3000, and DT4000 readers. The 3500 is USB, the 3000 is serial and the 4000 is pcmcia. The drivers have been released under full source so that you may modify them if needed. Best Regards, Dave ***

MUSCLE Perl wrappers

Hello, Some guys from Gemplus have released some wrappers for PC/SC for Perl. These Perl wrappers allow you to write extremely fast scripts for smartcards and are wonderful for doing bulk formatting. The software can be found under the Middleware section of the site. I have some Debian package

MUSCLE Re: OCF/GemPC 430

Date: Mon, 2 Jul 2001 21:58:46 +0200 From: Jean-Luc Giraud <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Fwd: MUSCLE Rich Wareham <[EMAIL PROTECTED]>] (fwd)] Message-ID: <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> Mime-Version

MUSCLE Re: GemPC 430 ATR

From: Jean-Luc Giraud <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Fwd: MUSCLE Error using an IBM MFC in GemPlus readers.] Message-ID: <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=u

MUSCLE Unsubscribe

Please remove from this list. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html **

MUSCLE Unsubscribe

unsubscribe *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***

MUSCLE Unsubscribe

Unsubscribe *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***

MUSCLE unsubscribe

unsubscribe -- Jayce Piel [EMAIL PROTECTED][EMAIL PROTECTED] * Le site francophone des serveurs sous MacOS X *** Linux Smart Car

MUSCLE Rich Wareham ] (fwd)

From: Rich Wareham <[EMAIL PROTECTED]> X-X-Sender: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: OCF and PC/SC lite problems (newbie alert) Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I'm trying to use the OCF to talk to an IBM Multi-

Re: MUSCLE Error using an IBM MFC in GemPlus readers.

I didn't think there was a conflict at all between N and CWT/BWT. N is how long the reader waits before sending the next byte. CWT is how long it waits before giving up on receiving the next byte. BWT is how long it waits before giving up on receiving the next block. Also, I'm not getting the

Re: MUSCLE Error using an IBM MFC in GemPlus readers.

: "Jim Rees" <[EMAIL PROTECTED]> To: "Smart Muscleheads" <[EMAIL PROTECTED]> Sent: Friday, June 29, 2001 1:47 PM Subject: Re: MUSCLE Error using an IBM MFC in GemPlus readers. > The Gemplus reader shouldn't wimp out just because BWT is "reserved."

Re: MUSCLE Error using an IBM MFC in GemPlus readers.

27;IBM' > > I seem to remember that the IBM MFC card is an ETSI TE9 / CEN EN726 > (telecoms standard) card, and not an ISO 7816 card... > > Peter T > Bristol UK > > - Original Message - > From: "Rich Wareham" <[EMAIL PROTECTED]> &g

Re: MUSCLE Error using an IBM MFC in GemPlus readers.

Mahlzeit On Fri, Jun 29, 2001 at 08:47:57AM -0400, Jim Rees wrote: > The Gemplus reader shouldn't wimp out just because BWT is "reserved." My > Todos driver does its best to talk to the card and uses defaults when the > protocol parameters don't make sense. There are an amazing number of cards

Re: MUSCLE Error using an IBM MFC in GemPlus readers.

The Gemplus reader shouldn't wimp out just because BWT is "reserved." My Todos driver does its best to talk to the card and uses defaults when the protocol parameters don't make sense. There are an amazing number of cards out there that aren't strictly 7816 compliant. Besides, isn't BWT given b

Re: MUSCLE Error using an IBM MFC in GemPlus readers.

ISO 7816 card. Peter T Bristol UK - Original Message - From: "Rich Wareham" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 29, 2001 9:49 AM Subject: MUSCLE Error using an IBM MFC in GemPlus readers. > > Hello, > > I am currently port

Re: MUSCLE Error using an IBM MFC in GemPlus readers.

MAIL PROTECTED]> Sent: Friday, June 29, 2001 9:49 AM Subject: MUSCLE Error using an IBM MFC in GemPlus readers. > > Hello, > > I am currently porting some Windows software for the management of > smartcards over to Linux, the cards in question are IBM MFC 4.22 smart > cards. I g

MUSCLE Error using an IBM MFC in GemPlus readers.

Hello, I am currently porting some Windows software for the management of smartcards over to Linux, the cards in question are IBM MFC 4.22 smart cards. I get the same error on card power up from both the GemPlus 410 serial and GemPlus 430 USB card reader when using the PCSClite drivers. In both

Re: MUSCLE Disk encryption and more

s security value > > is > > dubious to say the least, and this guy didn't seem to understand what > > a > > trust path even implied. > > > > Alex > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > -

Re: MUSCLE Disk encryption and more

h a system, it's security value > is > dubious to say the least, and this guy didn't seem to understand what > a > trust path even implied. > > Alex > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > - Original Message ----- > From: &q

Re: MUSCLE Disk encryption and more

Ok, it's offtopic here, but I don't think, it is a good idea to use such policy. Why to protect such thing ?? A good policy is to setup a box and to have a model earning money on services not on the boxes or the system (linux). The user can do what ever he/she wants to do, if the user disconfigu

Re: MUSCLE need help

When I looked in cyberflex toolkit they were requiring xcard. The xcard that I have ( provided in the toolkit) didn't work. I don't know the usefulness of xcard and can I get another tool with which I can work. I recommend you use "pay" from our web site: http://www.citi.umich.edu/projec

MUSCLE need help

Hello there, I am working on a project that uses smart card. I am usin Cyberflex access Class 00 and Reflex 60 Smart card reader. I am using pcsc lite 0.8.4. I want to develop an application in java that will be using the smart card like the wallet example. When I looked in cyberflex toolkit they

Re: MUSCLE Disk encryption and more

Patrick Valsecchi wrote: > > > I don't have to store each signature of each bin into the smartcard. I won't > have enough RAM for that! I'll store inside each executable and library the > signed crypto hash. The kernel will check if the crypto hash is still the same > and the smartcard will just

Re: MUSCLE Disk encryption and more

Quoting [EMAIL PROTECTED]: > On Fri, 22 Jun 2001, Jim Rees wrote: > > > Ok, so you have a bunch of executables and a table of pre-computed > CRC's. > > > > No, you have a bunch of executables, and for each you have a crypto > hash > > signed with a private key. > > Ok. > > > You could sto

Re: MUSCLE Disk encryption and more

eheads <[EMAIL PROTECTED]> Sent: Friday, June 22, 2001 11:17 PM Subject: Re: MUSCLE Disk encryption and more > On Fri, 22 Jun 2001, Jim Rees wrote: > > > Ok, so you have a bunch of executables and a table of pre-computed CRC's. > > > > No, you have a bunch of ex

Re: MUSCLE Disk encryption and more

built into their spec a system to control what programs it can run, they should have. Peter T Bristol UK - Original Message - From: "Jim Rees" <[EMAIL PROTECTED]> To: "Smart Muscleheads" <[EMAIL PROTECTED]> Sent: Friday, June 22, 2001 10:13 PM Subject: Re: MUS

Re: MUSCLE Disk encryption and more

On Fri, 22 Jun 2001, Jim Rees wrote: > Ok, so you have a bunch of executables and a table of pre-computed CRC's. > > No, you have a bunch of executables, and for each you have a crypto hash > signed with a private key. Ok. > You could store the public key in the secure rom, but this guy wa

Re: MUSCLE Disk encryption and more

Hi, It's still crude, but we have a paper on smartcard based secure booting: http://www.citi.umich.edu/techreports/ Boot up from secure ROM, and use a smartcard to make sure kernels and application binaries are good. -- Concentration .. Naomaru Itoi *

Re: MUSCLE Disk encryption and more

Ok, so you have a bunch of executables and a table of pre-computed CRC's. No, you have a bunch of executables, and for each you have a crypto hash signed with a private key. You could store the public key in the secure rom, but this guy wants to use a smart card, presumably because he wants t

Re: MUSCLE Disk encryption and more

Thanks you, this is a very good recapitulation. Even better that my first mail ;-) Quoting Jeremy Impson <[EMAIL PROTECTED]>: > On Fri, 22 Jun 2001 [EMAIL PROTECTED] wrote: > > > On Fri, 22 Jun 2001, Jim Rees wrote: > > > > > But if you really are concerned about "very skilled hackers" you >

Re: MUSCLE Disk encryption and more

On Fri, 22 Jun 2001, Patrick Valsecchi wrote: > I can sign the kernel, the executables and the libraries. The loader (lilo) can > be in the securized memory of the processor. So before it loads the kernel, it > checks the signature with the smartcard. Then I'm quit sure it's my own kernel > th

Re: MUSCLE Disk encryption and more

Aren't CRC algorithms easy to reverse? Sorry for the sloppy terminology. Obviously this has to be a cryptographic hash, not just a crc. But I still think performance will not be a huge issue. dumaguete# ls -l /bsd -rwxr-xr-x 1 rees wheel 2172784 Jan 25 16:11 /bsd dumaguete# time md5 /bsd

Re: MUSCLE Disk encryption and more

On Fri, Jun 22, 2001 at 10:00:35PM +0200, Patrick Valsecchi wrote: > The user will be able to change the code, that's not the matter, but it wont be > able to run it on my customer's hardware. That's the point. And I don't this it > goes against any law neither any license. > > I'm sure it does

Re: MUSCLE Disk encryption and more

The user will be able to change the code, that's not the matter, but it wont be able to run it on my customer's hardware. That's the point. And I don't this it goes against any law neither any license. I'm sure it doesn't go against any GPL spirit. It's even possible that my source will be par

Re: MUSCLE Disk encryption and more

On Fri, 22 Jun 2001 [EMAIL PROTECTED] wrote: > On Fri, 22 Jun 2001, Jim Rees wrote: > > > But if you really are concerned about "very skilled hackers" you will need > > significant hardware protection, like a processor with integrated boot code > > or an epoxy potted processor and boot rom modul

Re: MUSCLE Disk encryption and more

I know that checking the CRC of the executable can lead to slowlyness (have to load each page of it), but I don't think I have the choice. This shouldn't be slow at all. You have to load the pages anyway, right? I hope you're not thinking about sending the entire kernel to the card, that w

Re: MUSCLE Disk encryption and more

Hi Why not, but this solution is not solving my problem. This just provides encrypted disk. My main concern, is disallowing the user to run its own executables. For answering peoples questions, I don't want to protect this hardware against governements or very high budgeted crackers. My custo

Re: MUSCLE Disk encryption and more

On Fri, 22 Jun 2001, Jim Rees wrote: > But if you really are concerned about "very skilled hackers" you will need > significant hardware protection, like a processor with integrated boot code > or an epoxy potted processor and boot rom module. Even then you won't be > able to completely protect

MUSCLE FW: SecurityFocus Call for Linux Articles

Wouldn't it be great if someone here could pump up the movement in this manner. See below ;-) Greetings, SecurityFocus is currently looking for writers to develop articles for the Linux focus area. Articles are generally 2000 - 2200 words long, and SecurityFocus offers compensation for each publi

Re: MUSCLE Disk encryption and more

I don't know about the rest of it, but a former colleague of mine worked on a secure booting system using a smartcard. I don't see anything on his web page about it but you could contact him directly. http://www.citi.umich.edu/u/itoi/ But if you really are concerned about "very skilled hackers"

  1   2   3   4   5   6   7   8   9   10   >