Received: by 10.42.57.79 with SMTP id c15mr5693587ich.33.1349463550482; Fri, 05 Oct 2012 11:59:10 -0700 (PDT) X-BeenThere: android-security-discuss@googlegroups.com Received: by 10.50.87.137 with SMTP id ay9ls1506338igb.0.canary; Fri, 05 Oct 2012 11:59:03 -0700 (PDT) Received: by 10.43.58.194 with SMTP id wl2mr5349170icb.31.1349463543248; Fri, 05 Oct 2012 11:59:03 -0700 (PDT) Received: by 10.43.58.194 with SMTP id wl2mr5349169icb.31.1349463543237; Fri, 05 Oct 2012 11:59:03 -0700 (PDT) Return-Path: Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by gmr-mx.google.com with ESMTPS id i2si270413igl.1.2012.10.05.11.59.03 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Oct 2012 11:59:03 -0700 (PDT) Received-SPF: pass (google.com: domain of asm...@gmail.com designates 209.85.219.54 as permitted sender) client-ip=209.85.219.54; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of asm...@gmail.com designates 209.85.219.54 as permitted sender) smtp.mail=asm...@gmail.com; dkim=pass header...@gmail.com Received: by mail-oa0-f54.google.com with SMTP id n9so2785803oag.13 for ; Fri, 05 Oct 2012 11:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=LNS3w/wv6ZGkt/Aat6QXB5fPREa8H4yqrmmph3HrDmA=; b=QiNbuib5qirfHjhU38g9ellc2Y4gKnGLu1hQr0tY7IkHl8phdSCUXs86phM62kydnB V9XMHcx5Mcw6am/ZxsyxJ7LnjBjK0jup6zcpnLA+vry5wdxXsKKtiiRNWXk0j5tdn4NZ 1Xj2nZ2rfbnSVTaxQdLdhcYWopxLuNWAZXNyW8FaVyvjl7c+X6Ugh7Zf3yApcCTRf/cr zX8ZU+saA0H9Mhdm73SlIf4bhvcRhylWYLTO72Jj98aLHfQvyXjvl1Adm8n8nvKtGf6o lGvR84ycZezoskYfGxN1iBFxqb5Z78taZDJy6KkaLSpDuQgFRoQ3810INfCRmYUDv8Cq P/dg== Received: by 10.182.95.142 with SMTP id dk14mr7948274obb.2.1349463542965; Fri, 05 Oct 2012 11:59:02 -0700 (PDT) MIME-Version: 1.0 Sender: asm...@gmail.com Received: by 10.76.94.112 with HTTP; Fri, 5 Oct 2012 11:58:42 -0700 (PDT) From: Lucas Palma Date: Fri, 5 Oct 2012 15:58:42 -0300 Message-ID: Subject: Mobile Identification To: Android Security Discussions Content-Type: multipart/alternative; boundary=14dae93b5d2a1da45804cb5477ae --14dae93b5d2a1da45804cb5477ae Content-Type: text/plain; charset=ISO-8859-1 Hi everybody, There's some way to identify that the user is using a mobile device, not a desktop? Like, I have an application, which communicates with a web service, but anyone could access it through a desktop, and simulates that is using a mobile device. I don't think that "user-agents", "css" and things like that will help, since they can be forged. Someone know one or more ways to do the trick? There's some way to do it without changing the application? Thanks in advance! -- Lucas Palma *"If you are patient in one moment of anger, you will escape a hundred days of sorrow."* *- Chinese Proverb* --14dae93b5d2a1da45804cb5477ae Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi everybody,

There's some way to identify that the = user is using a mobile device, not a desktop?
Like, I have an app= lication, which communicates with a web service, but anyone could access it= through a desktop, and simulates that is using a mobile device.

I don't think that "user-agents", "c= ss" and things like that will help, since they can be forged.
Someone know one or more ways to do the trick?
There's some= way to do it without changing the application?

Thanks in advance!

--
Lucas Palma=



<= i>"If you are patient in one moment of anger, you will escape a hundre= d days of sorrow."
- Chinese Proverb

--14dae93b5d2a1da45804cb5477ae--