gmane.comp.java.jpos.devel

Re: FW: link - EMAIL ACCOUNT OR MACHINE COMPROMISED

2013-03-12T17:55:20

It appears that your email account or your machine has been compromised or has a virus, please correct and in the meantime I have placed you on moderation.


--- In jpos-dev-hHKSG33TihhbjbujkaE4pw< at >public.gmane.org, Naresh G L <naresh_gl< at >...> wrote:




------------------------------------

FW: link

Naresh G L — 2013-03-12T17:34:16

http://www.fvgiech.de/tdzmb/qcralgzsepm?agvm







[Non-text portions of this message have been removed]



------------------------------------

Re:4

willard kurisa — 2013-01-15T04:58:31

http://technolet.com/dateboatrobertjackson/


------------------------------------

Re: verifying the arpc with atalla box

Mark Salter — 2013-01-10T07:39:39

You really need to ask on an Atalla mailing list or of their support?

Any actual jPOS questions you have should really be asked on jpos-users:-

https://groups.google.com/forum/?fromgroups#!forum/jpos-users

verifying the arpc with atalla box

acarbajalvera — 2012-12-28T15:13:32

Hi: Trying to verify the arqc with the atalla box, sending the 350 command I just get the check digits, but not the arpc, so I assume I am not using the right keys. Looking at the atalla manual I notice that I need the IMK encrypted under the variant 9 of MFK. I have the clear IMK (this is a test system), and trying to get it encrypted under the variant 9 (command 10 ) I need the KEK encrypted under the variant 0 of MFK. My question is:  What command do I use to get the KEK encrypted under the variant 0 of MFK? 

Thanks in advance for your help

Regards,





------------------------------------

Re: DUKPT Pin Verification

Andy Orrock — 2012-10-22T12:10:44

Friend -

That KSN is between you and the transaction originator.  Check with them.
 This is not a jPOS question.

Andy


On Mon, Oct 22, 2012 at 6:26 AM, Arunkumar D <arun.buddha-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:



[Non-text portions of this message have been removed]



------------------------------------

Re: DUKPT Pin Verification

Arunkumar D — 2012-10-22T11:26:59

Hi Edurado,

  Very Thanks for your valuable reply.

  Now I verified the PIN with 3DES DUKPT IBM method.

  000000: 00 92 30 30 30 33 47 4f 30 39 30 39 45 39 36 30  ..0003GO0909E960
000010: 35 33 36 39 34 31 38 32 31 42 37 35 41 42 37 46  536941821B75AB7F
000020: 37 31 38 31 46 33 39 43 37 36 35 46 31 35 34 36  7181F39C765F1546
000030: 41 43 31 35 37 38 36 36 32 36 30 35 37 35 41 32  AC157866260575A2
000040: 44 41 30 30 30 41 38 30 30 30 30 31 43 37 30 46  DA000A800001C70F
000050: 45 30 35 33 32 45 34 42 45 39 38 39 30 31 30 34  E0532E4BE9890104
000060: 36 32 34 32 35 30 34 39 35 37 37 36 31 32 33 34  6242504957761234
000070: 35 36 37 38 39 30 31 32 33 34 35 36 34 33 38 36  5678901234564386
000080: 32 34 32 35 30 34 4e 36 31 32 33 34 46 46 46 46  242504N61234FFFF
000090: 46 46 46 46                                      FFFF


2012-10-22 16:37:21,628: INFO - [XBExtCommPoint] TCPIP Hexdump at receive

000000: 00 08 30 30 30 33 47 50 32 30                    ..0003GP20


 I suspect this time my problem could be with KSN descriptor ( 605 ) in my
case.

 Or is it could be with my KSN ? ( 75A2DA000A800001 )

 Please help me in this regard.

Regards,
Arun



On Mon, Oct 22, 2012 at 8:45 AM, Eduardo Espejo <eduardo.espejo-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Re: DUKPT Pin Verification

Eduardo Espejo — 2012-10-22T03:15:37

Hello Arun

The tool you are using at
(www.codemagus.com<http://www.codemagus.com/WebTools/cgi-bin/cmldkencrypt>)
generates a DUKPT 3DES Pin Block so you must use the GO command instead the
CK commnad for verifying Pin Blocks

Best Regards
*--
Eduardo*


On Sun, Oct 21, 2012 at 11:57 AM, Andy Orrock <orrock-9uYm5ZwILXmakBO8gow8eQ< at >public.gmane.org> wrote:



[Non-text portions of this message have been removed]



------------------------------------

Re: DUKPT Pin Verification

Andy Orrock — 2012-10-21T16:57:35

Hi Arun -

Apologies for weighing in here late.

The questions you're asking aren't at all related to jPOS. You should have
access to your customer's Thales distributor. They need to advise you
here. These are straight-up Thales questions.

I can give you some guidance. In your private queries to me, you asked:

"From the blogs, I have seen the composition of KSN descriptor. But, the
length of the
transaction counter bytes are ignore to fit into 3 byte spaces. I don't
understand how
HSM knows the KSN field is of specific size, because it's description
mentioned as 12-20H.
Since the value could be anywhere between 12-20H, the KSN descriptor
too has mentioned
about the length of the two fields, how it will identify the length of
the last field?"

[Where you say, "the blogs" you mean my blog,]

"I don't understand how HSM knows the KSN field is of specific size"

Your KSN Descriptor is 605, meaning 11 bytes.

You're probably befuddled by my blog where I say the Transaction Counter is
"essentially is the part "left over"."

Unfortunately, that's misleading. Thales says of the counter:

*"Transaction counter supplied by the PIN pad to identify a particular
transaction: 21 bits. Used by the HSM to compute the actual PIN key. The
left-most bit is supplied as the right-most bit of the device identifier.*
*The PIN pad cannot accept a serial number longer than 20 characters, so
the Host ensures that the total length of the first three fields does not
exceed 15 characters."*

So, that's your five bytes (and 1 bit).

So, your KSN is 6 + 0 + 5 + 5 = 16.

Andy Orrock

On Sun, Oct 21, 2012 at 10:12 AM, Arunkumar D <arun.buddha-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

[Non-text portions of this message have been removed]

------------------------------------

Re: DUKPT Pin Verification

Arunkumar D — 2012-10-21T15:12:12

Hi Mark,

  I already have a account in google and I am able to join in the
jPOS-users group. But when I do a new posting
  I am getting the permission error. I tried with another google account
also, I get the same error.

  I am not sure about enabling the access to post a new thread in the
group.

  I have sent another mail explaining for your queries. Will you please
help me in this regard?


Regards,
Arun


On Sun, Oct 21, 2012 at 8:22 PM, Mark Salter <marksalter-rIDUbWZ4T7Pk1uMJSBkQmQ< at >public.gmane.org>wrote:

Re: DUKPT Pin Verification

Mark Salter — 2012-10-21T15:00:26

It's not a problem, but I do suspect you will get a better qualified
discussion and resolution over there.

Ok, just checking, the 05 looked a little ominous :-)


So the natural PIN of the card is 2449 'minus 1234 or 1215 (if I have
done my sums correctly.

Thanks for the clear PIN details.


No I was wondering if the first place to check what you required matched
what this utility did was with the provider of this web utility (< at >
codemagus)

Yes, it was the people at codemagus I was thinking of :-).

Very good, I do always like to check, we do occasionally get all sorts
of sensitive or copyright data pasted by people not thinking it through.
I'm glad you did consider your keys.

Re: DUKPT Pin Verification

Mark Salter — 2012-10-21T14:52:40

Hello there

I am one of the mods of that group too, please acquire a google account
and then join the jpos-users group; posting will then be possible.

Re: DUKPT Pin Verification

Arunkumar D — 2012-10-20T21:13:36

Hi Mark,

  Sorry again. I don't have permission to access jPoS-users group. Kindly
help me to post the below query to jPoS-users group or
  grant me the permission to join in that group ( if you are one of the
moderator of that group ).

  My Query is :

  While working in DUKPT, I came across the below problem. If you could
help me out, it will be more helpful to me.

     I am using Thales RG8000 HSM.

     2012-10-17 17:49:14,607: INFO - [XBExtCommPoint] TCPIP Hexdump while
sending

     000000: 00 8f 30 30 30 39 43 4b 39 30 39 45 39 36 30 35
..0009CK909E9605
    000010: 33 36 39 34 31 38 32 31 42 37 35 41 42 37 46 37
36941821B75AB7F7
    000020: 31 38 31 46 33 39 43 37 36 35 46 31 35 34 36 41
181F39C765F1546A
    000030: 43 31 35 37 38 36 36 32 36 30 35 37 35 41 32 44
C157866260575A2D
    000040: 41 30 30 30 30 32 30 30 30 31 36 30 35 41 36 32
A000020001605A62
    000050: 38 32 43 42 39 38 41 35 44 33 30 30 34 36 32 34
82CB98A5D3004624
    000060: 32 35 30 34 39 35 37 37 36 31 32 33 34 35 36 37
2504957761234567
    000070: 38 39 30 31 32 33 34 35 36 34 33 38 36 32 34 32
8901234564386242
    000080: 35 30 34 4e 36 31 32 33 34 46 46 46 46 46 46 46
504N61234FFFFFFF
    000090: 46
                  F


     2012-10-17 17:49:14,816: INFO - [XBExtCommPoint] TCPIP Hexdump at
receive

     000000: 00 08 30 30 30 39 43 4c 32 34                    ..0009CL24


     The Message split-up is as follows;

     CmdCode => CK ( Verify DUKPT PIN IBM Method )

     BDK Encypted by LMK => 909E960536941821B75AB7F7181F39C7

     PVK Encrypted by LMK => 65F1546AC1578662 ( a Single Length One )

     KSN Descriptor => 605

     KSN => 75A2DA0000200016 ( My KSN Comprises of 75A2DA - BDK Id, 00002 -
Device Id, 00016 - Counter )

     Source Pin Block => 05A6282CB98A5D30

     Check Length => 04

     Account Number => 624250495776 ( 12 Digits excluding check digit )

     Decimalization Table => 1234567890123456

     PIN Validation Data => 4386242504N6

     Pin Offset => 1234FFFFFFFF ( Padded with 'F's )


    As mentioned in the response message, I am getting error as "PIN is
fewer than 4 or more than 12 digits in length"

     Since I am testing my application without PED, I am using the PIN
Block generated by a DUKPT utility
                                        at
http://www.codemagus.com/WebTools/cgi-bin/cmldkgipek

     The Clear BDK is 75A2DA799E4361FBA7C479FE5225FB1F ( For testing
purpose only )

     I created BDK as follows ( in console ),

     1. DD Command
             5EC7 3EF8 D680 5880 9D34 6BBF 29E0 EF45   ( Clear ZMK )

     2. DE Command
            A645 54F1 867F E2B8 3126 2DAC 8739 A0DB ( Encrypted ZMK )
            6FDF A94A ( Check Value )

     3. DG Command
        BDK Encrypted by ZMK : 67BE 7632 F7A0 856D E109 90A4 D89A BB5A
        BDK Encrypted by LMK : 909E 9605 3694 1821 B75A B7F7 181F 39C7


     Can you please help me to find out the reason for this error code 24?

     Please enlighten me on the concepts of KSN and KSN Descriptor.

   Since I don't have my PED in place, I have used Codemagus site for
generating PIN.

   My Clear PIN used for generating the encrypted PIN block is "2449".

   I suspect my KSN and KSN descriptor is wrong. I am not sure of what kind
of KSN I should be having for my BDK ( means the BDK Id in KSN ).

   Please help me in this regard.

   Thanks for all.


Thanks & Regards,
Arun


On Sun, Oct 21, 2012 at 1:59 AM, Arunkumar D <arun.buddha-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: DUKPT Pin Verification

Arunkumar D — 2012-10-20T20:29:14

Hi Mark,

Sorry that I mistakenly posted my question at jPOS Developers forum which
supposed to be
at users forum.

Anyway, I will answer for the queries you have asked below.

Sincerely Thanking you for your help.

Regards,
Arun

On Sat, Oct 20, 2012 at 3:54 AM, Mark Salter <marksalter-rIDUbWZ4T7Pk1uMJSBkQmQ< at >public.gmane.org>wrote:

This PIN block I have got from
http://www.codemagus.com/WebTools/cgi-bin/cmldkencrypt
after entering my clear BDK and my own composed KSN ( I am not sure of
the value I have
created ).

My Clear BDK is 75A2DA799E4361FBA7C479FE5225FB1F.

So, the KSN I have derived on my own is
KSN => 75A2DA0000200016 ( My KSN Comprises of 75A2DA - BDK Id, 00002 -
Device Id, 00016 - Counter )

The first 6 digits of KSN is my clear BDK. I am not sure that the BDK Id
is the 6 digits of clear value.

Please forgive me if I am too ignorant.

the keys injected into the virtual PED.
The IPEK is derived from the clear BDK and the KSN fed on the IPEK
generation page.

This is not a clear PIN Block. So, 05 is not the length of the PIN. My
actual PIN is 4 digits length. That is 2449.

For the given PIN offset, PIN got generated. So, it is unusual 1234.

I agree. I believe the web utility from codemagus is correct. So, I
suspect the problem
probably would be my inputs for creating the PIN blocks - KSN and KSN
descriptor.
If the utility is giving wrong results, I need to wait for my real PED
to come for testing.

My clear PIN is 2449.

Since I am new to DUKPT, I believe this utility works for our input data.
I believe their documentation( instructions ) are precise on my
understandings.

Our terminal is not ready yet. I need to wait for more time to get the
authentic PIN block from them.

I think you are asking for my PED provider. If the provider of the above
mentioned URL, I have not yet talked to them.

Thanks for your concerns. :-) It is a false keys only. To ensure that
the keys I am using
for KSN composition and the commands I used at Thales HSM for creating
the BDK I have
created, I have given the clear one.

I am posting this query in jPOS-users forum too. ( I am not permitted to
create any post there. Let me fix that issue and will post there ).

A big thanks and hearty gratitude for your valuable answers for my
query.

Re: DUKPT Pin Verification

Alejandro Revilla — 2012-10-19T22:47:45

goes to jpos-users.


[Non-text portions of this message have been removed]



------------------------------------

Re: DUKPT Pin Verification

Mark Salter — 2012-10-19T22:24:43

Hello.

I let this through because you had obviously spent some time composing a
smart question, although to the wrong mailing list, you should really
have used :-

https://groups.google.com/forum/#!forum/jpos-users

This is the PIN block as received/generated?

Are you sure this is not the clear PIN block?

Is your PIN 5 digits long - I am reacting to the 05 nothing more.


Perhaps an unusual offset - I just wanted to check you were sure on this
offset?

So your PIN block once in the clear reveals a PIN of the incorrect
length, indication the wrong clear PIN block format was used or the
different keys are being used to encrypt/decrypt.

What is the clear PIN please?
Do you know this service works?

Have you tried asking the provider first?

What did they say?

A test key I hope, if not report yourself to your IT Security department
immediately and tell them you have compromised your keys :-)!


Wrong keys used or clear PIN block is incorrect?


Might I suggest you restart this question thread < at > jpos-users, you might
get a wider/'better' audience there?

jpos-dev is intended more for the development of jpos than i's use you see.

DUKPT Pin Verification

CandieSweetieWoman — 2012-10-19T17:17:49

Hi All,

   Though I have not contributed anything in jPOS, I would like to summarize my issue in DUKPT Pin verification. Please help me to solve that.

While working on DUKPT, I am facing the below issue.

    2012-10-17 17:49:14,607: INFO - [XBExtCommPoint] TCPIP Hexdump while sending

    000000: 00 8f 30 30 30 39 43 4b 39 30 39 45 39 36 30 35  ..0009CK909E9605
    000010: 33 36 39 34 31 38 32 31 42 37 35 41 42 37 46 37  36941821B75AB7F7
    000020: 31 38 31 46 33 39 43 37 36 35 46 31 35 34 36 41  181F39C765F1546A
    000030: 43 31 35 37 38 36 36 32 36 30 35 37 35 41 32 44  C157866260575A2D
    000040: 41 30 30 30 30 32 30 30 30 31 36 30 35 41 36 32  A000020001605A62
    000050: 38 32 43 42 39 38 41 35 44 33 30 30 34 36 32 34  82CB98A5D3004624
    000060: 32 35 30 34 39 35 37 37 36 31 32 33 34 35 36 37  2504957761234567
    000070: 38 39 30 31 32 33 34 35 36 34 33 38 36 32 34 32  8901234564386242
    000080: 35 30 34 4e 36 31 32 33 34 46 46 46 46 46 46 46  504N61234FFFFFFF
    000090: 46                                                                             F


    2012-10-17 17:49:14,816: INFO - [XBExtCommPoint] TCPIP Hexdump at receive

    000000: 00 08 30 30 30 39 43 4c 32 34                    ..0009CL24


    The Message split-up is as follows;

    CmdCode => CK ( Verify DUKPT PIN IBM Method )

    BDK Encypted by LMK => 909E960536941821B75AB7F7181F39C7

    PVK Encrypted by LMK => 65F1546AC1578662 ( a Single Length One )

    KSN Descriptor => 605

    KSN => 75A2DA0000200016 ( My KSN Comprises of 75A2DA - BDK Id, 00002 - Device Id, 00016 - Counter )

    Source Pin Block => 05A6282CB98A5D30

    Check Length => 04

    Account Number => 624250495776 ( 12 Digits excluding check digit )

    Decimalization Table => 1234567890123456

    PIN Validation Data => 4386242504N6

    Pin Offset => 1234FFFFFFFF ( Padded with 'F's )

   
    As mentioned in the response message, I am getting error as "PIN is fewer than 4 or more than 12 digits in length"

    Since I am testing my application without PED, I am using the PIN Block generated by a DUKPT utility
                                        at     http://www.codemagus.com/WebTools/cgi-bin/cmldkgipek

    The Clear BDK is 75A2DA799E4361FBA7C479FE5225FB1F

    I created BDK as follows ( in console ),

    1. DD Command
             5EC7 3EF8 D680 5880 9D34 6BBF 29E0 EF45   ( Clear ZMK )

    2. DE Command
            A645 54F1 867F E2B8 3126 2DAC 8739 A0DB ( Encrypted ZMK )
            6FDF A94A ( Check Value )

    3. DG Command
        BDK Encrypted by ZMK : 67BE 7632 F7A0 856D E109 90A4 D89A BB5A
        BDK Encrypted by LMK : 909E 9605 3694 1821 B75A B7F7 181F 39C7


    Can you please help me to find out the reason for this error code 24?

    Please enlighten me on the concepts of KSN and KSN Descriptor.

    Awaiting for your replies.



------------------------------------

Re: Decrypted String After swiping the credit card with (IDTECH)swiper.

Victor Salaman — 2012-07-27T01:51:31

Wrong forum

On Jul 17, 2012, at 3:16 AM, sridhar wrote:




[Non-text portions of this message have been removed]



------------------------------------

Decrypted String After swiping the credit card with (IDTECH)swiper.

sridhar — 2012-07-17T07:16:15

Hi,

We are willing to do decryption of encrypted data which we get after swiping
the credit card with (IDTECH)swiper.
what you have ,it's only for EncryptedPIN that is it has been  taken the
encrypted PIN and PAN and gives us the decrypted PIN.

But After swiping the credit card , we got only the encrypted String.
Can you Please guide on this ,how to decrypt the String.


--
View this message in context: http://jpos.1045706.n5.nabble.com/Decrypted-String-After-swiping-the-credit-card-with-IDTECH-swiper-tp5709944.html
Sent from the jPOS - Dev mailing list archive at Nabble.com.


------------------------------------

Re: build jpos sources to jar files

Alejandro Revilla — 2012-05-30T20:41:09

mvn package

Please use jpos-users mailing list instead of this one, we have this one
just as an archive, but we are mostly active in the other one.

See http://jpos.org/resources

--
< at >apr <http://twitter.com/apr>



On Wed, May 30, 2012 at 4:04 AM, duong <mrdonduong-/E1597aS9LQAvxtiuMwx3w< at >public.gmane.org> wrote:



[Non-text portions of this message have been removed]



------------------------------------

build jpos sources to jar files

duong — 2012-05-30T07:04:46

hi all, i 've just download lastest version jpos 1.8.4
How can i build it to jar files.
Thanks



------------------------------------