Kali/Annoyances - Revision history

Admin at 02:10, 13 August 2017

2017-08-13T02:10:25Z

← Older revision		Revision as of 02:10, 13 August 2017
Line 2:		Line 2:

	A list of annoyances in Kali, by topic, and hopefully a fix for each annoyance.		A list of annoyances in Kali, by topic, and hopefully a fix for each annoyance.

			Also see [[Kali Raspberry Pi/Post-Install]].

	===Kali Installs X on Raspberry Pi===		===Kali Installs X on Raspberry Pi===

2017-08-12T23:55:27Z

Network manager

← Older revision		Revision as of 23:55, 12 August 2017
Line 26:		Line 26:
	On Kali, specifically the desktop, NetworkManager automatically remembers and connects to wireless networks. What is this dumb, I can't, what idiot, stupid, dumb decision, I don't even know. Whoever decided to turn that one on should go jump off a bridge.		On Kali, specifically the desktop, NetworkManager automatically remembers and connects to wireless networks. What is this dumb, I can't, what idiot, stupid, dumb decision, I don't even know. Whoever decided to turn that one on should go jump off a bridge.

	Solution: disable this obnoxious piece of crap.		Solution: disable this obnoxious piece of crap. (Note that before you do this you should have your ethernet/wireless configured correctly, so that you won't lock yourself out of your device - see below).

	<pre>		<pre>
Line 39:		Line 39:
	$ apt -y autoremove		$ apt -y autoremove
	</pre>		</pre>

			Before you perform the above commands, add the following information to your <code>/etc/network/interfaces</code>:

			<pre>
			auto eth0
			iface eth0 inet dhcp
			</pre>

			This ensures that when you plug your ethernet cable into the port, your box will run through the usual DHCP requests and automatically get set up.

	===Vim Takes Forever To Open===		===Vim Takes Forever To Open===

2017-08-12T23:53:10Z

Network manager

← Older revision		Revision as of 23:53, 12 August 2017
Line 39:		Line 39:
	$ apt -y autoremove		$ apt -y autoremove
	</pre>		</pre>

			===Vim Takes Forever To Open===

			Not sure if this is a problem with vimrc or what, but vim takes a full 4-5 seconds to open, every damn time. How is this even possible? How can you possibly bloat such a lightweight and fast piece of software? Did I somehow install emacs in my sleep and run <code>alias vim='emacs'</code>?

	===Hidden Networks===		===Hidden Networks===

2017-08-12T23:53:03Z

Vim Takes Forever To Open

← Older revision		Revision as of 23:53, 12 August 2017
Line 21:		Line 21:

	Other distributions for the Raspberry Pi: http://elinux.org/RPi_Distributions		Other distributions for the Raspberry Pi: http://elinux.org/RPi_Distributions

	~~===Vim Takes Forever To Open===~~

	Not sure if this is a problem with vimrc or what, but vim takes a full 4-5 seconds to open, every damn time. How is this even possible? How can you possibly bloat such a lightweight and fast piece of software? Did I somehow install emacs in my sleep and run <code>alias vim='emacs'</code>?

	===Network manager===		===Network manager===

2017-08-12T23:46:07Z

Network manager

← Older revision		Revision as of 23:46, 12 August 2017
Line 41:		Line 41:
	<pre>		<pre>
	$ apt-get remove -y network-manager network-manager-gnome		$ apt-get remove -y network-manager network-manager-gnome
			$ apt -y autoremove
	</pre>		</pre>

2017-08-12T23:45:51Z

Network manager

← Older revision		Revision as of 23:45, 12 August 2017
Line 34:		Line 34:
	<pre>		<pre>
	$ systemctl stop NetworkManager.service		$ systemctl stop NetworkManager.service
	$ systemctl disable NetworkManager.service		$ systemctl disable NetworkManager.service
			</pre>

			Better yet, remove it:

			<pre>
			$ apt-get remove -y network-manager network-manager-gnome
	</pre>		</pre>

2017-08-12T23:37:24Z

List of Annoyances

← Older revision		Revision as of 23:37, 12 August 2017
Line 14:		Line 14:
	</pre>		</pre>

	Of course, the REAL fix is to create your own Kali ARM image. See [[Kali/Custom ARM Image]].		Of course, the REAL fix is to create your own Kali ARM image, or go with an alternative distribution.

			See [[Kali/Custom ARM Image]] for custom Kali ARM image.

			See [[DietPi]] for alternative RPi distribution that is both lightweight AND has wifi support built in. Since that's the whole freaking point. Lightweight, headless server with a wifi dongle.

			Other distributions for the Raspberry Pi: http://elinux.org/RPi_Distributions

	===Vim Takes Forever To Open===		===Vim Takes Forever To Open===
Line 34:		Line 40:

	No way to join a hidden network without turning off network manager and resorting to linux wifi command line wpa supplicant crap.		No way to join a hidden network without turning off network manager and resorting to linux wifi command line wpa supplicant crap.



	==Flags==		==Flags==

	{{KaliFlag}}		{{KaliFlag}}

2017-08-12T23:33:53Z

@@ Line 1: / Line 1: @@
-A list of annoyances in Kali.
+==List of Annoyances==
 ===Kali Installs X on Raspberry Pi===
@@ Line 32: / Line 34: @@
 No way to join a hidden network without turning off network manager and resorting to linux wifi command line wpa supplicant crap.

2017-08-12T23:33:19Z

@@ Line 1: / Line 1: @@
-HUGE annoyances in Kali:
+A list of annoyances in Kali.
-. Raspberry Pi image for Kali installs all manner of irrelevant, unnecessary, bloated crap. After doing an apt-get dist-upgrade, now I have a bunch of Apache services installed and running? I have a desktop X server running? Are you kidding me?? This is a headless server. WTF is it installing X by default for?
+===Kali Installs X on Raspberry Pi===
-. Network manager automatically remembers and connects to wireless networks. What is this dumb, I can't, what idiot, stupid, dumb decision, I don't even know. Whoever decided to turn that one on should go jump off a bridge.
+Raspberry Pi image for Kali installs all manner of irrelevant, unnecessary, bloated crap. After doing an apt-get dist-upgrade, now I have a bunch of Apache services installed and running? I have a desktop X server running? Are you kidding me?? This is a headless server. WTF is it installing X by default for?
-. No way to join a hidden network without turning off network manager and resorting to linux wifi command line wpa supplicant crap.
+Fix:

2017-08-12T23:21:24Z

← Older revision		Revision as of 23:21, 12 August 2017
Line 4:		Line 4:

	2. Network manager automatically remembers and connects to wireless networks. What is this dumb, I can't, what idiot, stupid, dumb decision, I don't even know. Whoever decided to turn that one on should go jump off a bridge.		2. Network manager automatically remembers and connects to wireless networks. What is this dumb, I can't, what idiot, stupid, dumb decision, I don't even know. Whoever decided to turn that one on should go jump off a bridge.

			3. No way to join a hidden network without turning off network manager and resorting to linux wifi command line wpa supplicant crap.