Wednesday, March 25, 2009

WAS 6.1 Application/Portal Developer


WebSphere Application Server 6.1 Portal Developer

DUTIES AND RESPONSIBILITIES

1. Expert level knowledge in WebSphere, WebSphere Portal, LDAP schema,
strong Java, J2EE and Struts are required.

2. Solid experience in Servlets, Web Services, SOAP, XML, Java Beans
and JSP is highly preferred.

3. This role designs, develops and supports application solutions to
meet client requirements delivered through a WebSphere Portal based intranet.

4. The successful candidate will have a strong understanding of Portlet
technologies and have practical hands-on experience developing and
delivering JSR 168 Portlet solutions and J2EE Applications.

5. He/She will design, develop and/or re-engineer highly complex
application components, and integrate software packages, programs
and reusable objects potentially residing on multiple platforms.

6. This role will also manage the WebSphere Portal environment
and mentor junior developer.


ESSENTIAL DUTIES AND RESPONSIBILITIES

1. Design/Develop/Maintain IBM WebSphere Portal solutions using JAVA,
J2EE, XML, EJB, JSP, JDBC, Struts framework, CSS, Javascript using
IBM WebSphere Studio Application Developer (WSAD) IDE.

2. Almost all solutions will be developed using IBM WebSphere and JSR168 Portlets.

3. Strong experience developing Multi-tier application architecture applications.

4. Manage IBM WebSphere and WebSphere Portal environment including, upgrades,
monitoring, security & deployment.

5. Maintain, develop and update the structured Portal Intranet framework
(security implementation, design, layout, graphical content and navigation.

6. Troubleshoots system problems and provides timely resolutions.

7. Maintain, develop and update J2EE Tomcat\MySQL solutions.

8. Supports end-users in the use of deployed portal applications as necessary.

9. Application training and usage documentation required.

10. Identify emerging technologies that can be leveraged in the framework.

11. Mentor others in emerging J2EE and/or IBM Portal and related technologies.

12. Effectively communicate new technology concepts to other team members
and capability of mentoring others.

13. Communicate project status and escalating issues to management as needed

14. Provide extensive input to the architectural design of projects and provide
expertise to project teams and ensure adherence to established architectural
standards and principles

15. Provide detailed system design documentation and deliverables, such as
functional requirements, technical specifications, architecture diagrams,
UML diagrams, sequence diagrams, component and deployment diagrams,
class diagrams, data models, process flows, use cases, and
navigation maps as required

Friday, March 20, 2009

Data Recovery Using FreeNAS

Data Recovery Using FreeNAS
Posted by FrugalNYC at 6:00 AM | Labels: backup, freenas, system admin, tech support

I have written several posts about FreeNAS in the last several weeks. For such a small and compact OS, I have found this to be one of my favorite tools of late. I first wrote about 9 Great Things About FreeNAS and then I wrote 9 Reasons To Use FreeNAS At Work. I then wrote 11 FreeNAS Tips that I picked up after using it and reading about it for several weeks.

Today I would like to talk about how FreeNAS can be used as a data recovery tool. Below is my account of how I used the FreeNAS LiveCD to restore data from a Windows Laptop. I've done this on a HP/Compaq Windows XP Laptop and it worked very well.

Bootup and Install

* I Boot up with the LiveCD.
* Configure the IP address via DHCP
* I go to another machine for the WebGUI to do additional configuration.
* From the WebGUI, I login with the default admin/freenas account.
* Then I setup the Disks - steps are below.



Adding the Disk I want to Recover

* Disks - Management - Add Choose the Disk.
* In My case it was the acd4, the only other one being a RAM Disk or CDROM Drive (acd0)
* I give the description as HD (Hard Disk)
* I leave everything else default, but I do change the Preformatted File system to NTFS
* Save the changes



Mount the Disk

* Disks - Mount Point - Management - Add mount point
* I Choose the Disk I configured above
* I chosse partition 1, since I know the Laptop only has one primary partition.
* Filesystem: I choose NTFS
* Sharename: I call it Windows. You can call it anything you want.
* I leave everything else as the default.
* save the changes.



Get to the Files

* For the easiest access to files I setup the FTP service.
* I go to Services - FTP
* I click enable and then Save and Restart.
* From windows explorer (on the machine I did the WebAdmin work and where I want the data restored to) I go to the folder ftp://freenasIP
* I see the files from my windows install and grab whatever files I need to backup.



Shutdown the Laptop

* When Done copying, I just shutdown the system.
* System - Shutdown


Voila! Now you know how to use FreeNAS as a data recovery tool. There are other dedicated recovery tools, such as SystemRescueCD, but I find FreeNAS very easy to setup and it gives me the results I want faster. Do you use FreeNAS? What features do you like best? Share your thoughts and comments. You can get the current iso of FreeNAS here. Do you have other useful resources for FreeNAS?


ADDITIONAL:
1. http://developer.novell.com/wiki/index.php/HOWTO:_Install_FreeNAS
2. http://pcwizcomputer.com/index.php?option=com_content&task=view&id=71&Itemid=47



For additional links to frugal tips and tricks follow me on Twitter. If you would like to contribute to FrugalNYC or FrugalTech in any way (guest posts, articles, ideas, interesting links, advice, financial assistance, or anything else), feel free to contact me via email. Click here to add this to your RSS reader or Subscribe to FrugalTech by Email.
Monday, March 2, 2009
Reactions:
4 comments:

Brian said...

Cool. It seems so obvious after hearing this, but I probably would have never thought of using my LiveCD for this!
March 2, 2009 9:33 AM
FrugalNYC said...

Hi Brian,

It pays to get a little creative huh? Technically, just about all LiveCD distros of Linux/BSD can be used to do simple data recovery work. I just find FreeNAS to be one of the easiest to use in this regard. :) Thanks for visiting and reading FrugalTech posts.
March 2, 2009 10:46 AM
ravi said...

nice post

to knew more about data recovery you must visit

www.ravi-datarecovery.blogspot.com
March 8, 2009 12:19 AM
FrugalNYC said...

Hi Ravi,

Thanks. I've added you to the blogroll. Good resource for data recovery.
March 10, 2009 9:51 AM

Post a Comment

Thursday, March 19, 2009

Video Hosting - Fedora 5 Server Configuration (Optimized for Dedibox servers)


Video Hosting - Fedora 5 Server Configuration (Optimized for Dedibox servers)
I found it quite hard to get up to date information on how to configure properly a video hosting server on Fedora.

Here is a quick tutorial to tell you every single step I used after setting up my server with fedora core 5 (bordeaux). My hosting provider is Dedibox. It is designed for beginners to follow the step by step; but advanced users will surely know which steps to skip !

This will help you installing:

* Fmpeg (http://ffmpeg.mplayerhq.hu)
* FFmpeg-PHP (http://ffmpeg-php.sourceforge.net)
* Mplayer + Mencoder (mencoder is now built into the mplayer svn release )
(http://www.mplayerhq.hu/design7/dload.html)
* flv2tool (http://inlet-media.de/flvtool2)
* LAME MP3 Encoder (http://lame.sourceforge.net)
* Libogg + Libvorbis (http://www.xiph.org/downloads)



Table of contents

* Requirements

* 1-click Setup

* Setup explained



REQUIREMENTS

First, here are all the packages I needed on my fresh FRESH INSTALL of FC5

yum install subversion
y
yum install ruby
y
yum install gcc
y
yum install ncurses-devel
y
yum install gcc-c++
y
yum install php*dev*
y


You'll need the Livna repository to install mplayer so let's set it up now:

vi /etc/yum.repos.d/livna.repo


Then in Vi, press the key "i" and copy and paste this:

[livna]
name=Livna for Fedora Core $releasever - $basearch - Base
baseurl=http://rpm.livna.org/fedora/$releasever/$basearch
http://livna.cat.pdx.edu/fedora/$releasever/$basearch
http://wftp.tu-chemnitz.de/pub/linux/livna/fedora/$releasever/$basearch
http://ftp-stud.fht-esslingen.de/pub/Mirrors/rpm.livna.org/fedora/$releasever/$basearch
#mirrorlist=http://rpm.livna.org/mirrorlist
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-livna

[livna-testing]
name=Livna for Fedora Core $releasever - $basearch - Testing
baseurl=http://rpm.livna.org/fedora/$releasever/$basearch/RPMS.lvn-testing
http://livna.cat.pdx.edu/fedora/$releasever/$basearch/RPMS.lvn-testing
http://wftp.tu-chemnitz.de/pub/linux/livna/fedora/$releasever/$basearch/RPMS.lvn-testing
http://ftp-stud.fht-esslingen.de/pub/Mirrors/rpm.livna.org/fedora/$releasever/$basearch/RPMS.lvn-testing
#mirrorlist=http://rpm.livna.org/mirrorlist-testing
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-livna


Save your file by pressing "esc" and:

:wq


Once Vi exited let's import the GPG Key for this repository:

wget rpm.livna.org/RPM-LIVNA-GPG-KEY
rpm --import RPM-LIVNA-GPG-KEY
rm -rf RPM-LIVNA-GPG-KEY



1-click SETUP (just copy and paste)

cd /usr/local/src
wget http://www3.mplayerhq.hu/MPlayer/releases/codecs/all-20061022.tar.bz2
wget http://rubyforge.org/frs/download.php/17497/flvtool2-1.0.6.tgz
wget http://easynews.dl.sourceforge.net/sourceforge/lame/lame-3.97.tar.gz
wget http://switch.dl.sourceforge.net/sourceforge/ffmpeg-php/ffmpeg-php-0.5.1.tbz2
wget http://downloads.xiph.org/releases/ogg/libogg-1.1.3.tar.gz
wget http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.tar.gz
tar -xjf all-20061022.tar.bz2
tar -xzf flvtool2-1.0.6.tgz
tar -xzf lame-3.97.tar.gz
tar -xjf ffmpeg-php-0.5.1.tbz2
tar -xzf libogg-1.1.3.tar.gz
tar -xzf libvorbis-1.2.0.tar.gz
mkdir /usr/local/lib/codecs/
svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg
mv /usr/local/src/all-20061022/* /usr/local/lib/codecs/
chmod -R 755 /usr/local/lib/codecs/
mkdir /usr/local/src/tmp
chmod 777 /usr/local/src/tmp
export TMPDIR=/usr/local/src/tmp
cd /usr/local/src/lame-3.97
./configure
make && make install
cd /usr/local/src/libogg-1.1.3
./configure && make && make install
cd /usr/local/src/libvorbis-1.2.0
./configure && make && make install
cd /usr/local/src/flvtool2-1.0.6/
ruby setup.rb config
ruby setup.rb setup
ruby setup.rb install
yum install mplayer
y
cd /usr/local/src/ffmpeg/
./configure --enable-libmp3lame --enable-libvorbis --disable-mmx --enable-shared
make
make install
ln -s /usr/local/lib/libavformat.so.50 /usr/lib/libavformat.so.50
ln -s /usr/local/lib/libavcodec.so.51 /usr/lib/libavcodec.so.51
ln -s /usr/local/lib/libavutil.so.49 /usr/lib/libavutil.so.49
ln -s /usr/local/lib/libmp3lame.so.0 /usr/lib/libmp3lame.so.0
ln -s /usr/local/lib/libavformat.so.51 /usr/lib/libavformat.so.51
cd /usr/local/src/ffmpeg-php-0.5.1/
phpize
./configure
make
make install
echo ‘extension=/usr/local/lib/php/extensions/no-debug-non-zts-20020429/ffmpeg.so’ >> /etc/php.ini
service httpd restart

SETUP EXPLAINED

Download needed packages and unpack them:

cd /usr/local/src
wget http://www3.mplayerhq.hu/MPlayer/releases/codecs/all-20061022.tar.bz2
wget http://rubyforge.org/frs/download.php/17497/flvtool2-1.0.6.tgz
wget http://easynews.dl.sourceforge.net/sourceforge/lame/lame-3.97.tar.gz
wget http://switch.dl.sourceforge.net/sourceforge/ffmpeg-php/ffmpeg-php-0.5.1.tbz2
wget http://downloads.xiph.org/releases/ogg/libogg-1.1.3.tar.gz
wget http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.tar.gz
tar -xjf all-20061022.tar.bz2
tar -xzf flvtool2-1.0.6.tgz
tar -xzf lame-3.97.tar.gz
tar -xjf ffmpeg-php-0.5.1.tbz2
tar -xzf libogg-1.1.3.tar.gz
tar -xzf libvorbis-1.2.0.tar.gz
svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg


Install Mplayer codecs

mkdir /usr/local/lib/codecs/
mv /usr/local/src/all-20061022/* /usr/local/lib/codecs/


Secure TMP folder

chmod -R 755 /usr/local/lib/codecs/
mkdir /usr/local/src/tmp
chmod 777 /usr/local/src/tmp
export TMPDIR=/usr/local/src/tmp


Install Lame

cd /usr/local/src/lame-3.97
./configure
make && make install


Install Ogg

cd /usr/local/src/libogg-1.1.3
./configure && make && make install


Install Vorbis

cd /usr/local/src/libvorbis-1.2.0
./configure && make && make install


Install FLVtools

cd /usr/local/src/flvtool2-1.0.6/
ruby setup.rb config
ruby setup.rb setup
ruby setup.rb install


Install Mplayer

yum install mplayer


Install FFMpeg

cd /usr/local/src/ffmpeg/
./configure --enable-libmp3lame --enable-libvorbis --disable-mmx --enable-shared
make
make install
ln -s /usr/local/lib/libavformat.so.50 /usr/lib/libavformat.so.50
ln -s /usr/local/lib/libavcodec.so.51 /usr/lib/libavcodec.so.51
ln -s /usr/local/lib/libavutil.so.49 /usr/lib/libavutil.so.49
ln -s /usr/local/lib/libmp3lame.so.0 /usr/lib/libmp3lame.so.0
ln -s /usr/local/lib/libavformat.so.51 /usr/lib/libavformat.so.51


Install FFMpeg-PHP

cd /usr/local/src/ffmpeg-php-0.5.1/
phpize
./configure
make
make install


Add the FFMpeg extension in php.ini and restart httpd.

echo ‘extension=/usr/local/lib/php/extensions/no-debug-non-zts-20020429/ffmpeg.so’ >> /etc/php.ini
service httpd restart


Posted by Romain at 01:29
Labels: Tutorials

Wednesday, March 18, 2009

Getting a feel for the network with ‘netstat’


It seems that my previous article, “Getting a feel for the network
with ’ss’” was pretty popular. ss is a great tool but isn’t always
part of a base install for your favorite version of Linux. With
that in mind, let’s talk about how to do some things with tools
that are more likely to be part of the base. This time we will
discuss netstat and next time we will cover just the tip of the
iceberg that is lsof.

Our tricks for the day:

* Get a list of active TCP connections

* Get a list of active TCP connections and resolve hostnames of IP addresses in question

* Get a list of listening TCP sockets

* Get a list of TCP connections in various other connection states

First netstat:

Get a list of TCP connections (in this case, we include “listening” TCP ports):

$ netstat -ant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 1 192.168.253.101:52812 74.52.160.50:80 FIN_WAIT1
tcp 509792 0 192.168.253.101:49200 38.119.55.141:80 ESTABLISHED
tcp 0 1 192.168.253.101:52813 74.52.160.50:80 FIN_WAIT1
tcp 0 0 :::22 :::* LISTEN

As before, except this time resolve the IP addresses in question:

$ netstat -at
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost:ipp *:* LISTEN
tcp 509792 0 chaco.local:49200 rieko.ziaspace.com:www ESTABLISHED
tcp 0 0 *:ssh *:* LISTEN

In the previous commands we showed active TCP connections but also TCP
ports that were in the “listening” state. If you are messing with
netstat and lsof then you are probably at least somewhast familiar
with IP networking but, if not, listening basically means that some
process is ready to accept new connections on that port.

In this command we are going to show only TCP ports that are in the
listening state and not active TCP connections. Note that, as in my
previous article, the only processes listening for new connections
on my workstation are the SSH and CUPS daemons.

$ netstat -tl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost:ipp *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN

Now for our final netstat trick, we are going to list all of the TCP
connections where a TCP SYN packet has been sent but the receiving end
has not yet replied. See Wikipedia for more information about the TCP
handshake. I’ve fired up a Gnutella client so that we have lots of
interesting TCP connections in the output:

$ netstat -tl | grep SYN
(Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.)
tcp 0 1 192.168.253.101:59227 142.217.112.185:2729 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:36291 74.193.252.111:37998 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:36874 12.210.29.230:53781 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:35878 69.245.72.170:2500 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:33314 24.94.77.8:50345 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:43488 24.238.218.203:1334 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:53485 24.95.79.143:1128 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:60224 69.133.19.41:24536 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:52441 72.51.246.127:4379 SYN_SENT 7542/gtk-gnutella
tcp 0 1 192.168.253.101:57700 70.80.99.180:23112 SYN_SENT 7542/gtk-gnutella

Okay, that’s it for today. If you want to do some extra credit then I suggest
looking at the ‘-p’ flag for netstat.

Job Description Senior Consultant


Brief Description:
Senior Consultant is responsible for evaluating existing
systems and/or new user needs for the enterprise spatial
data operations, data governance, and data related service
offerings

Complete Description:
1. Fulfillment of geospatial service catalog offerings,
development of solution proposals and tracking of
service delivery schedules in order to meet/exceed
customer commitments

2. Manages and coordinates the spatial data architecture.
Work involves coordinating with agency spatial data
stewards, creation of processes, workflow diagrams,
step-by-step user guides for agency data stewards to
update/maintain their own data located in the
staging/production environments, resolution of
spatial data issues

3. Leads and fulfills data governance action items
Data structure changes impacting enterprise web applications
Maintenance of spatial data dictionary to communicate spatial data holdings
Development of data sharing agreements

4. Development of monthly statistics for the
geospatial service offerings and monthly
reporting to the CTO Dashboard

5. Management of enterprise contracts, renewals
and product deliverables

6. Project management of the State GIS Clearinghouse

7. Weekly tracking and monitoring of GTO/ESF projects
(i.e. data infrastructure upgrade), requests and
action items, signoffs, and facilitation with ESRI
for help desk support

8. Other geospatial operations supported by this
position include change management and standard
operating procedures

Tuesday, March 17, 2009

Install VMware-server-1.0.7 in Fedora 10


1. Check the Linux version
--------------------------
[root@localhost modules]# uname -a
Linux localhost.localdomain 2.6.27.19-170.2.35.fc10.x86_64 #1 SMP Mon Feb 23 13:00:23 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

2. Check the VMWare server installed
------------------------------------
[root@localhost modules]# rpm -qa | grep VM
VMware-server-1.0.7-108231.i386
[root@localhost modules]#

3. Download the path for kernerl 2.6.27
---------------------------------------
http://www.insecure.ws/warehouse/vmware-update-2.6.27-5.5.7-2.tar.gz

Thursday, March 5, 2009

Verifying the integrity of nmap-4.76.tar.bz2 downloads


1. Download the NMap Signing Key
[root@localhost gpg_test]# wget http://nmap.org/data/nmap_gpgkeys.txt
--2009-03-05 12:40:40-- http://nmap.org/data/nmap_gpgkeys.txt
Resolving nmap.org... 64.13.134.48
Connecting to nmap.org|64.13.134.48|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4975 (4.9K) [text/plain]
Saving to: `nmap_gpgkeys.txt'

100%[======================================>] 4,975 --.-K/s in 0.1s

2009-03-05 12:40:40 (46.2 KB/s) - `nmap_gpgkeys.txt' saved [4975/4975]

2. Import the Signing Keys using PGP
[root@localhost gpg_test]# gpg --import nmap_gpgkeys.txt
gpg: key 6B9355D0: "Nmap Project Signing Key (http://www.insecure.org/)" not changed
gpg: key 33599B5F: "Fyodor " not changed
gpg: Total number processed: 2
gpg: unchanged: 2

3. Verifying the Nmap and Fyodor PGP Key Fingerprints
[root@localhost gpg_test]# gpg --fingerprint nmap fyodor
pub 1024D/6B9355D0 2005-04-24
Key fingerprint = 436D 66AB 9A79 8425 FDA0 E3F8 01AF 9F03 6B93 55D0
uid Nmap Project Signing Key (http://www.insecure.org/)
sub 2048g/A50A6A94 2005-04-24

pub 1024D/33599B5F 2005-04-24
Key fingerprint = BB61 D057 C0D7 DCEF E730 996C 1AF6 EC50 3359 9B5F
uid Fyodor
sub 2048g/D3C2241C 2005-04-24

4. Verifying PGP key fingerprints (Successful)
[root@localhost gpg_test]# gpg --verify nmap-4.76.tar.bz2.gpg.txt nmap-4.76.tar.bz2
gpg: Signature made Fri 12 Sep 2008 05:03:59 AM EDT using DSA key ID 6B9355D0
gpg: Good signature from "Nmap Project Signing Key (http://www.insecure.org/)"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 436D 66AB 9A79 8425 FDA0 E3F8 01AF 9F03 6B93 55D0

5. View A typical Nmap release digest file
[root@localhost gpg_test]# cat nmap-4.76.tar.bz2.digest.txt
nmap-4.76.tar.bz2: MD5 = 27 8D D2 E8 49 CC 3D BB 94 7D F9 61 A1 AA FF D0
nmap-4.76.tar.bz2: SHA1 = A711 4173 8B45 12B6 D5B3 5EF9 4258 E525 DF30 A586
nmap-4.76.tar.bz2: RMD160 = EC93 522E 05E7 233E 8950 B28A B12B 4535 5E63 C0C7
nmap-4.76.tar.bz2: SHA224 = 4DBB6532 F94D3EDE 6BF900FC 9325FAA4 ADE46765
0B44D56C A2B7E136
nmap-4.76.tar.bz2: SHA256 = 4E24328C A6EC97AF B2A8CAF3 12B1F111 A15CF417
63A5AC41 E7A633FD B217D66D
nmap-4.76.tar.bz2: SHA384 = 17B27C42 12664066 D7E32A44 8EDC7D84 04AC23A2
6F6AD443 BCEA9114 F9F9A422 BC32C857 AF7B300B
5E11EF53 47C91975
nmap-4.76.tar.bz2: SHA512 = B1E04ED7 521744C0 090E1A30 81ED524A 7B3B1287
2090B064 D80E325E 4C5D273F 76FAE899 B28ECDBF
6E300D19 203EBE1D FDE6F3CA BDEAB7E7 6FDCCBB4
6139167E

6. Verifying Nmap hashes using md5sum
[root@localhost gpg_test]# md5sum nmap-4.76.tar.bz2
278dd2e849cc3dbb947df961a1aaffd0 nmap-4.76.tar.bz2

7. Verifying Nmap hashes using sha1sum
[root@localhost gpg_test]# sha1sum nmap-4.76.tar.bz2
a71141738b4512b6d5b35ef94258e525df30a586 nmap-4.76.tar.bz2

8. Verifying Nmap hashes using gpg
[root@localhost gpg_test]# gpg --print-md sha1 nmap-4.76.tar.bz2
nmap-4.76.tar.bz2: A711 4173 8B45 12B6 D5B3 5EF9 4258 E525 DF30 A586

Programmer Analyst


Job Description of A Programmer Analyst
---------------------------------------
1. Plans, develops, tests, and documents computer programs, applying knowledge
of programming techniques and computer systems.
2. Evaluates user request for new or modified program. Consults with user to
identify current operating procedures and clarify program objectives.
3. Formulates plan outlining steps required to develop program, using
methodologies such as structured analysis and design or object-oriented
development.
4. Captures requirements using industry standard development frameworks and
tools.
5. Designs reports, forms and letters along with computer terminal screen
displays to accomplish goals of user request.
6. Reviews screens, reports, forms and letters designs with users.
7. Converts project specifications, using industry standard tools, such as
object-oriented tools, into sequence of detailed instructions and logical
steps for coding into language processable by computer, applying knowledge
of computer programming techniques and computer languages.
8. Enters program codes into computer system.
9. Enters commands into computer to run and test program.
10. Reads computer printouts or observes display screen to detect syntax or
logic errors during program test, or uses diagnostic software to detect
errors.
11. Replaces, deletes, or modifies codes to correct errors.
12. Analyzes, reviews and alters program to increase operating efficiency or
adapt to new requirements.
13. Writes documentation to describe program development, logic, coding, and
corrections. Writes manual for users to describe installation and operating
procedures.
14. Assists users to solve operating problems.

Monday, March 2, 2009

Spyware Removal guide

Spyware Removal guide

For those that don't know, spyware is bad, spyware is really bad. It also has many different names. Like adware, malware, badware, trojans, worms, downloaders, junkware, etc. Whatever you call it it's bad and you need to know how to get rid of it. The most common method people use to remove spyware is to download some software from Download.com and run that to remove the spyware. This method works ok most of the time but it usually takes much longer than I would ever want to spend on a computer. This spyware removal guide presents a much faster more effective way.

To understand how to deal with spyware you first have to understand how it works. It gets on a computer by attaching itself to, or disguising itself as, some useful piece of software. Kazaa is the classic example of that It is a useful piece of Peer to Peer software but it is packed full of spyware. The first thing that spyware does when it is on a computer is add itself to various parts window's registry so that it will be loaded when windows starts up. So the first thing you need to do is removed these various registry entries so that you can then remove the spyware.

To do this you will need to use some cool software. The first cool software you should use is called msconfig. It is installed standard on Windows XP, Windows ME and Windows 98. It is not included with Windows 2000. Don't ask me why. I always run this right off before I do anything else. To access it all you have to do is click the Start button. Then click on Run and type in "msconfig" and click "ok". You are greeted with the System Configuration Utility. You can disable most start up items by clicking on "Selective Startup" and uncheck "Load Startup Items". If you do this most of the stuff that normally starts up will not start up when you reboot your computer. Then go to the Services tab and Disable all non-Microsoft services. Don't be timid in disabling anything in this utility. There is nothing you can do that will permanently damage Windows because you can always come back to this utility and undo your changes.

After you have ran msconfig I would reboot the computer into safe mode. You can do this by pressing "F8" while windows is starting up. Sometimes it hard to know when to do this. It's after your computer goes out of the bios and boots off the hard drive you should press F8. If in doubt repeatedly press F8 while the computer is starting up. The advantage of being in safe mode is that none but the cleverest Spyware is loaded in Safe Mode. In safe mode it is time to try the powerful program known as HiJackThis.exe. HiJackThis functions like msconfig but it is much more thorough at finding possible spyware problems. The rule to follow when using HiJackthis is, "If you don't know what it is get rid of it." When you run a scan with HiJackThis you will be presented with a list of possible spyware found in the registry. Keep in mid that it is possible spyware, just because it is there it doesn't mean it is bad. Most of the stuff listed here will be extensions to Internet explorer and stuff like that. Everything listed is optional. Your computer will work perfectly fine even if you removed everything listed. Once you check those things that you want to remove and you click "Fix Checked", restart your computer in normal mode and you should have about 90% of your spyware removed.

To find out if you have successfully removed all the spyware, start HiJackThis again and do a scan. If you find anything listed that you had previously removed that means that the spyware is still on your computer somewhere and has come back to plague your existence. At this point it is hard to give you an exact procedure on how to remove the remaining spyware. Probably the easiest thing to do is download a good spyware scanner and run that. You can see a list of the ones I recommend at the Spyware Scanners page. If the spyware scanners still fail to remove the spyware than you'll have to find a more involved procedure. A sure fire method of removing a known spyware file is by booting into an entirely different operating system and manually deleting it.

When you ran HiJackThis you probably noticed a file name associated with. This is most likely the file that is run when windows starts up that activates the evil spyware process. If you thought, "I'll just delete this file." It would be a great idea but if you tried to do so you probably came across the error, "Access Denied, file may be in use" or something like that. Don't ask me why but Windows is unable to delete a file if it is in use. There is absolutely no reason why this has to be the case. I have no problems deleting executables of running processes in Linux. Anyway, to delete this file you need to boot the computer from a different medium, the most convenient is probably a CD. The best type of bootable CD for spyware removal purposes is probably Bart's PE. You can find information on how to build a bootable CD with windows XP and spyware removal tools here.

If you took a look at that you probably noticed that it was a rather complicated procedure. It is quite possible that you already have a boot CD that will do what you need to do. If you have a windows Installation CD you could boot from it and then press 'r' to enter the recovery console. Sometimes it will ask you for your administrator password. If you don't know it try just pressing enter. If that doesn't work see Windows Password Recovery Guide for information on how to reset administrator passwords. Once you are presented with a prompt you can issue DOS commands like, "del /Path/to/file/filename.exe" to remove the offending file that you found with HiJackThis.exe (you did wright that file name down, right?).

Hopefully this spyware removal guide has helped you get your computer working as good as the day you purchased it. Of course this all would have been avoided if you had just used Linux. Don't forget to check out Spyware prevention once you get all the spyware removed.

Copyright © 2007–2009 by NNU Computer Whiz. All rights reserved.

Process text file of Book titles from B&N

Process the text file using this script