blackberry compatibility

[jackspirou]

blackberry compatibility

[jackspirou]

@ronaldnavarro689 thanks for reporting this issue. A couple questions. Are you checking the fingerprint at https://clientjs.org or are you using the getCustomFingerprint method?

[ronaldnavarro689]

Jack,

First of all I want to say that you're doing an excellent job and your solution is amazing for fingerprinting. I'm using the website, only. I just discovered it but plan on integrating it as a custom plugin for zencart. If you could let me know y our email I could ask you a quote for this job?

[ronaldnavarro689]

getting back with an update : It doesn't generate an unlimited number of random fingerprints it generates about 4 and it switches between them.

[jackspirou]

@ronaldnavarro689 Thanks for the support :)

After extensive searching I found that the only way to test Blackberry locally is to use VMware Player on windows and run http://us.blackberry.com/sites/developers/resources/simulators.html. Unfortunately Blackberry is not support by SauceLabs which this project uses for testing.

Tomorrow i'll be able to get my hands on a windows machine with VMware Player and the Blackberry installed and try to debug what your seeing above. Im guessing one or two of the values we use to generate the fingerprint isn't consistent, which would explain your 4 different fingerprint results. You can find the data points we use here https://github.com/jackspirou/clientjs/blob/v1.0.0-rc.1/src/client.js#L52-L62.

[ronaldnavarro689]

Awesome, thank you for the update. I've also send you another email
regarding api and integration questions.

On Mon, Feb 1, 2016 at 9:38 PM, Jack Spirou [email protected]
wrote:

@ronaldnavarro689 https://github.com/ronaldnavarro689 Thanks for the
support :)

After extensive searching I found that the only way to test Blackberry
locally is to use VMware Player on windows and run
http://us.blackberry.com/sites/developers/resources/simulators.html.
Unfortunately Blackberry is not support by SauceLabs which this project
uses for testing.

Tomorrow i'll be able to get my hands on a windows machine with VMware
Player and the Blackberry installed and try to debug what your seeing
above. Im guessing one or two of the values we use to generate the
fingerprint isn't consistent, which would explain your 4 different
fingerprint results. You can find the data points we use here
https://github.com/jackspirou/clientjs/blob/v1.0.0-rc.1/src/client.js#L52-L62
.

—
Reply to this email directly or view it on GitHub
#45 (comment).

[jackspirou]

@ronaldnavarro689 i'm having a hard time reproducing this issue without a blackberry. The VM I am using is not having the same issue you described above. Are you testing on real devices?

[ronaldnavarro689]

Hello,

Yes, It's a blackberry classic device.
I also noted something else but this is not a bug, more of a functionality:
there is no fuzziness factor like some other systems of device
fingerprinting try to add. Meaning I changed a minor detail like time,
resolution or something like this and had a new device id.
In fraud prevention it would turn into a big problem as carders switch
these little details anyway so you can't exclude his device from ordering.

On Mon, Feb 8, 2016 at 3:24 PM, Jack Spirou [email protected]
wrote:

@ronaldnavarro689 https://github.com/ronaldnavarro689 i'm having a hard
time reproducing this issue without a blackberry. The VM I am using is not
having the same issue you described above. Are you testing on real devices?

[image: capture_blackberry_fingerprint 1]
https://cloud.githubusercontent.com/assets/5687406/12895495/6a1c1d8a-ce62-11e5-8a23-502763be7c5e.PNG

—
Reply to this email directly or view it on GitHub
#45 (comment).

[dsmontoya]

Fuzzy hashes will be included in the next version. Be part of the development on https://github.com/jackspirou/clientjs/tree/v1.0.0-rc.1.

[ronaldnavarro689]

Hello,

That is awesome, could you please consider taking my project for
implementation into a zen cart module? I already have the module but it's
made for siftscience and it just needs replacement with your own api that
you mentioned you'll create soon.
Thank you.

On Mon, Feb 8, 2016 at 5:10 PM, Daniel Montoya [email protected]
wrote:

Fuzzy hashes will be included in the next version. Be part of the
development on https://github.com/jackspirou/clientjs/tree/v1.0.0-rc.1.

—
Reply to this email directly or view it on GitHub
#45 (comment).