This script will ping a Class B network(10.66.0.0/16) and put the responding IP address in a file called status. The next part of the script reads the status file and run a dig -x <IPADDRESS> +short. We pipe the dig results to a file called dns.log.#!/bin/bash # Write a shell to do a ping sweep and use the results with DIG # ------------------------------------------------------------------------- # Copyright (c) 2011 Sif Baksh # This script is licensed under GNU GPL version 3.0 or above # ------------------------------------------------------------------------- # This script is part of Sif Shell Script Collection (SSSC) # Visit http://sifizm.com/ for more information. # ------------------------------------------------------------------------- # NETS="10.66" # bash while loop for NET in $NETS; do for n in $(seq 1 254); do A=${NET}.${n} for s in $(seq 1 254); do B=${A}.${s} ping -i 0.3 -w 3 ${B} -c 3 if [ $? -ne 1 ] then echo "${B}" >> status fi done done done # Test address to name to address validity echo echo -e "\taddress -> name -> address" echo '-------------------------------------' while read H; do HOST=$(dig -x $H +short) if test -n "$HOST"; then ADDR=$(dig $HOST +short) if test "$H" = "$ADDR"; then echo -e "ok\t$H-> $HOST -> $ADDR" >> dns.log elif test -n "$ADDR"; then echo -e "fail\t$H -> $HOST -> $ADDR" >> dns.log else echo -e "fail\t$H -> $HOST -> [unassigned]" >> dns.log fi fi done < statusUpdated DNS script now it just ping all your internal Class B networks
and run the same dig commands. Now the file name is dns-"${NET}"-log
which means "${NET}" is the ClassB address of your choosing.#!/bin/bash # Write a shell to do a ping sweep and use the results with DIG # ------------------------------------------------------------------------- # Copyright (c) 2011 Sif Baksh <http://sifizm.com/> # This script is licensed under GNU GPL version 3.0 or above # ------------------------------------------------------------------------- # This script is part of Sif Shell Script Collection (SSSC) # Visit http://sifizm.com/ for more information. # ------------------------------------------------------------------------- # NETS="172.25 172.31 10.66 10.67" # bash while loop for NET in $NETS; do for n in $(seq 0 255); do A=${NET}.${n} for s in $(seq 0 255); do B=${A}.${s} ping -i 0.3 -w 3 ${B} -c 3 if [ $? -ne 1 ] then HOST=$(dig -x $B +short) if test -n "$HOST"; then ADDR=$(dig $HOST +short) if test "${B}" = "$ADDR"; then echo -e "ok\t${B}-> $HOST -> $ADDR" >> dns-"${NET}"-log elif test -n "$ADDR"; then echo -e "fail\t${B} -> $HOST -> $ADDR" >> dns-"${NET}"-log else echo -e "fail\t${B}-> $HOST -> [unassigned]" >> dns-"${NET}"-log fi fi fi done done done
Ping Sweep and DIG to check what’s missing in your DNS
Empathy with Office Communicator 2007
Using Fedora 15, but the same steps will work for Ubuntu
1 – First we need to install SIPE (yes I’m using the GUI, trying to make it friendlier for other users)
2 – Search for SIPE and install both from the results window
3 – Configure Empathy for Office Communicator 2007
4 - Here is how to configure the SIPE account in Empathy:
- Account: the username for communicator (at my company it is my e-mail)
- Password: obvious

- Server: it seems required to give the server with Empathy (whereas Pidgin Sipe since 1.7 autodetects it). Ask your administrator, or use Communicator and check the network (using Wireshark for instance) to see which server it connects to.
- Transport: auto works for me
- SSO: I had to check this one
- Email: as this is the same as my username, I left it blank
- Email login: here I had to put my SSO login (in the form of domain\domainlogin)
- Email password: as it is the same for the domain and Communicator, I left it blank
Fedora 64bit Flash Install
Third Party Repository
Alternately, a third-party yum repository for the 64-bit Adobe Flash plugin is available from community member leigh123linux. The forum thread for this effort is here. To install the yum repository, one would issue:
su -c 'yum localinstall --nogpgcheck http://www.linux-ati-drivers.homecall.co.uk/flashplayer.x86_64/flash-release-1-2.noarch.rpm'
Be sure to check the GPG key fingerprint against a trusted source. It is assumed this repository will post updates as they become available, but as with any repo be aware you are delegating your system security to a third party. To install the flash plugin, remove old versions (especially i586) if necessary, then install from the repository:
su -c 'yum remove flash-plugin' su -c 'yum install flash-plugin'
Checking the plugin
After the installation, exit all copies of Firefox and start it again to enable the plugin. Then type the following text in the Firefox address bar:
about:plugins
A section similar to the following should appear:
Flash-check-2.png
This information tells you that the Adobe Flash plugin has been successfully installed.
Also check the Adobe Flash Player test page
Installing the plugin on Chrome
Follow all of the instructions above. Then:
- create a Chrome plugin folder: su -c 'mkdir /opt/google/chrome/plugins' - on 32-bit, create a symbolic link that tells Chrome how to find the 32-bit plugin: su -c 'ln -s /usr/lib/mozilla/plugins/libflashplayer.so /opt/google/chrome/plugins/libflashplayer.so' - on 64-bit, create a symbolic link that tells Chrome how to find the 64-bit plugin: - run Mozilla Firefox once so that it creates /usr/lib64/mozilla/plugins-wrapped/nswrapper_32_64.libflashplayer.so su -c 'ln -s /usr/lib64/mozilla/plugins-wrapped/nswrapper_32_64.libflashplayer.so /opt/google/chrome/plugins/nswrapper_32_64.libflashplayer.so'
- Exit all Chrome windows and restart Chrome.
- In the Chrome address bar, type “about:plugins” to check whether the plugin loaded. You may have to re-run Chrome with the –enable-plugins command line switch to force Chrome to re-scan its plugins folder.
Source: http://fedoraproject.org/wiki/Flash#Third_Party_Repository
How to mount extend/LVM partition with Knoppix
- Burned a ADRIANE-KNOPPIX LiveCD – ADRIANE-KNOPPIX_V6.4.3CD-2010-12-20-EN
(it has lvm-tools available)
- Booted the PC with ADRIANE-KNOPPIX Live CD
- Started a Terminal

Secure Password Creation Methodology
There are many methods that people use to create secure passwords. One of the more popular methods involves acronyms. For example:
• Think of an easily-remembered phrase, such as:
“over the river and through the woods, to grandmother’s house we go.”
• Next, turn it into an acronym (including the punctuation).
otrattw,tghwg.
• Add complexity by substituting numbers and symbols for letters in the acronym. For example, substitute 7 for t and the at symbol (@) for a:
o7r@77w,7ghwg.
• Add more complexity by capitalizing at least one letter, such as H.
o7r@77w,7gHwg.
• Finally, do not use the example password above for any systems, ever.
While creating secure passwords is imperative, managing them properly is also important, especially for system administrators within larger organizations. The following section details good practices for creating and managing user passwords within an organization.


