Category Archives: Posts

Kali.nogui.armel.zitstif.chroot.482013 Update

For those of you who don’t own devices that are officially supported by nethunter or if you’re not having any luck porting over nethunter using this method: https://github.com/offensive-security/kali-nethunter/wiki/Porting-Nethunter , there is hope for you to at least run Kali on your device. Of course you need a device that is rootable and you’ll need to download the following 7z file:

https://archive.org/download/Kali.nogui.armel.zitstif.chroot.482013/kali.nogui.armel.zitstif.chroot.482013.7z

kali.nogui.armel.zitstif.chroot.482013.7z

md5: d60c5a52bcea35834daecb860bd8a5c7
sha1: f62c2633d214de9edad1842c9209f443bcea385d

kali.img

MD5: be61799f8eb2d98ff8874daaf572a1d5
SHA-1: f9c6a820349530350bbb902d17ae6b4a5173937c

Then simply look over this post: http://zitstif.no-ip.org/?p=811

Once you have this setup, according to “JosephTheHacker Pwn3r” :

Great News ,I have successfully updated your kali img into rolling edtion! ,It really works at my tablet by editing the sources.list file in the “/etc/apt/sources.list”

in sources.list:

deb http://http.kali.org/kali kali-rolling main contrib non-free

deb-src http://http.kali.org/kali kali-rolling main contrib non-free

then I typed apt-get upgrade!

and also I doubled checked the new tools installed on kali img”

So essentially you’ll have to just edit your sources.list file to only have these repositories and issue a:

apt-get update && apt-get dist-upgrade -y

As for how well it works, I’m not quite sure because I am now running the nethunter ROM on my Nexus 6. However, I would like to thank “JosephTheHacker Pwn3r” for looking into this and informing me. Lastly, if rooting your phone is not an option but you still want a debian terminal based environment to work with, I highly recommend checking out Termux:

https://play.google.com/store/apps/details?id=com.termux&hl=en

Kali Linux 2.0 (x64) system upgrade GUI fix

When Kali Linux 2.0 came out I decided to upgrade my laptop to this version through the upgrade process (which took very long keep in mind.. it may have just been quicker to just reload the OS). Upon completion of the upgrade process I noticed the desktop GUI and windows didn’t look quite right. Additionally the theme wasn’t right either. Long story short I had to install these packages to fix the issue:

gir1.2-gnomebluetooth-1.0
gir1.2-gnomedesktop-3.0
gir1.2-gnomekeyring-1.0
gkbd-capplet
gnome-accessibility-themes
gnome-backgrounds
gnome-bluetooth
gnome-brave-icon-theme
gnome-calculator
gnome-colors-common
gnome-contacts
gnome-control-center
gnome-control-center-data
gnome-core
gnome-desktop3-data
gnome-dictionary
gnome-disk-utility
gnome-font-viewer
gnome-icon-theme
gnome-icon-theme-symbolic
gnome-keyring
gnome-menus
gnome-mime-data
gnome-online-accounts
gnome-online-miners
gnome-orca
gnome-packagekit
gnome-packagekit-data
gnome-packagekit-session
gnome-screenshot
gnome-session
gnome-session-bin
gnome-session-common
gnome-settings-daemon
gnome-shell
gnome-shell-common
gnome-shell-extension-dashtodock
gnome-shell-extension-easyscreencast
gnome-shell-extension-proxyswitcher
gnome-shell-extension-refreshwifi
gnome-shell-extension-workspacestodock
gnome-shell-extensions
gnome-sushi
gnome-system-log
gnome-system-monitor
gnome-terminal
gnome-terminal-data
gnome-theme-kali
gnome-themes-standard:amd64
gnome-themes-standard-data
gnome-tweak-tool
gnome-user-guide
gnome-user-share
kali-desktop-gnome
libgnome-2-0:amd64
libgnome-bluetooth13
libgnome-desktop-3-10
libgnome-keyring-common
libgnome-keyring0:amd64
libgnome-menu-3-0
libgnome2-0:amd64
libgnome2-bin
libgnome2-common
libgnomekbd-common
libgnomekbd8
libgnomevfs2-0:amd64
libgnomevfs2-common
libgnomevfs2-extra:amd64
libpam-gnome-keyring
libsoup-gnome2.4-1:amd64
network-manager-gnome
policykit-1-gnome

Or you can simply run this quick and dirty script (using sudo obviously):

View as txt here:

THENEWLIST.txt update (THENEWLISTupdated.txt)

I’ve compiled another HOSTS block list for those who want to block crap. If you’re not sure how to add the list to your hosts file, check out:

http://zitstif.no-ip.org/?p=570

You can download the updated HOSTS block list from here:

http://zitstif.no-ip.org/THENEWLISTupdated.txt

shasum: f94c3aee2e1483bc945e6a728ba8c70df821f5c3

Here’s a mirror:

http://s000.tinyupload.com/index.php?file_id=15983907671280562742

Enjoy less crap on the internet!

WARNING: I have tested adding this to my Windows 10 hosts and I have noticed svchost.exe (owned by NETWORK SERVICE) spikes up in CPU usage and DNS functionality stops responding momentarily until the mentioned process calms down in CPU usage. On my work computer running Windows 7 Professional in a domain environment the same service would spike up and seem to cause a DOS condition with DNS functionality and would not respond. USE WITH CAUTION AND TEST BEFORE DEPLOYING IN PRODUCTION ENVIRONMENTS.

#Update 10/9/2015

After testing and much consideration I do not recommend adding these hosts to your hosts list on Windows based systems unless they are higher end systems with cpu scores of like 8000 from https://www.cpubenchmark.net/

#Update 12/28/2015

This updated blacklist also causes issues with tennis.com comments section and Nexon account registration.