The middle section of the below .htaccess file switches to https if the request URI begins with /dev and works.

The last section of the file works as well but does not work properly with the https redirect.

I basically want to be able to type http://www.namhuy.org/dev/some_sub_dir/ and be redirected to https://www.namhuy.org/dev/some_sub_dir/ and prompted for the http auth username and password.

What currently happens is if I go to http://www.namhuy.org/dev/some_sub_dir/ I get prompted for a username and password over port 80, and then immediately get prompted again over port 443. So my credentials are being sent twice, once in the clear, and once encrypted. Making the whole https url rewrite a little pointless.

The reason for doing this is so that I won’t be able to accidentally submit my user/pass over http; https will always be used to access the /dev directory.

Create a file /etc/httpd/conf.d/test.conf with:

<Directory “/var/www/html/dev”>
#
# force HTTPS
#
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
</Directory>

…and then adding the following inside /etc/httpd/conf.d/ssl.conf just above the </VirtualHost> tag:

<Directory “/var/www/html/dev”>
#
# require authentication
#
AuthType Basic
AuthName “Please Log In”
AuthUserFile /var/www/auth/passwords
Require valid-user
</Directory>

rpm -Uvh http://bit.ly/q7kHBq

NoteThe full link for the RHEL 6 EPEL package and the links for the lower versions of RHEL are provided below. The rpm command prior to RHEL 6 cannot handle http redirects so no bit.ly links have been provided.

http://download.fedora.redhat.com/pub/epel/6/i386/epel-release-6-5.noarch.rpm

http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm

http://download.fedora.redhat.com/pub/epel/4/i386/epel-release-4-10.noarch.rpm

yum repolist2. Verify the installation using the command below. You should see epel in the output.

yum repolist

install yum priorities3. Install the Yum priorities package using the command below.

yum install yum-priorities

edit epel.repo4. Edit the file /etc/yum.repos.d/epel.repo and add the line below under the [epel] section.

priority=10

yum check update5. Test your configuration using the command below. You should see a priority protections message in the output.

yum check-update

• Proper configuration
• Updates
• Reading materials
• Frequent penetration tests
• Monitoring and logging
• Experience with advanced configurations

Zone-h archives

All operating systems have vulnerabilities.  And yes Apple, Microsoft and Linux is only as safe as the end user.

sudo apt-get install curl libcurl3 libcurl3-dev php5-curl

After installing libcurl you should restart the web server with following command,

sudo /etc/init.d/apache2 restart

If you don’t have LAMP functionality already installed, then please click on the following link to find out how install LAMP on Ubuntu Linux,

Install Time Zone
1 $sudo aptitude install tzdata
2 $dpkg-reconfigure tzdata
3 $sudo vim /etc/ntp.conf

Add NTP server
1 driftfile /var/lib/ntp/ntp.drift
2 server 0.pool.ntp.org
3 server 1.pool.ntp.org
4 server 2.pool.ntp.org
5 server pool.ntp.org

Manually update the time by “$sudo ntpdate pool.ntp.org”

SEVERE: Error initializing endpoint
java.net.BindException: Address already in use:8080

Means you will to change tomcat’s port, here is how to do, go to
$CATALINA_HOME/conf/server.xml

change

<connector port:8080

to

<connector port:8083

If you running in multiple catalina services, you should create new shell script and include different $CATALINE_HOME and $CATALINA_BASE into it

First, check on your $CATALINA_HOME/conf/server.xml

You’ll end up with a file called installed-software. Copy the file to a usb key and copy it to a location on your backtrack machine.
Run: “dpkg –set-selections < installed-software” in the directory where you copied the file installed-software.
Finally the “sudo apt-get dselect-upgrade” commands completes all of this. Be aware that is might take while until the installtion finishes.

If the above doesn’t work, you probably do not have dselect installed.
In that case, run “apt-get install deselect”
The above instructions also work on BackTrack 5

In linux systems this “linking” process is called “symlinking” (softlinking) or “hardlinking.” The difference between the two is a little subtle and can be understood in that unix files have two parts the “file header” (which includes the name) and the “data” part. The header part contains the file name, permissions, etc, and also contains an inode number. This inode number is like the data part’s address on the hard drive…and points/associates the file name to the data it contains. One way to think about it is through this schematic:

You can imagine that linking to the file can be accomplished through one of two methods. One method is to simply have two filenames associated with the same inode. These two filenames (file header information) can reside in different physical locations on the hard disk and thus in two different locations in your folder tree of your computer. This process is called “hardlinking” and looks like this:

Hardlinking is great. If you delete filename1, filename2 still has the data stored in itself even though the file was originally created with filename1. Dropbox supports this linking feature. The only drawback to this kind of linking is that the link literally looks like and feels like the file in any file system–you can’t really tell the difference. So you better remember what was supposed to be the link! The filename doesn’t show up as a link because it has the same properties as a normal file… file header information (stored in the filename1, including the inode number), which links to the data.

Through command line, the way you create one of these hardlinks is through the following command:

ln file-to-be-linked.txt linking-file-name.txt

Now, the other way of linking files is a literal link: its a special unique file that has a file header portion with an inode link, but instead of that inode pointing straight to the file data inode, it points to the inode of its own file within which contains a “link” to the file you’re linking too. It’s much like a shortcut in Windows…and this is called soft-linking, or forming a symbolic link or “symlink.” It works in the following manner:

Obviously that “to.txt” file is the file header information that contains the inode number of where the data actually resides…so soft links are literally a special file that points to another file and the operating system treats it as such…its obvious that its a link and if you delete the symlink it just no longer points to the file anymore. And if you delete the original file and the symlink still links to it, the data is lost…it is not kept.

To access this kind of linking in the command line, you run the following command:

ln -s file-to-be-linked.txt name-of-link-to-file

Notice how I dropped the file extension off of the name of the link…you can do that because it is its own type of file that just points to the real thing. Dropbox also supports this kind of file linking. And it comes in handy particularly if you want the file to show up as a symlink.

Now you might be asking yourself why bother with the soft linking if hard linking works so well? The answer might be baffling: all directories in unix/linux systems are soft links that contain a name and point to a data file that contains all the file header information location of all the files associated with that directory. I mean, what are folders anyways? They aren’t “files” in that they don’t have data intrinsic to themselves. But they are “containers” that tell you what is associated with them. Brilliant? Yes. Immediately intuitive? No.

So a “directory” or “folder” has its own file header information which points to an inode number that contains all the addresses of all the files associated with itself. When you go to one of these addresses of the contained files you get pointed to the inode that contains all the data associated with that file. That’s how folders work–and if you want to use a symlink to point to a directory, you have to add a special flag to the linking command:

ln -sd directory-to-be-symlinked name-of-link

Of course, you can also hardlink a directory, then the code would just be:

ln -d directory-to-be-hardlinked name-of-link

I think I mostly use symlinking so I remember its a link and not the actual file, but I’m very appreciative that Dropbox supports this option. Makes changing files in different directories on my computer remotely very easy to do!

1. First download apache tomcat 7 linux version zipped file, then extract it.

2. now u place the tomcat wherever you like using following command

sudo mv apachetomcat /usr/local/tomcat

3. make *.sh file executable inside /usr/local/tomcat/bin folder

sudo chmod +x *.sh

make sure you are inside the /usr/local/tomcat/bin folder..

4. you can install open jdk and jre or sun jdk and jre.

define JAVA_HOME path in .bashrc file or /etc/environment file

export JAVA_HOME=/usr/lib/jvm/sun-java-jdk…in my case..check yours

5. now write the script to run the tomcat at startup..

by creating a file tomcat in /etc/init.d directory

sudo nano /etc/init.d/tomcat

after that

in tomcat script file..

write script to start stop and restart

case “$1″ in

start)

sh /etc/local/tomcat/bin/startup.sh

;;

stop)

sh /etc/local/tomcat/bin/shutdown.sh

;;

restart)

sh /etc/local/tomcat/bin/shutdown.sh

sh /etc/local/tomcat/bin/startup.sh

;;

esac

exit 0

6. to run this tomcat script at startup, you can run this script in rc.local script which runs at startup or rc0 which is run at rebooting or rc6 which runs at shutdown..

for automatic handling by ubuntu,you can run following command

sudo update-rc.d tomcat defaults

it may show some warning message like LSB ..but you can ignore it because it is just a comment to write in any script in standard pattern.

reboot you computer or just login logout, you are ready to run your apache tomcat 7..

issue:: http://localhost:8080

for manager and host manager application of tomcat 7, you need to write following code..

sudo nano /usr/local/tomcat/conf/tomcat-users.xml

That’s all done..

For check..some commands can be useful..

echo $JAVA_HOME

sudo update-alternatives –config java

sudo update-alternatives –config javac

To free pagecache:
echo 1 > /proc/sys/vm/drop_caches

To free dentries and inodes:
echo 2 > /proc/sys/vm/drop_caches

To free pagecache, dentries and inodes:
echo 3 > /proc/sys/vm/drop_caches