| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,952
» Latest member: Aruz508
» Forum threads: 16,335
» Forum posts: 117,436
Full Statistics
|
|
|
| MAC Address/NIC Privacy Script [various options] |
|
Posted by: RTP - 08-11-2020, 10:31 AM - Forum: Mobian on PinePhone
- Replies (2)
|
 |
Edited: added new smartphone mimic -p
A script I wrote (bash) called WiPri (WiFi Privacy: I use it on Mobian/Arch so wifi tracking beacons/public wifi do not track my phone movements and thought I would share with other Pinephone privacy interested users (since mac addresses generally stay static and easily trackable by default).
It works on default Mobian install (no extras needed) (Arch was easy to install a missing prerequisite bash command) and has various options for different types of MAC address/network device disinformation. The install.sh part gives you the option of installing as a command or optionally as a systemd service (systemd service starts at boot- by default the .service file sets a new unique, randomly generated (with valid OUI) mac address identity at each boot (valid OUI imho superior to false OUI as tracking many times weeds out nonvalid OUI mac addresses to track down true mac address leaks).
If installed as systemd service the default is the above command (sets device wlan0 [change to match your device name if not wlan0] and -i sets a randomly generated new mac address identity to be held for remainder of command run (or if systemd by default the above changes the mac address identity at each boot and holds it until next power off)
Currently -i [new static random identity] by default checks current mac address every 20sec to ensure firmware doesn't reset mac address (on standard mac changers some cards try to leak/reset address). if the mac address changes during one of the regular checks it sets it back to the original chosen, randomly generated mac identity to be held.
Other commandline options:
The above -p generates/sets a single random, valid MAC address either Apple or Samsung (to mimic smartphones the most common wifi devices in area). It holds that single randomly generated valid mac.
The above -P flag is similar to -p but instead of holding a single Apple/Samsung mac address, it continuously changes mac addresses every so often (continuously randomized changing times), at continuously changing randomized mac addresses with Apple/Samsung OUI. Again, to blend in with smartphones
Code: wipri -d wlan0 -r -h
The above sets wlan0 as device and continually randomizes mac address (again, valid OUI's) to be changed at continually changing randomized times, at continually changing randomized mac addresses. The -h flag generates a randomly generated hostname using a standard set of randomly chosen bases with a randomized extension. Example: PC-27423 or My-iPhone (will be adding Apple OUI list in near future to mimic iphones)
The above is nice for travelling ime (continually changing randomized addresses at randomized times make more difficult to do pattern analysis)
Code: wipri -d wlan0 -m [mac address here]
The above lets you select any mac address of your choice and by default checks every 20sec to ensure firmware doesn't crash or reset it.
Code: wipri -d wlan0 -r -s -h
The above -r flag like earlier changes the mac address to continually changing randomized mac addresses at continually changing randomized times. The -s is an experimental feature that makes the txpower signal change strengths (while staying connected) giving wifi tracker beacons changing signal strengths, giving the impression your device is moving and attempts to confuse trackers.. The -h again changes the hostname to a randomized address (hostname is another fingerprint on networks).
The above changes mac address at continually changing randomized times while simultaneously changing hostname and txpower at randomized strengths at continually changing randomized times (to give impression of new devices: new hostname at same time as new txpower as same time as new mac address).
Video installing WiPri on Mobian/Pinephone:
https://youtu.be/1j-AtFtsqH4
If you want to check out latest: https://github.com/Aresesi/wipri
To make a copy of the files:
Code: git clone https://gitlab.com/Aresesi/wipri
The install.sh does all the work (and asks if you want it as command or optional systemd boot service)
Hope someone finds it useful 
|
|
|
|
| Powertop? |
|
Posted by: stozi - 08-11-2020, 10:27 AM - Forum: General Discussion on Pinebook Pro
- No Replies
|
 |
I see tlp is pre-installed on the default Manjaro, I assume it's configured well. Anyone tried running Powertop too? I know some people run both. Powertop has an automatic setup, I'm just worried it will mess something up. Anyone tried? any tips? should it help battery life?
|
|
|
|
| audio jack: OMTP or CTIA? |
|
Posted by: desca - 08-11-2020, 08:28 AM - Forum: PinePhone Hardware
- Replies (2)
|
|
Searching the forum, I see where someone said that the A64 board claimed to be CTIA in the datasheet but was really OMTP. And I see that the PinePhone datasheet also says CTIA… Can anyone tell me whether that’s true?
|
|
|
|
| Build issue on Windows 10 |
|
Posted by: thibww67 - 08-11-2020, 06:17 AM - Forum: PineTime Tutorials
- No Replies
|
|
Hi,
I'm on Windows 10, I managed to launch the Cmake command with OpenOCD mode.
Then, when I launch "make" I have errors :
arm-none-eabi-gcc: error: BOARD_PCA10040: No such file or directory
arm-none-eabi-gcc: error: CONFIG_GPIO_AS_PINRESET: No such file or directory
arm-none-eabi-gcc: error: DEBUG: No such file or directory
arm-none-eabi-gcc: error: DEBUG_NRF_USER: No such file or directory
arm-none-eabi-gcc: error: FREERTOS: No such file or directory
arm-none-eabi-gcc: error: NIMBLE_CFG_CONTROLLER: No such file or directory
arm-none-eabi-gcc: error: NRF52: No such file or directory
arm-none-eabi-gcc: error: NRF52832: No such file or directory
arm-none-eabi-gcc: error: NRF52832_XXAA: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_12: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_15: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_20: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_31: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_36: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_51: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_54: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_55: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_58: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_64: No such file or directory
arm-none-eabi-gcc: error: NRF52_PAN_74: No such file or directory
arm-none-eabi-gcc: error: OS_CPUTIME_FREQ: No such file or directory
arm-none-eabi-gcc: error: __HEAP_SIZE=8192: No such file or directory
arm-none-eabi-gcc: error: __STACK_SIZE=8192: No such file or directory
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
arm-none-eabi-gcc: error: unrecognized command line option '--defsym'
So I tried to use nrf Connect to use DFU, but I have not the possibility to use it on the application (I'm with a Glaxy S8 and it is not poossible with an IPhone too)
I have no Raspberry Pi available right now.
What is the solution to flash it with my computer ?
Thank you !
|
|
|
|
| openwrt for the rock64 |
|
Posted by: wilsonYan - 08-11-2020, 12:13 AM - Forum: Linux on Rock64
- Replies (29)
|
|
hello,
for anyone interested I managed to generate an openwrt image for the rock64 based off the latest master tree
Link to download:
https://yadi.sk/d/TfX6-MYy3RTf5h?w=1
I basically provide this as is as a proof it's doable that said it should be good to go as a basic router using ethernet vlans, and there's wireguard that can be set up via webui to try it as a vpn etc. Power usage seems good, only 1.4w-1.5w idle with only the microsd card and ethernet plugged in and working.
Don't forget to turn on 'packet steering' in the web ui and you can probably increase performance by increasing the minimum cpu frequency in the starup section by just pasting something like ''echo 600000 > /sys/bus/cpu/devices/cpu0/cpufreq/scaling_min_freq" or "echo 816000 > /sys/bus/cpu/devices/cpu0/cpufreq/scaling_min_freq"
|
|
|
|
|
