Nexon's Private/Public Key's

[spookyskunkk]

LOL CRACKED MY ASS OFF WHEN I RED THAT

I don't know how to explane it D: you cant just compile it right now and inject it..... @taylo123100

[FUKO]

LOL Thanks now i can convert it > HEEHE IMA HACK NEXON >DDD EVIL EVIL EVIL!! hehe thanks now i can make a knew thing and combine it with mine thanks ;Dchewheheheheheeh SSOOO HAPPY DANKE THANK YOU

Exactly what I was waiting for, the definition of a dumbass.

[Stevenom]

Of course. MD5 was never built for complete security - it had speed in mind. Of course, now, we have multi-core GPUs that can computer billions of hashes a second, so that's kind of... well... death for MD5 security.

That's also why so many security professionals are strongly advocating the use of bcrypt, a variable difficulty hashing algorithm to store passwords. Rather than a few billion hashes a second, we can change the workload for our bcrypt hash to take 10 times, 100 times or even 1,000,000 times more than MD5, meaning we can keep up with new and powerful hardware (that consequently would have otherwise made brute forcing hashes a lot easier if not for variable workload algorithms).

Multicore GPU?
Isn't GPU a graphic processing unit?

[freedompeace]

Multicore GPU?
Isn't GPU a graphic processing unit?

Yeah. A GPU, in commoner terms () is your graphics card. Your fine-tuned graphics card is more efficient at doin' its thing than your general-purpose CPU (think about it. specialise and be amazing at one, or do "well" at all). It's much faster, for example, doing work related to matrices, vectors, and funnily enough, hashes, a core part of cryptography these days. This means graphics cards can be many magnitudes faster than your CPU for some tasks.

Oh yeah, GPUs are multicore. Check out this wicked sick 2048 core GPU from NVIDIA!

@Boss

[Stevenom]

Yeah. A GPU, in commoner terms () is your graphics card. Your fine-tuned graphics card is more efficient at doin' its thing than your general-purpose CPU (think about it. specialise and be amazing at one, or do "well" at all). It's much faster, for example, doing work related to matrices, vectors, and funnily enough, hashes, a core part of cryptography these days. This means graphics cards can be many magnitudes faster than your CPU for some tasks.

Oh yeah, GPUs are multicore. Check out this wicked sick 2048 core GPU from NVIDIA!

@Boss

Yeah, I know there are dual core GPU's.
Just that I didn't think that'd got to do with what ever this is about.
There are some dual cards like GTX 590, 6990 HD and 5970 HD.
Some manufacturers make some other card dual core like ASUS's MARS GTX 285x2
Edit: Oops wrong type of card.
Edit2: Actually, I was right 2x GPU cards.
LOL

[freedompeace]

Yeah, I know there are dual core GPU's.
Just that I didn't think that'd got to do with what ever this is about.
There are some dual cards like GTX 590, 6990 HD and 5970 HD.
Some manufacturers make some other card dual core like ASUS's MARS GTX 285x2
Edit: Oops wrong type of card.
Edit2: Actually, I was right 2x GPU cards.
LOL

@Boss, you can also take multiple physical graphics cards and stick them in the same computer so that they run in parallel, delivering twice the grunt. Imagine 10x 2048 core GPUs

*drools*

[Stevenom]

@Boss, you can also take multiple physical graphics cards and stick them in the same computer so that they run in parallel, delivering twice the grunt. Imagine 10x 2048 core GPUs

*drools*

That's crossfire/sli.
But it's not like that.
1 card = 16x
2 card = 8x8
3 card = 16x8
4 card = 8x8x8x8

[freedompeace]

That's crossfire/sli.
But it's not like that.
1 card = 16x
2 card = 8x8
3 card = 16x8
4 card = 8x8x8x8

@Boss, I'm not quite understanding what you've just said up there. Are the x's supposed to be multipliers? And what do the numbers represent?

[Stevenom]

@Boss, I'm not quite understanding what you've just said up there. Are the x's supposed to be multipliers? And what do the numbers represent?

Yeah those X's are multipliers.
I forgot what the numbers are.
Go google it.
It was on a SLi/crossfire table.

[freedompeace]

Yeah those X's are multipliers.
I forgot what the numbers are.
Go google it.
It was on a SLi/crossfire table.

I'm not exactly sure why 1 card would be 16 times faster than 1 card(?).. But anywho, forgetting the actual numbers, two cards are faster than one (obviously). Take two beast 2048 core cards and stick them together, that's 4096 usable cores :3

Okay. This is off topic /:

ima go play some League

[Ghost8631]

Not trying to bump but if i recall correctly spidermanftw was working on this a long time ago.

[ThelightningBolt]

Ok so what you're saying is we make our own CA, get sued by Nexon and arrested great idea, just not for the arrest part. I like that you figured a way
to do a trendiness thing like this but really dude! Nexon will be ontop of our asses if MPGH did something like this. It would be the end of the site.

amm if we.... modified the ¨server¨more than 60% they can demand us

[se7enthsin]

Nexon's public and private key's are one step closer to discovery.Here's a algorithm and some info.With these key's we can run are own lobby's/sign files the same way nexon does.ECDSA Param's are in there,im hoping to get a P.O.C going.....
.signature has problems, re-make with post SSLeay045.....SHA1

ENCRYPTED PRIVATE KEY...PRIVATE KEY.ANY PRIVATE KEY..................$...$.. $...........M...O......................@...`...
PEM part of OpenSSL 0.9.8k 25 Mar 2009..0123456789ABCDEF....C:\src\buildtools\branch es\voon\tmp4x2fne\externals\openssl-0.9.8k\crypto\pem\pem_lib.c.phrase is too short, needs to be at least %d chars..Enter PEM pass phrase:..Proc-Type: 4,...BAD-TYPE....MIC-ONLY....MIC-CLEAR...ENCRYPTED...DEK-Info: ..PKCS #7 SIGNED DATA.TRUSTED CERTIFICATE.X509 CERTIFICATE....-----END ...-----...-----BEGIN .strlen(objstr)+23+2*enc->iv_len+13 <= sizeof buf....enc->iv_len <= (int)sizeof(iv)..Proc-Type: .Expecting: .X509_CRL....crl.X509_CRL_INFO...revoked.nextUpdat e..lastUpdate..issuer..X509_REVOKED....extensions. .revocationDate..serialNumber

CERTIFICATE.RSA PRIVATE KEY.RSA PUBLIC KEY..PUBLIC KEY..DSA PRIVATE KEY.DSA PARAMETERS..EC PARAMETERS...EC PRIVATE KEY..DH PARAMETERS...
md4WithRSAEncryption....RSA-MD4.
aes-256-cfb.AES-256-CFB.aes-256-ofb.AES-256-OFB.aes-256-cbc.aes-256-ecb.AES-256-ECB.aes-192-cfb.AES-192-CFB.aes-192-ofb.AES-192-OFB.aes-192-cbc.AES-192-CBC.aes-192-ecb.AES-192-ECB.aes-128-cfb.AES-128-CFB.aes-128-ofb.AES-128-OFB.aes-128-cbc.aes-128-ecb.AES-128-ECB.Microsoft CSP Name..CSPName.ecdsa-with-SHA1.prime256v1..prime239v3..prime239v2..prime239v 1..prime192v3..prime192v2..prime192v1..id-ecPublicKey..characteristic-two-field....prime-field.ANSI X9.62..ansi-X9-62..X509v3 No Revocation Available..

CERTIFICATE.RSA PRIVATE KEY.RSA PUBLIC KEY..PUBLIC KEY..DSA PRIVATE KEY.DSA PARAMETERS..EC PARAMETERS...EC PRIVATE KEY..DH PARAMETERS...memory buffer...

PKEY_USAGE_PERIOD...T........œ,................... ...............œ,.........‰...........lëK..B).‰... ........`ëK..B).........Ä=L.............x=L.Not After: .Not Before: ....decipherOnly....Decipher Only...encipherOnly....Encipher Only...cRLSign.CRL Sign....keyCertSign.Certificate Sign....keyAgreement....Key Agreement...dataEncipherment....Data Encipherment...keyEncipherment.Key Encipherment....nonRepudiation..Non Repudiation.digitalSignature....Digital Signature...objCA...Object Signing CA...emailCA.S/MIME CA...sslCA...SSL CA..reserved....Unused..objsign.Object Signing..server..client..G


%s%02X..%*sKey Id: .%*sAlias: %s....%*sNo Rejected Uses.....%*sRejected Uses:.%*s...%*sNo Trusted Uses......%*sTrusted Uses:.%*s....<EMPTY>.....%*s.%*s<Not Supported>..%*s<Parse Error>....%*s%s...: %s....%*s%s:..Generator (hybrid):.Generator (uncompressed):...Generator (compressed):.%s %s%lu (%s0x%lx)..%s 0.... recommended-private-length: %d bits.....generator:..prime:..Diffie-Hellman-Parameters: (%d bit).....


PKCS7_ATTR_VERIFY...PKCS7_ATTR_SIGN.PKCS7_ATTRIBUT ES....PKCS7_DIGEST....md..PKCS7_ENCRYPT...PKCS7_SI GN_ENVELOPE.PKCS7_ENC_CONTENT...PKCS7_RECIP_INFO.. ..enc_key.key_enc_algor...PKCS7_ENVELOPE..enc_data ....recipientinfo...PKCS7_ISSUER_AND_SERIAL.serial ..PKCS7_SIGNER_INFO...unauth_attr.enc_digest..dige st_enc_alg..auth_attr...digest_alg..issuer_and_ser ial...PKCS7_SIGNED....signer_info.cert....contents ....md_algs.d.encrypted.d.digest....d.signed_and_e nveloped..d.enveloped.d.sign..d.data..d.other

DSA-Parameters: (%d bit)....coefficient:....exponent2:..exponent1:..pr ime2:.prime1:.privateExponent:....publicExponent:. Exponent:...modulus:....Modulus (%d bit):...Private-Key: (%d bit)...G: ...Q: ...P: ...pub: ...priv:...Seed:...Cofactor: ..Order: .B: ...A: ...Prime:..Polynomial:.Basis Type: %s..Field Type: %s..ASN1 OID: %s....ECDSA-Parameters: (%d bit)..X........=).................ðÉ,............. ............Œ........=).................ðÉ,....... ..................ì........=).................ðÉ,. àW,.....................

PKCS8_PRIV_KEY_INFO.pkey....pkeyalg.........

11>...ENUMERATED..REAL....EXTERNAL....OBJECT DESCRIPTOR...OBJECT..OCTET STRING....BIT STRING..INTEGER.BOOLEAN.EOC.%-18s...%2d %-15s...(unknown)...<ASN1 %d>...appl [ %d ].cont [ %d ].priv [ %d ] ....prim: ..cons: ..length is greater than %ld..Error in encoding...BAD ENUMERATED..BAD INTEGER.00..%02X....[HEX DUMP]:.:%d.Bad boolean.....:BAD OBJECT.d=%-2d hl=%ld l=inf ...d=%-2d hl=%ld l=%4ld ...%5ld:.... Public key OCSP hash: ..... Subject OCSP hash: .%02x%s... ... Signature Algorithm: ...Bad time value..%s %2d %02d:%02d:%02d %d%s.. GMT....X509v3 extensions...%12sUnknown Public Key:.....%12sEC Public Key:..%12sDSA Public Key:.....%12sRSA Public Key: (%d bit)....%12sUnable to load Public Key...%12sPublic Key Algorithm: .. Subject Public Key Info:.... Subject:%c... Not After : ... Not Before: .... Validity.... Issuer:%c...%8sSignature Algorithm: ....%02x%c...%12s%s. (Negative). %s%lu (%s0x%lx).... Serial Number:..%8sVersion: %lu (0x%lx)..... Data:...Certificate:....'()+,-./:=?.maxsize=....minsize=..............

Hope to be working with you some time in the near future. Keep up the good work.

[kaskore]

this is all scrambled how about organizing it so we can read it easier and understand it a little more clearly