fingerprinting

I have generated my SHA1 code from my keystore but when I try to create an OAuth client 2.0, Google game console is giving me the error: "Certificate fingerprint is invalid". Anyone knows why this happens? How do I fix this? I've contacted Google Play Developer Support about this issue (I've got a same problem). Here is their answer : Please ensure the key is set to 2048 bit and is valid for at least 25 years. I've tried it, but sadly my debug.keystore is still not getting accepted, maybe there will be some luck on your side. $ keytool -genkey -v -keystore debug.keystore -storepass android

I have found myself cornered, so here we go. Context I need to produce a fingerprint hash code for object diffing. Comparing the hashes of two sets of objects will need to tell me if there are identical objects with the same hash. The fingerprint hash must be platform-independent . So I went for MD5 hashing . I am working with a large Object model code base that is out of my control. All types that I will be passed for this fingerprinting can not be modified by me . I cannot add attribute or constructors or modify anything. That does not exclude that the types will change in the future. So any

Is there any way to distinguish a NTAG213 from a MF0ICU2 tag based on its UID, ATQA or SAK values? As I have to program the tags differently (PWD/PACK for NTAG213 or 3DES for MF0ICU2) there must be a way to call either one or another method. Unfortunately, the Android framework tells me that both tags are MifareUltralight with type TYPE_ULTRALIGHT_C . The ATQA ( 0x0044 ) and SAK ( 0x00 ) are identical, too. Other apps like NFC TagInfo by NXP can tell me the exact type of a tag, so I know that there must be some way. Once you know that the tag is an NXP tag (UID starts with 0x04), you would

I need to generate a unique string that will differ from machine to machine -- a "device fingerprint". What are... possible approaches for custom implementations? (I've got a few ideas, but I figure you guys probably have BETTER ones) existing solutions? (both commercial / non commercial are acceptable) Device fingerprinting is a complex topic if you want to cover the many edge cases (e.g. hardware upgrades, OS upgrades, etc.) and if you are worried about people expending energy to either forge a known-good device fingerprint (good meaning the fingerprint is known to you and receives some

I have generated my SHA1 code from my keystore but when I try to create an OAuth client 2.0, Google game console is giving me the error: "Certificate fingerprint is invalid". Anyone knows why this happens? How do I fix this? I've contacted Google Play Developer Support about this issue (I've got a same problem). Here is their answer : Please ensure the key is set to 2048 bit and is valid for at least 25 years. I've tried it, but sadly my debug.keystore is still not getting accepted, maybe there will be some luck on your side. $ keytool -genkey -v -keystore debug.keystore -storepass android