Hey guys!
I have a somewhat paranoid way of thinking of security. I would like to be able to tunnel my browser requests using a ssh-tunnel, especially if I am on an open wifi (even though tls should be secure enough).
I have followed some tutorials online:
First result on googling "tunneling-and-port-forwarding-in-android" (apparently new members are denied posting outside links)
First result on googling "shantanugoel ssh-tunneling-android"
I have set up a port forward with connect bot and have tried changing the proxy settings in AP but when I try to browse, it doesn't load anything.
(First result on googling "My internet connection through my operator (3G) does not work. Can I set it up manually?")
I think some tutorial stated that your device needs to be rooted, but if I have understood correctly, the fairphone should already be rooted, right?
Related
I just installed the latest WM6.1 rom by Kavana. I'm trying to connect to my private/work network, and I need to use EAP type "Smart Card or Certificate", but only PEAP and TLS are listed. Are there any solutions to this issue? I searched on this forum, but could only find the same question asked (but not answered) here:
http://forum.xda-developers.com/showthread.php?p=2028467&highlight=Smartcard#post2028467
Thanks!
Sorry for the lack of details but I had a similar problem. There are several google references to various ways to get certificates working. You can also disable certificate checking which is what I elected to do for now.
To force WM5 or WM6 to accept the PEAP server's certificate without attempting any other validation, add the following registry key:
[\HKLM\Comm\EAP\Extension\25\]
"ValidateServerCert"=dword:00000000
This worked for me. More good hacks and the full article/blog http://www.mobilewave.ro/forum/topic-2549.html
Can you link to those several references on google? Why is the smartcard or certificate option missing from this rom anyway? Are there any registry hacks to get this option back?
Hey man, do your home work and google and you can always change the registry entry if you think that the network your are connecting too is not trustworthy. Otherwise I think you will spend many hours of trial and error like I did.
I tried
"ValidateServerCert"=dword:00000000
I am still not able to connect to network. Also as said above, the TLS is not showing the certificates & smartcard. Also when I click on TLS "properties" nothing shows up. I have certificates installed, I can see it from Settings->Security->Certificates.
Any help. It is getting very frustrating.
Bump. Please chime in.
Hi all,
With reference to this thread I found:
https://supportforums.motorola.com/message/311407
I've got the same problem as he does.
There is no way to set proxy URL and proxy port for Wi-Fi connections. I am trying to access a secure WiFi network at my work but it also uses a proxy to enable access to the outside networks. I can access internal websites but not the "regular" Internet sites.
Click to expand...
Click to collapse
Been trying to get my Defy working with the university's Wi-Fi but apparently Android doesn't natively support it (sorry if I've worded it wrongly, still new to the OS) due to the lack of iptables.
Would flashing any of the ROMs out there help with this issue? And if so, which?
I'm on the 2.21 firmware.
I've tried multiple apps on the market and also tried following connection instructions for eduroam with no luck.
Thanks
Attached you will find an Excel file with 1,194 different connection settings for internet access and MMS. These settings are needed when you install custom ROMS, screw around with your phone and forget what you changed , use certain SIM unlock services, or when you have your phone tethered to your computer via USB. For example you need this for my tutorial on how to tether with the Dell Venue Pro entitled "Mango USB Tethering - Confirmed Working". This is why I have placed this in the hacking section instead of general.
If you find this useful please check out my other work available in my signature.
Cheers!
I guess this isn't as popular since most people can tether via WiFi now
Thanks, helped me setup data for some Canadian providers.
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
atombombzero said:
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Click to expand...
Click to collapse
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
I am running a rooted stock with a stock recovery. In installing the hotspot hack zip, does this require TWRP or CWM recovery??
Aronmorg said:
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
Click to expand...
Click to collapse
I am just a UNIX admin so I know enough to be dangerous. I am no dev.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
Also, I can't find the hack of which you speak. I scoured the forums today and found nothing.
I'm running synergy 4.3 rom and native hotspot works no problem. .
I just got my wife's s4 to use the native hotspot by downloading the service.odex and .jar with stock rom. I don't know if something like that is available with the note 2. I see that someone using the synergy 4.3 rom got native hotspot to work, but is that possible with stock rom.
So, here it goes.
My goal is to connect to a network using certain MAC address. Wanted network is marked with "open" and I know that it allows access only to certain devices (according to MAC) on which the administrator have gave a permission to. Once your MAC passes the verification, device gets connected to the network and then I'm asked to enter username and password through WEB browser (well known for me, because it is a procedure that I do on my other device, as well as all my colleagues do).
For example, I was allowed to provide one personal MAC address to administrator to connect to this network. I would like to set the MAC address of my other personal device and set it on my I9195 so that I can access the same network.
So, what have I done so far: I9195 is rooted, it has Android 4.2.2 on it and Busybox installed. I have changed MAC on it using following apps: MacChanger (blue WIFI logo), MAC Address Ghost (green ghost logo), using Android Terminal Emulator commands and via MAC Spoofer (black circle with green text logo). What can I conclude: As soon as superuser has granted the access to these apps, all of them manage to change the MAC. I've done the verification using Terminal Emulator. I also have to add that the MAC remains original if viewed from WIFI advanced menu BUT this shouldn't be an issue because:
1.) Colleague of mine is using his S4 (rooted etc.), while using MAC Address Ghost that does not change the original address (viewed from WIFI advanced menu) but he manages to make a spoof (verified from the Android Terminal Emulator, as all of this apps actually do) and he manages to connect without any problems in the same way as I connect with another device that I have!
2.) I had time to make a small test at home which put a light on the idea that the problem should be focused on the Samsung (and not on the router, especially because I am unable to modify anything on the router on this facility, not even restarting it). My home network works in a similar way as the network that we are discussing about. My S4 Mini has been included in it with his original MAC and it connects to the network without any problems. My other device is also included to the network using its MAC (the one that I am using for spoofing). My other device is turned OFF, router has been reset and I am normally accessing the network with S4 Mini. Then I run the MAC Address Ghost to spoof the MAC on my S4 Mini. In that moment, I have lost the connection that I had which means that the MAC spoofer actually did something. I tried to reconnect to the network but then I am asked to enter the password for my network. I have checked and re-checked it many times, tried to forget the network and doing it all over again but it does not accept the CORRECT password. Changing my MAC back to the original one connects S4 Mini back to the network, while accepting the password immediately.
Problem is represented in a way that it either says “saved” and does not connect to the network or every few times displays a message “Authentication error occurred”.
I have tried I would say every possibility that I’ve seen over the internet. That includes:
1.) Installing WiFi Connection Manager (it provided some info regarding the network that I wish to connect to: IEEE 802.11g standard, 54 Mb link and CH:11). I’ve used its function to fix the WIFI (advanced fix (root required)) but it didn’t help.
2.) All sorts of staying close to the rooter, while enabling and disabling the Power save mode (accessed via *#0011# command) or while having GSM signal.
3.) Browsing through system, data etc. folders to try to find the file that contains the MAC address information (like it did on older android versions in the nvram file). I’ve been unable to find this file or any sort of file that displays my MAC for the purpose to modify it.
I have a plan to upgrade Android to version 4.4.2 later today and make a test.
Please, feel free to suggest anything else! If I do not succeed, I will have to replace my S4 Mini with something else.
Kind regards,
QUICK REPLY: After installing CyanoGEN MOD 4.4.2, the problem remains!
I think there could be a shorter solution! On Sony Xperia Acro S with 4.1.2 Android it was just a matter of changing the MAC address within the file data/etc/wifi/fw! One minute modification...
So, please, if somebody knows the path to the file that contains MAC on CyanoGEN MOD 4.4.2 or on Android 4.2.2, PLEASE HELP!
Kind regards!