Since VZW still throttles hotspot, I found in another post a way to circumvent this.
I made a quick and dirty batch file that will take care of those steps.
It uses nvspbind, a Microsoft program (downloadable from MSDN if you don't trust mine) to remove the IPv6 binding from Wi-Fi.
Its the same steps as the post I linked, but as a batch file.
I take absolutely no credit for this finding, I just made the batch file.
If this worked for you, thank middleearth1010
Related
Hi all, I have a major concern about privacy and all the 3rd party data collectors...
A lot of apps are uploading user info and stats to companies like Flurry, pinch media etc.
I'm about to make the move from iphone OS to android, and i'm looking for a opt out to keep my privacy intact.
Saurik creaded PrivaCy for the jailbreak community that enabled on\off toggles for the 4 major companies.
My issue on iphone was that Pinch Media alone gathered the following information without my knowledge :
* iPhone’s unique ID (imei)
* iPhone model
* OS version
* Application version (in this case, camera zoom 1.x)
* If the application is cracked/pirated
* If the iPhone is jailbroken
* Time & date I start the application
* Time & date I close the application
* My current latitude & longitude
* My gender (if Facebook enabled)
* My birth month (if Facebook enabled)
* My birth year (if Facebook enabled)
I want the option to chose weither or not this kind of info gets collected and distributed.
I've looked into this issue on the android platform, and it seems like there's no option other than not to install the app.
Take for instance Locale. To my knowledge it uploads my imei nr (+lot of other info) to Flurry, whilst i do see the developers need to gather info, and I do not see why my imei number should be uploaded at all.
When I get my android phone I can only chose NOT to install locale, but I just want to prevent it from uploading such info..
Can anybody create a toggle, preferably one that doesn't aquire root, or some guide as to hosts file editing, or a firewall app that will give me this control over my device?
regards
-e
just add a line in hosts file like the following for each website you want to block:
127.0.0.1 some.company.com
Fantastic, thanks mate.
Unfortunately I will have to have root permissions to edit the hosts file.
(it might take time before the htc desire gets root)
(edit: unless theres another way to get write permissions for that file..?)
If I do mess with the hosts file I'd be keen on adding a fair few entries to block ads too..
Since the hosts file gets loaded in ram at bootup, will there be any noticably difference in speed due to the size increase?
regards
-e
could you please post the host-file or the addresses/ip's of the companies your gonna block?
they should be of interest for everybody here
1. You will need root access.
2. The change shouldn't impact the performance in the least. Any local host lookup is always faster than DNS lookup. Meaning that it should increase performance in cases where it finds the match in hosts file, although I doubt if you will notice it.
3. I wouldn't worry about RAM. The host file, even if you add a hundred entries, given that each line consumes 100 bytes, should still be under 10kb.
Great to hear. Thanks for the replies.
@fabsn: I'll post my hosts file as soon as I get this working.. (gimme a few weeks to get my phone, move to android and root
Although: I'd be keen on using the adblock app in androidstore (the one that modifies the hosts file), but my manual changes will break every time I update the app.
I'll try to get hold of the dev to se if he/she might add these info collectors (like Flurry) in another version so that people can get "the best of both worlds"
By the way: I wish all devs that utilizes info collection in their apps could just provide users with an opt out, then my problem would be solved...
-e
http://textbin.com/x6430
Here is a complete "phone home" list for the iPhone. A lot of this will directly apply to android as well, so perhaps a nice soul here at the forum could compile the most useful adresses for me (I'm writing on my phone and it's a b**** to do this on)
the list is taken from: i-phone-home.blogspot(dot)com/
so credit goes to that community.
I really want to combine this with the hosts file that jamesisbored/droid has for adblock..
I will test this once desire hits my mailbox and someone finds root.
-e
This sounds like a great idea. Once a comprehensive list is compiled it should be passed on to "bigtincan". I know myself and a lot of other people use their "ad free" app to block ads using the same method mentioned by Ady above. Although they may be blocking them already and I don't know. I've never looked closely at the host file.
http://bigtincan.com/downloads/android.html
Any progress made on this end?
ady said:
1. You will need root access.
2. The change shouldn't impact the performance in the least. Any local host lookup is always faster than DNS lookup. Meaning that it should increase performance in cases where it finds the match in hosts file, although I doubt if you will notice it.
3. I wouldn't worry about RAM. The host file, even if you add a hundred entries, given that each line consumes 100 bytes, should still be under 10kb.
Click to expand...
Click to collapse
I am new to modding my phone, would you be so kind as to go into more detail how to do this. Specifically, what is this "Hosts file" you speak of? I do have root access and searched my entire phone for a file like that with no joy.
Also, the links provided to possible host data do not work, can somebody update that?
Thanks!!!:laugh:
You may be interested in the MOAB (mother of all adblockers) thread here on xda. Best ad blocker out there, imo, if you haven't already. Sorry, I can't link it now.
Sent from my SCH-I545 using Tapatalk
So for those of you wondering if a Hardware Level Modification can be made to the US-VZW 3G+WiFi Xoom to enable the Native Tethering capabilities of the Xoom...Similar to the one used on the Droid 3, X2 and other Motorola Devices (Thanks To Team RedHat and CellZealot)...There IS!!!
Last night, while working on another project on the Xoom, I had an idea. Here is the result.
NOW, I am saying this up front! IF you decide to make this modification, you do so at your own risk. Both the risk to your device (possible completely bricked Xoom) and to the possible violation of your Terms of Service with your specific provider. Please know and understand the risks, and don't blame me if it goes horribly wrong and you end up with a Xoom shaped paper-weight.
I do need some willing volunteers to test the system on their Xooms and make sure that others are:
A) Able to follow the directions and clarify any points I may be vague on describing.
B) Verify my results of making the native WiFi Tethering work on the Xoom.
I will be gone most of the weekend, but please PM me if you are willing to give this a try.
Items you will need:
Latest Motorola Drivers WITH Moto-Helper. Download the latest version from here: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
RadioComm 11.12.1 (Could be that 11.11.11 works. I will try that over the weekend and verify)
Micro USB Cable
Windows (RadioComm application is for Windows, sorry Linux Ladies and Gentlemen)
A LOT of Patience
Notepad or similar note program to copy/paste original information
Ability to follow directions Without skipping steps.
Able to Document all your steps.
A good grasp of copy/paste and right-click function
A willingness to push the envelope on your device to prove a concept.
Again, this is a proof of concept. I do not condone or encourage violation of your terms of service with your provider.
I do NOT yet know if this works on the 4G upgraded Xoom tablets. Volunteers appreciated. Otherwise I will be sending mine in for upgrade soon and can test the following: If the mod survives the upgrade process, and if it works after the upgrade to 4G (There is no reason it shouldn't unless changes are made at the NvRAM level with the 4G upgrade, AND those changes include these values)
It is very similar to the Version for the Droid 3, but the parameters are different for the 3G Xoom. It has also been setup to block some of the features that we used to so easily make the changes to the Droid 3. The first item you will note, when making the change, is that the characters are no longer visible in the field where you will be copying and pasting your values.
The other change is that it will only ACCEPT 256 bits when storing back information. If you export the Existing values, it will add 128 bits of 0s to the output. Read as a huge pain to make sure you delete exactly 128 of them.
The Field for the Radio Session Information is in a different Tab of the RadioComm application as well. Read Element Length is Greyed out, so you get what you get for an output. No more can you dictate that value.
Essentially, it means that this Mod IS possible. CAN be done WITHOUT root as it is a Hardware Level modification below the operating system. Similar to Team RedHat's Awesome Explaination HERE
So, that being said. PM me today and tomorrow if you want me to send you directions on trying the procedure Sunday night, and I will take care of getting those PMd back to you.
Thanks to CellZealot for the 11.12.1 version of Radiocomm. And Thanks to TBH for finding the vulnerability to seek out and test on the Xoom.
If you like what I do, or have helped you; please consider Donating. All Donations in February are forwarded to a DEV that has helped me and many others in the Eris forums; Workshed. (Thanks Shed, for everything on the Eris! 2 still running GSB 4.4)
You will also need contortionist fingers (joke) to be able to put your xoom into BP linux-cold boot in order to get the NV to read properly and allow the mod.
If not returned to original via RadioComm, this appears to be a permanent WiFi Tether enablement for the VZW-US-3G Xoom.
AGAIN, I take NO responsibility for you damaging your device or violating your Carrier's TOS. This is proof of concept ONLY. Use at your own risk.
IF I get too many volunteers, I WILL let you know the trial is MAXed out, and will post the final findings in the next posting that I will reserve for the Directions and Layout.
I'm thinking that 10 will be the Max for this week. If all goes well, I will have directions posted by the end of next week. Let's hope!!
Thanks, and please consider making a Donation for the "Give to Shed" fund.
Reserved for Directions
Reserved for Current Findings Updates
Moved to proper forum.
This tutorial will explain how do basic developing on your Windows/Linux Machine from your tablet or smartphone while away from it. This is a very simple process and I take no credit for the application used in this tutorial.
Its quite simple:
Install PocketCloud from the Play store, set it up, follow the directions to get it set up, install it on your PC/MAC, and vwala! I have successfully decompiled an app, surfed the net, edited XMLs, etc. from my tablet (this is the most recommended device due to the large screen, 8-10 inch tablet will give you the easiest way). Please note that you have to have the stuff installed such as APK Multi-tool, Notepad++, etc. to do this stuff, this simply allows you to remotely develop with all of your tools while away from them, while not having to jump through hoops like INSTALLING THE OS ON YOUR DEVICE (even though that's cool too). Also, I am using this with 1 MB internet speeds, and it is pretty laggy, but not unusable. Awesome 3G speeds, 4G or wifi are needed or strongly advised (I think 3 MBps+ will give you some solid performance)
THis is a small contribution, is self explainitory, and helped me the other day while I was at school . I was curious about the code located in the ICS apks and remembered I had this, so I decompiled the app from my phone, it is a VERY USEFUL TOOL for any [aspiring/veteran] developer.
AirDroid App from Play Store is also very good! Nice guide.
One more thing if you try to edit system Apps then this technique becomes complicated. You should flash it via creating a small updater-script and making a small directories in which you would put your system apps so they can work well.
One of the most severe threats when surfing the Internet currently is browsing a website that does Canvas-Fingerprinting. For example here is reported, that actually 5600+ sites do so.
I've tranformed the 5600+ list into a text-file (57 copy & paste operations) that easily can be imported into your PC's HOSTS file. The text-file is attached.
HTH
If you know a little about MortScript, you futurely can create by yourself an updated text-file to be imported in your PC's HOSTS file using a script as shown next:
Code:
Path=SystemPath("ScriptPath")
InFile=Path\"sites-with-canvas-fingerprinting.txt"
If(NOT FileExists(InFile))
Exit
EndIf
OutFile=Path\"HOSTS-file-extension.txt"
OutFileLine="######## Canvas-Fingerprinting Domains ##################^NL^"
WriteFile(OutFile,OutFileLine,0)
LineCount=0
InFileLine=ReadLine(InFile)
While(NOT IsEmpty(InFileLine))
URLStartPos=Find(InFileLine,"http")
If(URLStartPos)
InFileLine=SubStr(InFileLine,URLStartPos)
URLEndPos=Find(InFileLine," ")
If(URLEndPos)
URLToBeBlocked=SubStr(InFileLine,1,(URLEndPos-1))
Else
URLToBeBlocked=InFileLine
EndIf
LineCount+=1
OutFileLine="127.0.0.1 "&URLToBeBlocked&"^NL^"
WriteFile(OutFile,OutFileLine,1)
EndIf
Sleep(1)
InFileLine=ReadLine(InFile)
EndWhile
If(LineCount)
OutFileLine="######################################################"
WriteFile(OutFile,OutFileLine,1)
Message(OutFile&" created")
Else
Delete(OutFile)
Message("Failed create "&OutFile)
EndIf
While I appreciate the effort, mass-blocking via the hosts file isn't a good idea for canvas fingerprinting (CF) blocking. In fact, it's not a good idea, period, since it requires the user's thorough knowledge of the sites be blocked, and constant monitoring of any changes. IP-blocking should be done only on an individual basis, with known-bad actors. In any case, CF in itself is an insufficient reason to entirely ban a site, which may be useful for the user.
Browser/system fingerprinting is a continuing escalation, with moves and countermoves on both sides. Now that this new CF technique has made the news, circumvention methods will likely be made available at the browser level, via extension or plugin. I'd suggest simply keeping up with developments by periodically Googling on "canvas fingerprinting blocking".
I did just that to find out more about it, and blocking methods. From ghacks.net,
http://www.ghacks.net/2014/07/21/companies-use-canvas-fingerprinting-track-online/
CF is simply another of several fingerprinting methods. From the the EFF's Panopticlick page (fingerprint test), your browser plugin details are already enough to establish a unique fingerprint. All are limited by the fact that changes to the user's system/browser can change the fingerprint. With Chrome/Firefox rapid iterations, I don't see CF as a major concern.
http://panopticlick.eff.org
No easy blocking methods exist as of yet for CF, although plugins will surely appear for it. The privacy conscious can always take further steps by researching on "how to modify browser fingerprint". I can only imagine that spoofers exist.
it's interesting, will think about
Thread Closed
Thread Closed
We all know that, we need a Wireguard Account and its application to use Wireguard VPN(AzireVPN) services.
Click to expand...
Click to collapse
I should clarify that WireGuard ≠ AzireVPN. WireGuard is an open source VPN protocol and implementation project I started. AzireVPN is one of many providers selling commercial service to their particular WireGuard servers. Beyond that, they are pretty separate and unrelated.
With that out of the way, I'd encourage people not to use the attached zips of the original post here. They contain private keys -- which are evidently no longer private -- which means that if any other XDAers are using it, you'll be kicked off by each other and the thing will basically be unusable. More obviously, this also means there are grave security issues, since anybody can impersonate you, since your private key is shared with the world. It's sort of like if a stranger on the street gave you a microphone with an antenna attached and said, "you can trust this microphone with all your secrets, I swear", and then walked away with no further explanation. Don't talk into microphones given to you by strangers.
zx2c4 said:
I should clarify that WireGuard ≠ AzireVPN. WireGuard is an open source VPN protocol and implementation project I started. AzireVPN is one of many providers selling commercial service to their particular WireGuard servers. Beyond that, they are pretty separate and unrelated.
With that out of the way, I'd encourage people not to use the attached zips of the original post here. They contain private keys -- which are evidently no longer private -- which means that if any other XDAers are using it, you'll be kicked off by each other and the thing will basically be unusable. More obviously, this also means there are grave security issues, since anybody can impersonate you, since your private key is shared with the world. It's sort of like if a stranger on the street gave you a microphone with an antenna attached and said, "you can trust this microphone with all your secrets, I swear", and then walked away with no further explanation. Don't talk into microphones given to you by strangers.
Click to expand...
Click to collapse
Hi @zx2c4
Thank you for clarifying certain things. As per your post there are several security issues which is a matter of concern. I thought its a great idea to use wireguard vpn because this just works fine. Since *Public Key* resides in the *.conf files whenever i use world-writable permission for *.conf files and setup the VPN connection. It warns me at the time of execution of script not to use *world-writable* permission. So i changed the permission to *owner* only and make them sticky. After this everything seems working fine.
TheHitMan said:
Hi @zx2c4
Thank you for clarifying certain things. As per your post there are several security issues which is a matter of concern. I thought its a great idea to use wireguard vpn because this just works fine. Since *Public Key* resides in the *.conf files whenever i use world-writable permission for *.conf files and setup the VPN connection. It warns me at the time of execution of script not to use *world-writable* permission. So i changed the permission to *owner* only and make them sticky. After this everything seems working fine.
Click to expand...
Click to collapse
Your irrelevant response here isn't at all related to the security issue at hand, which probably indicates you don't understand the security issue. If you tell the world your private keys, those private keys are no longer secure. Your zip files contain static private keys. Hence, they are no longer private.
I'd strongly recommend you take down this post before others use it and find themselves in a dangerous situation. It looks like you put a lot of hard commendable work into this release, and so I'm very sorry to deliver the bad news to you.
Regrettably I won't have the time to field additional follow-ups on the matter. However, I'd encourage those reading not to use the zips attached to the original post.
zx2c4 said:
Your irrelevant response here isn't at all related to the security issue at hand, which probably indicates you don't understand the security issue. If you tell the world your private keys, those private keys are no longer secure. Your zip files contain static private keys. Hence, they are no longer private.
I'd strongly recommend you take down this post before others use it and find themselves in a dangerous situation. It looks like you put a lot of hard commendable work into this release, and so I'm very sorry to deliver the bad news to you.
Regrettably I won't have the time to field additional follow-ups on the matter. However, I'd encourage those reading not to use the zips attached to the original post.
Click to expand...
Click to collapse
I really appreciate the time you gave here to clarify certain useful thing. I am going to take these downloads and this thread down. @zx2c4 thanks for your work. The VPN Protocol is amazing and works without any problem :good::good: .
Thread closed on OP request
Thread re-opened at OP's request.