[[Q] How do I edit a forum thread ?]

oh wow! that's a first! Thanks for sharing man, all those phones though. I didn't they they have all those phones to execute the clicks, I was thinking more on the software bots side. 

[Looking for a VPS]

Correction: Vultr introduced a $2.5 plan as their cheapest. And also they use SSDs.

[Looking for a VPS]

I use Vultr , for my personal website and deploying test servers for pen testing etc. It's really cheap. 5 USD/month for the cheapest plan. and its pay as you go. billed by the hour. 

[[Q] How do I edit a forum thread ?]

Thanks for the reply,

I don't see the "Edit" or "Delete" buttons in my posts. I guess I'll have to just wait and see. Forum system should implement a feature where it verifies the account by a phone number. So if the user verifies his/her phone number then the account is deemed to be non-spam.

[[Q] How do I edit a forum thread ?]

Hi,

Last night I posted a 'How To' thread under the Hacks/Mods category. Today I decided to write a bash script to automate the process. While I was going through the thread I wrote, I noticed that there are some typos. I would like to edit the thread but there seems to be no option to do so. I understand that as I'm a newbie to Hak5 forums, my account editing privileges are revoked until I post 5 times, but I'm not sure if this is affecting the ability to edit a thread.

If anyone could clarify this issue or an admin allow me to edit the thread, that would be awesome!

 

Thanks

[[HOW TO] [SCRIPT] Increase TX Power Of A WiFi Card Beyond 30dBm (Kali Linux)]

Hi all,

I'm a newbie to Hak5 Forums, so if this thread is in the wrong category, it would be great if the admins could move it to the correct category. 

Most of you are probably using 'BO' as the region for 'iw' on Linux. This allows the WiFi interface to operate at 30dBm (1 Watt) at max. However, if you're like me and have a device that is capable of transmitting over 1W (I have Alpha Network AWUS036NH - 2W), you might be interested in increasing the TX power beyond 30dBm. 

By default, selecting 'BO' as the region only allows the device to operate at a maximum of 30dBm. 

I tested this on my Raspberry Pi 3, Model B running Kali Linux (with the kali-linux-full metapackage). 

*** If you are lazy and don't want to follow these manual steps below, I made two bash scripts that will work on Kali Linux and Ubuntu  : https://github.com/hiruna/wifi-txpower-unlocker

 

Working directory:

/root

Steps:

1. Update and upgrade

apt-get update
apt-get upgrade

2. Install dependencies to compile

apt-get install pkg-config libnl-3-dev libgcrypt11-dev libnl-genl-3-dev build-essential

3. Download the latest Central Regulatory Domain Agent (CRDA) and Wireless Regulatory Database

I downloaded crda-3.18.tar.xz and wireless-regdb-2017.03.07.tar.xz

wget https://www.kernel.org/pub/software/network/crda/crda-3.18.tar.xz
wget https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2017.03.07.tar.xz

4. Unzip the downloaded files

tar xvJf crda-3.18.tar.xz
tar xvJf wireless-regdb-2017.03.07.tar.xz

5. Navigate into wireless-regdb-2017.03.07

cd wireless-regdb-2017.03.07

6. Open db.txt and locate the region BO section

nano db.txt

You will see something like this:

country BO: DFS-JP
	(2402 - 2482 @ 40), (30)
	(5250 - 5330 @ 80), (30), DFS
	(5735 - 5835 @ 80), (30)

The number in the second set of brackets (for each frequency) is the txpower. Since I'm using the 2.4Ghz and want a txpower of 2W (~33dBm), I changed the 20 to 33, and saved the file:

country BO: DFS-JP
	(2402 - 2482 @ 40), (33)
	(5250 - 5330 @ 80), (30), DFS
	(5735 - 5835 @ 80), (30)

I also noticed that region AU allows 36dBm for 2.4Ghz, so you could just continue without modifying the region BO:

country AU: DFS-ETSI
	(2400 - 2483.5 @ 40), (36)
	(5150 - 5250 @ 80), (23), NO-OUTDOOR, AUTO-BW
	(5250 - 5350 @ 80), (20), NO-OUTDOOR, AUTO-BW, DFS
	(5470 - 5600 @ 80), (27), DFS
	(5650 - 5730 @ 80), (27), DFS
	(5730 - 5850 @ 80), (36)
	(57000 - 66000 @ 2160), (43), NO-OUTDOOR

However, I checked with Kali Linux (without compiling and changing the regulatory.bin) and it showed that max txpower was only 20dBm:

country AU: DFS-ETSI
	(2402 - 2482 @ 40), (N/A, 20), (N/A)
	(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5490 - 5710 @ 160), (N/A, 24), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)

So I'm assuming Kali Linux is using an old regulatory.bin and legislation in AU has changed.

7. Compile

make

8. Backup up your old regulatory.bin file and move the new file into /lib/crda

mv /lib/crda/regulatory.bin /lib/crda/regulatory.bin.old
mv regulatory.bin /lib/crda

As mentioned in https://wireless.wiki.kernel.org/en/developers/regulatory/crda and https://wireless.wiki.kernel.org/en/developers/regulatory/wireless-regdb, we need to include RSA public keys in crda-3.18/pubkeys. I noticed that there are already 2 .pem files in crda-3.18/pubkeys:

sforshee.key.pub.pem
linville.key.pub.pem

9. Copy root.key.pub.pem into crda-3.18/pubkeys. I also copied sforshee.key.pub.pem from wireless-regdb-2017.03.07 as it was newer:

cp root.key.pub.pem ../crda-3.18/pubkeys/
cp sforshee.key.pub.pem ../crda-3.18/pubkeys/

I found that there are two other pubkeys located at /lib/crda :

-rw-r--r-- 1 root root 451 Jan 18 12:58 benh@debian.org.key.pub.pem
-rw-r--r-- 1 root root 451 Jan 18 12:58 linville.key.pub.pem
-rw-r--r-- 1 root root 451 Jan 18 12:58 sforshee.key.pub.pem

So I copied them too (wasn't too sure whether I needed to copy them):

cp /lib/crda/pubkeys/benh\@debian.org.key.pub.pem ../crda-3.18/pubkeys/
cp /lib/crda/pubkeys/linville.key.pub.pem ../crda-3.18/pubkeys/

10. Navigate into crda-3.18 and open the Makefile

cd ../crda-3.18
nano Makefile

In Kali Linux, crda is located at /lib/crda instead of /usr/bin/crda, so in the file change the 3rd line REG_BIN?=/usr/lib/crda/regulatory.bin to REG_BIN?=/lib/crda/regulatory.bin :

REG_BIN?=/lib/crda/regulatory.bin

11. In the Makefile, find the line CFLAGS += -std=gnu99 -Wall -Werror -pedantic and remove the -Werror option (I couldn't compile without changing it as it treats warnings as errors):

CFLAGS += -std=gnu99 -Wall -pedantic

12. Compile

make clean
make
make install

That's it! I rebooted my Raspberry Pi after compiling.

reboot

13. Now let's change the region and set the txpower to 33dBm:

ifconfig wlan1 down
iw reg set BO
iwconfig wlan1 txpower 33
ifconfig wlan1 up