Method 1 (Windows 7 Professional / Ultimate Edition)

1. Under “Control Panel”, find “System and Security”
2. Open “Administrative Tools”
3. Double Click “Local Security Policy”
4. Expand “Local Policies”
5. Click “Security Options” and Scroll to find “Network Security: LAN Manager Authentication Level”
6. Choose “Send LM & NTLM, use NTLMv2 session security is negotiated” for the drop down.
7. Done. you can now map network drive as normal (like in XP)

Method 2 (Windows 7 Home Edition)

1. Use notepad and save the snippet below as win7fix.reg

   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
   "lmcompatibilitylevel"=dword:00000002

2. Double click the win7fix.reg you just create to run it
3. Press “Yes” to add that into registry
4. Done. you can now map network drive as normal (like in XP)

ref. http://www.ntnu.no/itinfo/read_article.php?aid=711

# First, let's create a directory for the jail account
mkdir /jail
chown root:root /jail

# Then we create a new user account specially for jail account
# *replace <group name>, <username>, <password> with your own value
groupadd <group name>
useradd -d /home/jail -g <group name> -p <password> <username>

# For example, if we only want to allow the jail account to have ssh and basic shell access
jk_init -v -j /jail basicshell ssh

# Then we shall jail the user account we previously created to the jail directory
jk_jailuser -m -j /jail <username>

Now the jail account and file system is ready, however if you want more control, we can do the following.

# OPTIONAL: Edit /jail/etc/passwd file and /jail/etc/group file to further limit the access
# The following further limit the user logged in jail account to have only access to bash
# Assume the jail user account & group = jail_user, and we edit the passwd file
jail_user:x:1016:1016:/home/jail:/bin/bash

# edit group file
jail_user:x:1016

In order to generate Keystore and Certificate using open SSL, we first need to generate a key

openssl genrsa -out <name of private key file>.key 1024

then we need to generate a Certificate Signing Request by reading the private key we just generated

openssl req -new -key <name of private key file>.key -out <name of csr file>.csr

After that, we could Self-Sign the certificate (note: if you only want the key-cert pair, you could stop after this step, else go to the next step for keystore generation).

openssl x509 -req- days <num of days valid> -in <name of csr file>.csr -signkey <name of private key file>.key -sha1 -out  <name of cert file>.cert

Finally, with the key and certificate, we could combine them into a keystore

openssl pkcs12 -name <key alias> -export -in <name of cert file>.cert -inkey <name of private key file>.key -out <name  of the keystore file>.p12

The key and certificate is ready to be used in various applications (e.g. Dovecot, Apache WebServer…)