This time I am showing you how to password protect your Website on a Apache Web Server. The method I am showing you is the recommended way but this is only possible if you have console access to your Apache Web Server. There is another method to protect your web site if you are on a shared web server. Which usually is the situation on web hosting companies where you can buy a domain and web space. I will demonstrated it in a later article. In the video clip below I demonstrate the recommended way.
The Directives below I am using to accomplish the access protection.
Click on the links below and you will get more detailed information regarding the directive.
Turns on Authentications methods, if its set to none it ignores all previous specified limitations or regulations.
With this Directive you can specify a label on the logon dialog.
This Directive specifies the security level basic or digest. If you use a web server with sensitive data you should use digest because it is more secure than basic. For private use you can use basic.
With this directive you have to specify the full path to the user/password file.
With this directive you have to specify the full path to the group file.
This directive specifies who can and has to authenticate. Valid values are user, group and valid-user.
Enjoy the Video Clip and post your Questions or comments here or at youtube.
Building an iSCSI storage device can be very helpful for proof of concepts or actually for production use. I prefer using a Linux Server that provides an iSCSI storage for proof of concept scenarios because real SANs cost a lot of money. iSCSI is the abreviation of Internet Small Computer System Interface and it is an Internet Protocoll (IP). iSCSI is a standard for linking storage facilities.
The iSCSI Enterprise Target is an Open Source project to implement professional iSCSI feature for Linux and provides the iscsitarget software. Ubuntu included iscsitarget package in there repositories and cam be installed with apt-get.
In my demonstration I will make use of a image file which will be the storage device. Storage device is probably not the correct term but best describes its purpose. Usually you will use a logical volume, hard drive or a partition as a block device but it works with image files as well.
Every iSCSI Target defined with an IQN. I copied the definition from Wikipedia.
- iSCSI Qualified Name (IQN)
- Format: The iSCSI Qualified Name is documented in RFC 3720, with further examples of names in RFC 3721. Briefly, the fields are:
- literal iqn
- date (yyyy-mm) that the naming authority took ownership of the domain
- reversed domain name of the authority (org.alpinelinux, com.example, to.yp.cr)
- Optional “:” prefixing a storage target name specified by the naming authority.
- From the RFC:
Naming String defined by
Type Date Auth "example.com" naming authority
+----+ +-----+ +---------+ +-----------------------------+
To enhance the security iSCSI make use of CHAP protocol for authentication and the credentials are not sent in clear text over the wire. In all the iSCSI storage implementation I worked on the iSCSI is been placed in its own VLAN and only accessible for the Servers that utilizes iSCSI SAN Storage like VMware ESX or Citrix Xen server Hosts.
Enjoy the following Youtube Video which demonstrates a simple iSCSI Storage on a Ubuntu Linux Server.