So...I've had it stored on my PC for several months now. However, I come into work today, and apparently Symantec now believes it's a virus. Has anyone else seen this happen recently?
Scan type: Scheduled Scan
Event: Security Risk Found!
Security risk detected: Trojan.Gen.2
File: d:\Android\RootMyX2\rageagainstthecage-arm5.bin
Location: Quarantine
Computer: SOL5001243-1D
User: SYSTEM
Action taken: Quarantine succeeded
Date found: Monday, April 25, 2011 8:41:49 PM
Yep, same here. Just hit today.
I'm guessing that Symantec updated their definition and got a false positive (but it would be comforting to have someone confirm that)
Related
I've setup a couple of Hermes handsets this past week, one on Cingular (US) and one on Vodafone (UK).
Our Exchange server is hosted in the UK.
I have a problem whereby the password you are forced to set when setting up the push/sync is prompting the user for entry almost every 5 minutes (ie. when the phone requires interaction from 'power save mode')
Entering the password 'settings' screen is no use as the option to change the 5 minute period is greyed out.
Is there a fix to this? Is this handset related or server related?
Surely I'm not alone with this problem?
Hermes (WM5) (1x Cingular US, 1x Vodafone UK)
Vini said:
I've setup a couple of Hermes handsets this past week, one on Cingular (US) and one on Vodafone (UK).
Our Exchange server is hosted in the UK.
I have a problem whereby the password you are forced to set when setting up the push/sync is prompting the user for entry almost every 5 minutes (ie. when the phone requires interaction from 'power save mode')
Entering the password 'settings' screen is no use as the option to change the 5 minute period is greyed out.
Is there a fix to this? Is this handset related or server related?
Surely I'm not alone with this problem?
Hermes (WM5) (1x Cingular US, 1x Vodafone UK)
Click to expand...
Click to collapse
This is server related. Technically you do not need a fix because everything is working as intended. What's happening is the exchange admin is enforcing a security certificate on your phone with the idea being that if you lose your phone, strangers cannot access your data. Further more they can trigger a remote wipe of your device after a set number of failed password attempts. This is pretty much standard in any corporation as they don't want outsiders getting access to their information. That being said there are ways to get around it. Just bear in mind that if you lose your phone, whoever picks it up will have full access to it and all information it contains. If you're willing to accept the potential implications then it's very simple. Google "zenyee.com stay unlock" and read through that thread on Mobility Today. There's a cab on the second page you need to install that will "un-grey" that box so you can set it to something more reasonable, like 24 hours.
Excellent, thanks for the info!
Is there anyway the server can be changed to avoid having to install this Zenyee.com Stay Unlock.zip on each unit?
Yes the exchange server administrator can change the certificate requirements (password requirements as well as idle time requirement).
I am the admin, any idea where this option is?
Very oddly I still see the screen attached below on Android 4.3 (stock, rooted, on a Galaxy Nexus).
What could this mean?
Bluebox Security Scanner is a fake and always shows vulnerable.
Google has forgotten to fix the security hole. (Kind of hard to believe.)
Bluebox Security Scanner always shows vulnerable on rooted phones. But why should it?
Bluebox Security Scanner is defective at least on some phones.
I have made some stupid mistake. But which?
Please report what you see on Android 4.3.
I think is safe to say that #2 is clearly not your problem
https://android.googlesource.com/platform/libcore/+/38cad1eb5cc0c30e034063c14c210912d97acb92^!/#F0
If you're running the OTA then is mostly the app itself having issues BUT if you didn't and are running some winzip creation then I would go ahead and wait til you get the OTA or just run CM10.2
Good luck dude!
Mazda said:
… If you're running the OTA then is mostly the app itself having issues BUT if you didn't and are running some winzip creation then I would go ahead and wait til you get the OTA or just run CM10.2
Good luck dude!
Click to expand...
Click to collapse
Don't frighten me! Now where did I get that ZIP file from?
I'm pretty sure that it came from one of Google's download URLs.
One moment; I have a near-identical phone here that I updated with the very same OTA ZIP file. Let's call it phone B.
I just installed the Bluebox Security Scanner on phone B, and it shows no vulnerability. Now that is really strange. What could be wrong with my phone A? I know that the OTA update file checks all files before patching them and makes sure that nothing has changed from the original 4.2.2 version. So from all I know the two phones should be identical, as far as Android is concerned. Weird!
Update: Found the cause. Bluebox Security Scanner only scans once, when you start it for the first time. Then it keeps showing you the very same result, no matter whether and how your phone's software has changed.
I solved the problem by forcing the app to stop, then deleting its data. When I started the program after that, it re-scanned the phone and came up with the expected result. Only even later I found that the program has a menu, containing exactly one command: Rescan.
That is a crude user interface design mistake, not to say, a trap. "Rescan" should be an always visible button or, simpler and even better, the program should rescan every time when it is opened.
Update: They have fixed it. Good job, Bluebox. Now the app scans every time it is opened.
You had me scared for a minute... I'm no n00b, but I'm still a junior when it comes to deep down coding, patches, security and stuff. I mean, I know how to lock down a Windows machine pretty well, but Android is a whole different ball game for me. I'm currently running rooted stock 4.3 on a N4.
Good to know about Bluebox... I'm never sure if I should get a security app or not, or just not be stupid and visit xyzapps dot com for that sweet "free" game....
I stumbled upon something strange today, I don't really know what to do with this information... Thought I'd shared though.
Some history:
I got a tf700 early september 2012. Registered it with the Asus Device Tracker service.
The device suffered from sleep of death and after two RMA, "some parts" of my transformer have been replaced. I believe "some parts" is the mainboard (I cannot have details of the RMA since it was handled by my reseller).
Some time ago, I contacted Asus Support France to report I could not use the Device Tracker anymore (my goal being actually to unlock, see this thread where a user claims he was able to unlock after Asus solved his issue with the Device Tracker).
Among other things I told them the service did not list the updates OTA I had installed after the second RMA, which it did before.
Today's status:
Asus never solved anything (they even told me my android version was incompatible with the device tracker and I should contact the developer).
I connected by chance to the Device Tracker today and discovered... the service does list some updates I did NOT install !
In particular, it says the transformer received and installed the latest OTA ([WW_epad] 10.6.1.14.8 to 10.6.1.14.10) on 08/20, though I am still avoiding this one. (on a side note: I have not been able to unlock in 6 months or more, but I do receive OTA updates).
The implications ?
So I'm wondering... Did the service center reuse my faulty motherboard on another serviced device ? Am I really seeing the status of another user's device ?
I cannot locate the device referenced by my device tracker account. In previous attempts, I've tried locking the related transformer. The command however always fails due to "unstable connection". I tried adding my email to the message this time, just in case.
Hello,
My phone is protected using fingerprint scans and pin code. I noticed that after several failures the phone is not only telling me that it will lock, but also that it will reset (after 8 failures, or something like that).
I don't see that as a security feature, anyone willing to make me loose a lot of time only have to put his/her fingers 8 times on the button and ... everything is gone in my phone ?
Is this a local security feature ? I mean is it configurable somewhere ? or is coming from a remote policy, or hardcoded somewhere in the phone ?
Thanks.
Did you add your work email? I had this when I synched my work email to my device. Apparently, this is one of the security policies of my workplace.
And yes, I was locked out of my device a few days after I got it. It read my belly as a "fingerprint" unlock attempt, and soon I just saw it was wiping all my data. I was really bummed by that since it took hours for me to set up my device according to my liking. Fortunately, I still had my previous phone and didnt wipe it yet.
Yes, I have a work mail configured. Do you think it comes with security policies ? Because on our other phones (iphone, GS5/6) there is no similar settings put in place to wipe data.
My samsung phone has been reset a few times, wiped and reinstalled by Samsung techs, and Samsung in Japan, but, the identity theft cloning still happens. I have an AT&T phone that goes to a verizon network lock. In global tables showing
Vzw network lock 1,
And so far the consensus is that the hackers are using the date 12-31-1969 because most operations, apps,system,unix,internet etc are date dependant and sensitive so a date of 12-31-1969 is not valid and the files do not appear. Does anyone know how to rid my phone of these files? When i was hospitalized in feb 2021, my phone was intruded upon and the person linked my phone to a device only known as a linux 3800x that withdrew monies from my bank account. Just like scripts that are on the internet line that literally fried a twc modem every 2 weeks until we switched to AT&T provider. Can anyone think of or write an applet that checks the date of the files and when it encounters the 12-31-1969, it quarantines the files or corrects the date time stamp so the files update?
AFAIK in Android a file's creation date isn't available, only a file's last-modified date.