An alternative to hashing is to use and persist a secure random value.
You can use SecureRandom, if you seed it well, or you can use /dev/
random. I don't know the quality of the Android implementation of /dev/
random, but given its ancestry, I'd expect it to be reasonably strong.
You're not lookin
This is indeed a good idea.
Instead of PRODUCT, I would rather use MODEL + BRAND as a prefix to the
ANDROID_ID (before rehashing it to obtain an hex string with always the same
length such as SHA1).
2010/3/15 Wayne Wenthin
> If you use it while using items like android.os.Build.PRODUCT or someth
If you use it while using items like android.os.Build.PRODUCT or something
similar you should be able to create a unique ID. Of course with this is
the assumption that no manufacturer will duplicate.
On Mon, Mar 15, 2010 at 7:58 AM, Greg Donald wrote:
> On Mon, Mar 15, 2010 at 10:48 AM, Mark Mu
On Mon, Mar 15, 2010 at 10:48 AM, Mark Murphy wrote:
> ANDROID_ID is fine for casual use, but it's not exactly the Rock of
> Gibraltar, if you know what I mean.
I can't think of a scenario where I would ever need it "casually".
Either I need it or I don't.
--
Greg Donald
destiney.com | gregdon
I guess we'll have to use some hashing technique of many values like
explained on another thread, but I don't like this solution...
Thanks for the answer anyway.
2010/3/15 Mark Murphy
> Guillaume Perrot wrote:
> > In my job, I have to use a unique device ID that is not the IMEI or any
> > other
Guillaume Perrot wrote:
> In my job, I have to use a unique device ID that is not the IMEI or any
> other info provided by the TelephonyManager (for some privacy reasons)
> so I would like to rely on ANDROID_ID.
> But people I work for don't trust the ANDROID_ID because they don't know
> exactly wh
In my job, I have to use a unique device ID that is not the IMEI or any
other info provided by the TelephonyManager (for some privacy reasons) so I
would like to rely on ANDROID_ID.
But people I work for don't trust the ANDROID_ID because they don't know
exactly what it is and we don't have the gua
Too bad it is NOT documented. There was a long thread about this
recently and one poster even thought it had something to do with
connecting to the Market. Seems like some developers are looking for
workarounds for a viable unique ID. Probably most of this is due to
misunderstanding which is du
> > Is it related to
> > google apps ?
>
> Not that I am aware of.
I asked this question since we can read in the doc: "Identical to that
obtained by calling GoogleLoginService.getAndroidId();" which sounds
strange. Spoofing android_id could grant access to the Google account
of someone else ?
--
9 matches
Mail list logo
