Database Info

Warning: Dom't download Skype yet!!! Read Here

Skype For Android Has Major Security Problems
Update 1: link is dead
Update 2: Wasn't transfer to new site

THANKS for the info man

xriderx66 said:
THANKS for the info man
Click to expand...
Click to collapse
You are welcome.

even in windows mobile version, skype has the send file feature.

otivaeey said:
even in windows mobile version, skype has the send file feature.
Click to expand...
Click to collapse
Hmmm?? Didn't know that.

Link is broken. Is the article anywhere else?

GrandAdmiral said:
Link is broken. Is the article anywhere else?
Click to expand...
Click to collapse
"Here is something is really hate to report, especially since so many people were excited about finally having Skype for the Thunderbolt including myself. If you've installed skype on your Thunderbolt, a flaw has been exposed that exposes your personal information. Thanks to AndroidPolice they have caught the flaw. The flaw would let this rogue app harvest details for the users phone such as their account balance, full name, date of birth, city/state/county, home phone, office phone, cell phone, email, webpage, bio and more. YIKES!
Skype is aware of this, and is said to be working on it. Of course we don't want anyone be to be taken advantage of so of course if you feel the need to uninstall until an update is pushed to secure your information. Be sure to check out the video to."
http://www.youtube.com/watch?v=An8SnCBj-gU&feature=player_embedded

HTC Peep Login Problems

This thread is to track my dealing with HTC and their service department over the current Twitter Tab (HTC Peep) outage. Please don't PM me about it, I'll just make fun of you for not reading and searching.
The current outage has NOTHING AT ALL to do with the Peep security updates published back in February. For information on the past update, please refer to this post.
I am reaching out to everyone who uses this application to bug the crap out of HTC until they fix this problem. Please read this post all the way through so you can contact them with a bit of information. I originally tried to ask about it as simply as possible, but only got an idiotic response. The communication log will be posted in the next post.
Basically, for anyone experiencing issues with Peep, simply read the post I linked to and the following post. This will give you enough information to be able to contact HTC and make some noise. If you do contact them, please use proper grammar and be respectful. Typing like a pissed off high school girl (no offense to pissed off high school girls) will get us no where.
A brief history of Peep outages​Since the very beginning of HTC Sense, most experienced users have known about Peep's security flaws and have either decided to live with it, figuring that it wasn't very important to them, or simply used another client for Twitter. The problem is that Peep was accessing the Twitter API through use of unencrypted HTTP headers which exposed your username and password to anyone who might be eavesdropping on the connection via cellular data IP or WiFi.
Twitter experienced some headlines last summer where several celebrity and high profile accounts were compromised due to lax security features. This caused them to begin shifting their API towards a more secure end. In doing this, they notified the developers of Twitter clients of this shift and to update their applications accordingly. HTC was one of the few who did not update their applications.
Late last year, HTC's Peep application experienced some outages. HTC, instead of repairing the problem, petitioned Twitter about the outage and, after several weeks, the functionality of Peep was restored through an exception made in Twitter's API. This was the easiest solution for HTC, but the worst solution for the customers, since it still left the user's data exposed to risk and was only a temporary solution.
Then, sometime in late January/early February, the members of Tadong blog released their security information to the general public after trying for months to get HTC to fix the security flaw in Peep as outlined above. Subsequent to the release of the information, HTC finally release the security updates for Peep that corrected half of the problem. The initial log in attempt now used OAuth to establish a secure connection over HTTPS on TCP port 443. This fixed the update Twitter rolled out shortly after where some users got the "Forbidden" errors when trying to use the tab. It did not fix the remainder of the session where Peep would request data from Twitter. The rest of the time, Peep requested data over unencrypted HTTP basic headers just as it always had. This, as most of you know, caused problems with the most recent update to Twitter's API.
Twitter rolled out an update again at the end of April that broke the Peep client again. The problem wasn't really Twitter, though. Twitter has now disallowed any new requests to access it through unencrypted channels. This, of course, blocks Peep again. The sad thing now is that this would not be a problem if HTC had simply fixed the problem last year during the first outage or even produced a secure client in the first place.
This brings us to the present. I have contacted HTC with all the information I could gather about this problem. The conversation is listed in the next post. I encourage everyone reading this to learn a bit here and contact HTC via their support page. Any serial number should work as long in the contact form as it matches the correct device. The only Rhodiums to receive the Sense update were the Euro and AT&T ones, as far as I know. Leos ship with it, and I'm sure there were other devices that got Sense updates as well, such as the Photon and Topaz. I'm not up to speed on the models of those devices that got Sense, though. If you contact them, please post in here your conversations. If you need help crafting a proper response to the HTC support techs, please PM me. I will try to assist as best I can.

Communication log
Log between myself and HTC reps, Douglas and Danielle.
Me said:
I have both a Tilt2 and a HD2. Both are using HTC Sense as the primary GUI. On both of them, the Twitter Tab (HTC Peep) no longer works. I put in the right username and password and it always tells me that it is the wrong username or password. I have done this multiple times, and am absolutely certain that I am typing it in correctly.
After searching around for a while, it appears that I am not the only one to have this problem. I also have the HTC Peep security update installed on both of the devices, but it does not work with or without that fix.
Is HTC planning to roll out an update to fix this problem?
Click to expand...
Click to collapse
HTC Douglas said:
understand you are unable to log in to Twitter even with the Peep security update. The link you need to download the update for is different for your two devices.
Use this first link for your Touch Pro 2:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1085&news_id=874
And this link for your HD2:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1086&news_id=865
If this does not work you may need to restore your devices to factory settings and re-apply the appropriate hotfix after backing up your information, for example with ActiveSync or the Windows Mobile Device Center to sync your information with Outlook.
Sync software is available at: http://www.microsoft.com/windowsphone/en-us/apps/65-downloads.aspx
You can back up your information using ActiveSync or the Windows Mobile Device Center located at the following URL:
http://www.microsoft.com/windowsphone/en-us/apps/65-downloads.aspx
Essentially, plug your phone into the PC after installing the software and select Activesync as your connection type. Your computer will walk you through backing up your data.
A factory data reset will clear all data from the phone's internal memory and restore the device to manufacturer defaults. Information on your storage card will be kept. To reset the phone press start>settings>(menu>all settings)>system>clear data and confirm.
Click to expand...
Click to collapse
Me said:
I just mentioned that I installed the security update already, and the response I got was to install the security update? What kind of answer is that? Even if the line of thinking was that I perhaps installed the wrong update, how would that even be possible considering the updates require the installation to pass software version checks before installing? I was trying to make this as simple as possible, but considering the response I received, it is apparent I will be unable to do this.
The problem is that the Peep Security Update did not fix the problem all the way. Originally, the Twitter account information was sent via unencrypted http headers upon login which reveal both the username and password to anyone who happens to be eavesdropping on the connection, whether it is by cellular data or wifi. Also, when sending tweets or receiving them, their is a continuous authenticate request sent which exposes the username and password again in the same manner.
The security update is not a 100% fix. After installing the update, it seems that while the initial session is now being sent over https using TCP port 443 (sending against the api.twitter.com domain), during the rest of the session, Peep switches back to HTTP basic. This still leaves the whole session after the initial login vulnerable to hijacking based on the Twitter's session ID through cookies. Because this was not fixed properly in the first place, Twitter has blocked the application from accessing its api. Twitter has increased its security measures and disallowed new authenticate requests from unsecured clients. So any device that is currently authenticated in Peep will not be affected, but once the user logs out of Twitter, does a hard reset, or a ROM upgrade, the Oauth token will be invalidated or removed and will not allow Peep to log back in.
This is the position I am currently in, along with hundreds other users. It affects every user on HTC Sense as it will break the Peep client as soon as they log out. Since these devices are still being sold as brand new, HTC should still be providing support for them, since it is the HTC software that is not functioning as intended. Now, what is HTC prepared to do for every single Sense user? All that needs to be done is to FINALLY secure the Peep client and force it to use HTTPS instead of basic HTTP. The Twitter api will refuse all new auth requests that are unencrypted.
I have attached an eavesdrop of the timeline update request that is sent when the client refreshes. Notice that the username and password are UNENCRYPTED and shown in plain text. One more time I will ask what HTC is prepared to do to solve this problem. Please don't give me a cookie cutter response again. Thank you for your time.
Click to expand...
Click to collapse
The previously mentioned log is attached to this post.
HTC Douglas said:
Thank you for your reply. If you have performed the security update after performing a factory data reset please let me know and I can escalate this issue within HTC.
These are standard troubleshooting steps required to identify an issue and would be required before Escalations can review the case. I appreciate the additional data and log you included, as well.
Also so that I can escalate this issue, please reply with the following information:
Mobile device number:
Alternate contact number
Time zone:
Preferred contact time:
Current ROM version: (Start>Settings>about phone>software information on the HD2)
Click to expand...
Click to collapse
Me said:
As I mentioned, this is problem is persistent through hard resets and ROM updates. Anytime you log out or clear the Peep auth token in any way, it will not allow any further logins due to the (lack of) security of Peep. The only way around this currently is to back up the registry data associated with the Peep client in [HKLM\Software\HTC\HTCAccountManager] as well as the entire folder [\Temp\TwitEng]. If these are imported into a new flash of a ROM update or after a hard reset, the client will function again, as no new initial auth request will be needed. This still does not fix the problem of the client exposing usernames and passwords during EVERY update attempt. Nor does it allow less savvy users to use the Tab after having to hard reset or update the ROM.
The Tilt 2 is running ROM version 2.10.502.4.
The HD2 is running ROM version 3.14.531.1.
You may contact me via e-mail (email removed). I prefer not to be called.
Click to expand...
Click to collapse
HTC Douglas said:
Thank you for your reply. I have escalated the issue for further review. An escalations agent will reach out to you soon. Escalations contacts are performed in the order they are received so it may take a few days for us to review this information and get in touch with you.
Thank you for the detailed information about your analysis.
Click to expand...
Click to collapse
HTC Danielle said:
The previous agent has forwarded your email request to the next level for further review. The escalations team will be getting back with you as soon as they have any information for you. I hope you have a safe holiday weekend.
If you need any further assistance, you are welcome to send another inquiry through the HTC website by going through the Support page (http://www.htc.com/us/support) then tapping ‘send us an email’. You should input all the necessary information requested on the page.
Click to expand...
Click to collapse
Me said:
I will be awaiting further reply. Thank you for your attention to this matter.
Click to expand...
Click to collapse
HTC Travis said:
Thank you for provding us information about the shortcomings of our PEEP security update. I have verified that you are correct and have alerted our corporate office of this fact. They are researching the root cause in terms of the programming and will look into providing an update.
Click to expand...
Click to collapse
Me said:
This is great news. I'm having trouble seeing that I'm the first person to bring this to HTC's attention, though, seeing as this has been an issue for right about a month now. I figured someone else would have reported the problem before me. Please do keep me informed as this progresses. It should be as simple as forcing Peep to use secure HTTPS over TCP port 443 during the session as it does during the login procedure that was updated in February. Currently, it uses OAuth over HTTPS to establish the initial login, but switches back to HTTP basic for the remainder of the session. This allows the username and password to be seen in plain text every time the application requests an update from the Twitter API. Using this method also has another side effect. Twitter updated its security measures to disallow unencrypted requests. This means that Peep is no longer able to establish a connection since it moves from OAuth over HTTPS to HTTP basic during the initial session. If I can be of any other assistance, please let me know. I look forward to updates in this matter.
Click to expand...
Click to collapse
HTC Travis said:
You are not the first person to tell us they are having a problem with Twitter. You are the first person to provide us with this level of information and we thank you for that. Please reply to this email in a few days and someone should be able to give you more information.
Click to expand...
Click to collapse
Me said:
I see. I'm just doing what I can to benefit the dwindling Windows Mobile community. I will check back later this week. Thank you for the updated information.
Click to expand...
Click to collapse

Retain Twitter Tab/Peep functionality through a flash or hard reset
Before you ask, I don't have first hand experience with this. This is based on successful attempts by other members of the community.
This only works if the Twitter Tab/Peep currently still work for you. If it doesn't, then you are out of luck, and this will not work for you.​
To retain the functionality of the Peep client through a flash of a new ROM or a hard reset, you will need to follow the steps listed below.
1. Stop Sense and soft reset to make sure that Sense doesn't continue altering information while you are backing up data.
2. Back up the entire key of "HKLM\Software\HTC\HTCAccountManager." You really only need the Twitter strings, but it's easier to just back up the whole thing.
3. Backup the entire folder of \Temp\TwitEng. This is where the Twitter authentication token is stored.
4. Flash the new ROM or hard reset, whichever you need to do.
5. Once the new ROM is stable and working, stop Sense and soft reset.
6. Restore the registry key and backed up directory.
7. Soft reset and then enable Sense. The Twitter tab should now continue working for you without any trouble.
EDIT: JVH3 made a pair of posts about this HERE and HERE. The second one talks about authenticating another device with the backed up data.

Great initiative ! I'm very curious to hear about HTC's reception of the issue, and see if they will take the initiative to fix it...or imagine a way to justify how not doing it

majorasshole said:
Great initiative ! I'm very curious to hear about HTC's reception of the issue, and see if they will take the initiative to fix it...or imagine a way to justify how not doing it
Click to expand...
Click to collapse
Please use this thread to contact HTC about the problem. Please don't link them to this thread, though. I started this with the intention that others would use the information I have gathered on the issue to contact HTC in an informed manner to get it resolved.
Basically, the more noise is made on this issue, the better chance there will be to have it fixed.

HOLY $ |-| 1 +, it worked!
Ok, so I received official word that Peep is being looked into by HTC. I would still encourage anyone reading this to contact them with the information I have provided here. The squeaky wheel gets the grease, as they say.
HTC Travis said:
Thank you for provding us information about the shortcomings of our PEEP security update. I have verified that you are correct and have alerted our corporate office of this fact. They are researching the root cause in terms of the programming and will look into providing an update.
Click to expand...
Click to collapse
Me said:
This is great news. I'm having trouble seeing that I'm the first person to bring this to HTC's attention, though, seeing as this has been an issue for right about a month now. I figured someone else would have reported the problem before me. Please do keep me informed as this progresses. It should be as simple as forcing Peep to use secure HTTPS over TCP port 443 during the session as it does during the login procedure that was updated in February. Currently, it uses OAuth over HTTPS to establish the initial login, but switches back to HTTP basic for the remainder of the session. This allows the username and password to be seen in plain text every time the application requests an update from the Twitter API. Using this method also has another side effect. Twitter updated its security measures to disallow unencrypted requests. This means that Peep is no longer able to establish a connection since it moves from OAuth over HTTPS to HTTP basic during the initial session. If I can be of any other assistance, please let me know. I look forward to updates in this matter.
Click to expand...
Click to collapse
HTC Travis said:
You are not the first person to tell us they are having a problem with Twitter. You are the first person to provide us with this level of information and we thank you for that. Please reply to this email in a few days and someone should be able to give you more information.
Click to expand...
Click to collapse
Me said:
I see. I'm just doing what I can to benefit the dwindling Windows Mobile community. I will check back later this week. Thank you for the updated information.
Click to expand...
Click to collapse

cajunflavoredbob said:
Before you ask, I don't have first hand experience with this. This is based on successful attempts by other members of the community.
This only works if the Twitter Tab/Peep currently still work for you. If it doesn't, then you are out of luck, and this will not work for you.​
To retain the functionality of the Peep client through a flash of a new ROM or a hard reset, you will need to follow the steps listed below.
1. Stop Sense and soft reset to make sure that Sense doesn't continue altering information while you are backing up data.
2. Back up the entire key of "HKLM\Software\HTC\HTCAccountManager." You really only need the Twitter strings, but it's easier to just back up the whole thing.
3. Backup the entire folder of \Temp\TwitEng. This is where the Twitter authentication token is stored.
4. Flash the new ROM or hard reset, whichever you need to do.
5. Once the new ROM is stable and working, stop Sense and soft reset.
6. Restore the registry key and backed up directory.
7. Soft reset and then enable Sense. The Twitter tab should now continue working for you without any trouble.
Click to expand...
Click to collapse
Looks alot like what I posted here: http://forum.xda-developers.com/showpost.php?p=13790743&postcount=34951
Your thread is a better place for it though.
I also posted this: http://forum.xda-developers.com/showpost.php?p=13520319&postcount=34836
Which is helpful if you have another device that still is authenticated with the Twitter tab and transfering the info to another device.
Real glad you got things going with HTC to finally work on this.

JVH3 said:
Looks alot like what I posted here: http://forum.xda-developers.com/showpost.php?p=13790743&postcount=34951
Your thread is a better place for it though.
I also posted this: http://forum.xda-developers.com/showpost.php?p=13520319&postcount=34836
Which is helpful if you have another device that still is authenticated with the Twitter tab and transfering the info to another device.
Real glad you got things going with HTC to finally work on this.
Click to expand...
Click to collapse
Well, I already knew the key and file that needed to back up, but I forgot where I saw the bit about turning on and off Sense. Thanks. I'll add some credit for you.
Yea, there's a bit more that I can't post due to personal or sensitive information, but it's looking good so far. I'll keep updating this as more info rolls in. I'm hoping that other people contact them about it as well.

Very good afford cajunflavoredbob .
Lets hope Peep developer team in HTC are getting ready with new client
Thanks.

prabhat said:
Very good afford cajunflavoredbob .
Lets hope Peep developer team in HTC are getting ready with new client
Thanks.
Click to expand...
Click to collapse
I have a bit more to update tonight. They have sent the information onward and are working on a fix right now. No ETA was given, however.

Ive just suffered this problem today - logged out of peep and now i cant get back in again. As i didnt know about this issue, obviously dont have any backup! Thanks for pursuing this!

This has been my ongoing encounter with HTC Support for the Touch HD / Blackstone
Simon Lee Reply
Ok, could you keep me notifed if the touch HD will get the update or not ?
Thanks 2011/06/08 18:04:45
Bjorn [EU team] Close Pending I'm not saying it won't happen, I'm just saying that at this point I can not guarantee taht the touch HD will get such an update as it is an older device. I'm not saying it won't happen, I'm just saying that at this point I can not guarantee taht the touch HD will get such an update as it is an older device. 2011/06/08 16:15:10
--
Simon Lee Reply How come thou ? If theres no fix then that might meen i will have to buy a new phone, and am quite happy with the Touch HD ?
--
2011/06/08 10:57:55 Bjorn
[EU team] Close Pending I can not guarantee That a fix will be released for the Touch HD when te issue is resolved. I can not guarantee That a fix will be released for the Touch HD when te issue is resolved.
--
2011/06/08 07:59:10 Simon Lee Reply
Yeah, i realise its an Unoffical ROM, but thats beside the point, When tyou fix the HTC peep, will the Touch HD get a Upgrade for 6.1 with the HTC Peep fix?
--
2011/06/07 17:15:23 Bjorn [EU team]
Close Pending As your device is runnig an unaproved ROM we are unable to support it and can not guarantee that any applications will work properly. We have how ever had reports regarding this and are looking in to it on our approved ROM's, As your device is runnig an unaproved ROM we are unable to support it and can not guarantee that any applications will work properly. We have how ever had reports regarding this and are looking in to it on our approved ROM's,
--
2011/06/07 16:14:50

spikeyl said:
Ive just suffered this problem today - logged out of peep and now i cant get back in again. As i didnt know about this issue, obviously dont have any backup! Thanks for pursuing this!
Click to expand...
Click to collapse
Theres some kind of solution floating around here somewere
- Edit -
you could try this: http://forum.xda-developers.com/showthread.php?t=708770

Thanks - i found this earlier and tried all these but none of them work! Having read through the thread above I can see why though - it is related to the security authentication issue, so currently no fix.

spikeyl said:
Thanks - i found this earlier and tried all these but none of them work! Having read through the thread above I can see why though - it is related to the security authentication issue, so currently no fix.
Click to expand...
Click to collapse
Yeah, and HTC are planning on bring out a fix, but wont say which devices, will get the supported fix,

Simon_WM said:
Yeah, and HTC are planning on bring out a fix, but wont say which devices, will get the supported fix,
Click to expand...
Click to collapse
The only devices that will get the fix are the ones that have official Sense 2.5 ROMs. There are only four of them.
1. Leo
2. Rhodium
3. Photon
4. Topaz
My recent communications with HTC contain personal information regarding the fix. It is being worked on, but there is no current ETA that they have provided. I am keeping in touch with them and working with HTC to resolve the problem. I'll update this thread as more information is provided to me.
EDIT: Please don't post here about possible fixes. There is no fix for this error. The problem is with Peep and has nothing to do with Twitter. Logging in and out of Twitter on the desktop will have no bearing on the Peep application. No applications are allowed to access Twitter's API though unsecured connections, thus Peep is excluded.

My Twitter also stopped working sometime last week, but I don't ever remember logging out. However when I scrolled past the peep tab on my HD2 this morning it read "no tweets" instead of the click to login screen (or whatever it said). I clicked the screen and now have tweets going back to sometime yesterday. Is this any way connected?

jools5431 said:
My Twitter also stopped working sometime last week, but I don't ever remember logging out. However when I scrolled past the peep tab on my HD2 this morning it read "no tweets" instead of the click to login screen (or whatever it said). I clicked the screen and now have tweets going back to sometime yesterday. Is this any way connected?
Click to expand...
Click to collapse
This is unrelated if you did not log out, as far as we know. Twitter isn't yet blocking anyone from their API who already has a connection. They are only refusing new attempts.

HTC knows the problem, is working on it, but still no ETA
Just to add my story:
Originally Posted by Me
After flashing a new row to my HTC HD Mini, HTC Peep cannot sync with Twitter anymore.
I have flashed this rom: http://www.htc.com/europe/SupportDownload.aspx?p_id=314&cat=2&dl_id=980
And updated it with this update: http://www.htc.com/europe/SupportDownload.aspx?p_id=314&cat=0&dl_id=1085
When I enter my account and password, HTC Peep tells me: "You entered an incorrect username or password".
The account and password are OK, since I can use them via the web and other Twitter-applications.
I tried revoking HTC Peep as a Twitter-application and then re-adding HTC Peep.
But the message is still "You entered an incorrect username or password".
From an old backup I have retrieved registry settings at HKLM\Software\HTC\HTCAccountManager and the directory at \Temp\TwitEng.
After putting these settings back into the new rom I get a message: "The account was forbidden to access the twitter server!"
This is logically because I revoked HTC Peep as a Twitter-application at the Twitter website.
So, the HTC Peep client does not recreate the connection to Twitter.
Please provide a solution or update so that the HTC Peep client will work again.
Click to expand...
Click to collapse
Originally Posted by HTC
Thank you for contacting HTC Support.
The problems you are experiencing is because of a change in the Twitter API's that Peep has not yet adapted to.
Unfortunately I have no ETA for when this might be.
Until then I can only recommend using another Twitter client.
I hope this helps.
Click to expand...
Click to collapse
Originally Posted by Me
Thank you for the answer.
I am already using another Twitter client, but miss Peep...
I sincerely hope that Peep will be adapted soon.
Is this problem (already) sent to the development department?
Click to expand...
Click to collapse
Originally Posted by HTC Thank you for your email.
Yes, HTC is working on solving this issue as soon as possible.
If you have any further queries please don't hesitate to contact HTC again.
Have a nice weekend.
Click to expand...
Click to collapse
So, HTC knows the problem, is working on it. But still no ETA.....

wensing said:
Just to add my story:
So, HTC knows the problem, is working on it. But still no ETA.....
Click to expand...
Click to collapse
It's good to hear someone else's experience. I will ry to get back in touch with the HTC rep I've been communicating with this evening or tomorrow to see if there are any updates.

WhatsApp Sniffer issue

Hi guys,
I downloaded WhatsApp Sniffer in my HTC Desire, it seems to be working but can't capture any conversation. In short, when I start the app, I can only see the following message:
"There isnn't any conversations yet, wait until one has been captured. Make sure WhatsAppSniffer is listening and if you are on a WPA/WPA2 network, check that the ARP_Spoof is activated."
I've tried the app in both WEP and WPA/WPA2 networks but no luck. My phone is rooted with:
Android version: 2.3.7
Mod Version: CyanogenMod-7-11162011-NIGHTLY-Desire
WhatsApp Messenger: 2.7.8509
Any clues what might be the reason?
Thx,
Sotiris.

I thought Whats App was now fixed so that it did not send plain text.

Hmm, I am not aware of it. But it makes sense... Thx for your reply.

if your network is secured with Wpa or wpa2
the chat will not be captured
to capture chat the network must be protected with wep
or it need to be unsecured

Pl provide link to download

alinawaz said:
Pl provide link to download
Click to expand...
Click to collapse
can someone send me (PM me) a working link to whatsapp sniffer, please?!

https://docs.google.com/open?id=0B_PzeJyBdcp3UW5GOVZlOTZKYVU - google drive link cause i dont use any other servers

pransh said:
https://docs.google.com/open?id=0B_PzeJyBdcp3UW5GOVZlOTZKYVU - google drive link cause i dont use any other servers
Click to expand...
Click to collapse
thank you!

Hello all am new @ this site, awesome site... am using whatsapp sniffer or @ least am trying too...
my issue is that @ times it says that ( my devise seem not to be rooted ), I have rooted phone i do have the superuser icon... samsung GS3
and i restart the app, and it runs ok, but it don't capture anything... am i doing something wrong??? i do see that it will not
capture anything in wap or wap2...
any help will be appreciated

bumping because it seems that this app doesnt work (anymore)
anyone confirming?

Hi.
I'm also wondering the same thing. Just went through the fairly painful process of downgrading my HTC Desire Z Gingerbread to Froyo in order to then gain root, specifically so that I could use WhatsAppSniffer.
The app seems to have installed correctly, it's running fine, the other apps like SuperUser and BusyBox have no problems. I've run the sniffer for several hours on my shared WPA network at home, and for a couple of hours on a shared Open network last night with no results. It could very easily be the case that there were no conversations to capture, but the other possibility is that WhatsApp have fixed the vulnerability. I'm going to keep trying for a couple more days, and on one more network connection. Will confirm if whether or not I get anything here.

Just reading a couple of open-source articles it seems that WhatsApp pushed release 2.8.3 to iPhones on 27th August 2012, and a similar release to Androids around the same time. This release included (relatively poor) encryption. Anyone who has downloaded the update will now be protected from WhatsAppSniffer. Seems that sniffing is still possible if you can fathom this: ezioamodio.it/?p=29. It's beyond me though. #noob

I tried yesterday found on web the versione 1.03 donate root,
also for myself it seems doens't work,
the spoof says that if I'm scanning a WPA/WPA2 network I have to activated the ARP Spoof, otherwise for WEP it doens't need.
But I supposed it worked in one of the two cases, instead the app continue to search but see nothing.
I tried to send a whatsapp message connecting to the same network that sniffer is connecting too, and it see even not my message.
Is it an older version that doesn't work or maybe it needs a rooted phone and mine one is not?
THANKS

pransh said:
https://docs.google.com/open?id=0B_PzeJyBdcp3UW5GOVZlOTZKYVU - google drive link cause i dont use any other servers
Click to expand...
Click to collapse
Google removed it, can you give another link?

FardeenTGO said:
Google removed it, can you give another link?[/QU
same here too
Click to expand...
Click to collapse

Links, Email Addresses cannot be tapped (clicked) from messages ??

Everyone is happy that HTC provided ICS update. Did anyone notice that email addresses, links are detected in a message but they cannot be tapped (clicked) ? I upgraded using EU WWE RUU. I wanted to know how widespread this issue is. In GB, we could tap on links and web browser used to open. Now that doesn't happen. This isn't limited to messages application. Whatsapp and other apps have this issue.
Is there an updating coming to fix this or is it an attempt to avoid Apple's lawsuit ?? I read recently that Apple was going to launch a lawsuit because of this. If the latter is the case, what is the workaround for this ?
Can someone put light on this ?

prince87 said:
Everyone is happy that HTC provided ICS update. Did anyone notice that email addresses, links are detected in a message but they cannot be tapped (clicked) ? I upgraded using EU WWE RUU. I wanted to know how widespread this issue is. In GB, we could tap on links and web browser used to open. Now that doesn't happen. This isn't limited to messages application. Whatsapp and other apps have this issue.
Is there an updating coming to fix this or is it an attempt to avoid Apple's lawsuit ?? I read recently that Apple was going to launch a lawsuit because of this. If the latter is the case, what is the workaround for this ?
Can someone put light on this ?
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/showthread.php?t=1865756

Every time I install a new rom or do a factory reset it looks like I've been hacked

As the title say time I install a new rom or do a factory reset it looks like I've been hacked. As soon as I register and connect my phone to the internet google security activity shows that my phone has been connected from Irland or Germany although I'm connecting from Sweden. How can this be explained if I'm not being hacked? I take all the security measures, changing password etc... But yet this problem doesn't go away. Does this happen to anyone else?

give us more detail
did happen only with one device or more? what do u use for root, wich rom, custom recovery do u install? wich kind of gapps do u use? it happen just when u install the rom/recovery, or when u set up the gapps?
the foreign connection message is inside the gmail account? do u see foreign ip address logged when u are not logged or just foreign ip when u are logged? (this question is because maybe something use a vpn)

I use Viperone rom, but it does't matter what rom I use. As soon as i logg in to my google account it happens, on the google security activity where I can see my devices, it shows that I logged in from Irland or Germany, and after that it goes back to show that I logged in from Sweden. So far I noticed that it only happens on my phone, but in the past it use to happen on my PC too, and it does not show the ip address, it only shows the name of the country. This is how it looks like: http://imgur.com/2A9ZBJy Tyskland is Germany in Swedish and it's not supposed to be there with Irland.

Keomas said:
I use Viperone rom, but it does't matter what rom I use. As soon as i logg in to my google account it happens, on the google security activity where I can see my devices, it shows that I logged in from Irland or Germany, and after that it goes back to show that I logged in from Sweden. So far I noticed that it only happens on my phone, but in the past it use to happen on my PC too, and it does not show the ip address, it only shows the name of the country. This is how it looks like: http://imgur.com/2A9ZBJy Tyskland is Germany in Swedish and it's not supposed to be there with Irland.
Click to expand...
Click to collapse
when u install rom and configure gapps r u using your wifi? because is strange it happens also with your pc, maybe the problem is in your LAN, it happens just after the gapps setup after a fresh install or also later?
do u ose official gapps (and where is the source) or do u use other kind of gapps?

The roms that I use has allready Google apps installed. This time it happened right after I logged in to my phone. In the past it happened a day later.

It's possible that the new rom had it's location history set to those locations.. And Google apps like a good little app is telling where your are...
But it's wrong until it gets a proper location update.

nutpants said:
It's possible that the new rom had it's location history set to those locations.. And Google apps like a good little app is telling where your are...
But it's wrong until it gets a proper location update.
Click to expand...
Click to collapse
No. This happens when i change the password. I changed the password before i installed the new rom.

Google
Yeah sure.google needs update location.

sichuv11 said:
Yeah sure.google needs update location.
Click to expand...
Click to collapse
Nope. I'm definitely being hacked. Everything points towards it. I change my password I format my PC I install the original android to my phone, same **** happens. It was not like this before.
There is a trojan that can not be found by virus, malware and trojan software. This bastard got me. I think it could be the government.

Now it looks like this,I got USA instead of Germay http://imgur.com/uYDxZ1j Am i being hacked or not? 6th februari is the day i changed my password, compare it with the first picture i posted.

make 2 new google account with your pc
wipe your phone and install a rom, than configure it with one new account
use it for a day
than with your pc go in both account and see if are both comprimised or not

Let's assume the worst thing, that I am being hacked. How can I stop this from happening? I already changed password (I'm doing that from time to time), I use 2 step verification and sms verification when I login to my Gmail and I got virus, malware and firewall softwares, what else can I do? How am I being hacked?

Keomas said:
Let's assume the worst thing, that I am being hacked. How can I stop this from happening? I already changed password (I'm doing that from time to time), I use 2 step verification and sms verification when I login to my Gmail and I got virus, malware and firewall softwares, what else can I do? How am I being hacked?
Click to expand...
Click to collapse
if u want help you should try to do what we say and report it

niubboxp said:
if u want help you should try to do what we say and report it
Click to expand...
Click to collapse
Your just asking questions, I don't think you have answers.

Keomas said:
Your just asking questions, I don't think you have answers.
Click to expand...
Click to collapse
and you will never know

niubboxp said:
and you will never know
Click to expand...
Click to collapse
Maybe not on this forum, but there are other forums.

What rom are you using? Where did you get it?
What email app are you using?
Who is your internet provider for your device?
All of these can be factors in you being hacked...
Your rom could have a Trojan on it.
Your email could be not properly storing your password.
(Your not using the factory email app that uses the account your signed info your phone with are you? Please say no)
Is your internet provider known for making a federal case out of every request for information or do they give it out to anyone with a badge?
More information is needed before you can be helped.
First off change roms...
If you are using a oem rom get a custom rom from a popular developer.
Then change email providers
(Unless you are taking Google)
Then dump the two factor crap
Get a third party open source email app or use tor to sign in by web mail.
Change and set your password from a cafe or hotel Wi-Fi that is nowhere where you usually go.
Then see if you think you are being hacked..
If so trash the phone
Get a new one with cash..
Root it secure it
Try again
And if that still looks bad..
User paper and one time pads for encryption and safe drop points.