LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Advisory Watch: August 15th, 2014
Linux Advisory Watch: August 8th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
Configuring the kernel

3. Configuring the kernel

In order to use Cryptoloop, you need to activate a few kernel options. You have the option to either compile these requirements as modules or compile them directly into the kernel. The following steps enable them as modules. If you are not familiar with building a 2.6 kernel, you should refer to the Linux Kernel HOWTO. The following instructions just give the minimal steps.

  1. Go to the directory that holds your kernel source tree (usually /usr/src/linux/) and start the configuration:

    make menuconfig
  2. Enable general loop device support. Active "Loopback device support" under:

    Device Drivers -> Block Devices -> Loopback device support
  3. Enable Cryptoloop support in the same section. The option should show up as soon as you enable general loopback support.

  4. Enable the cryptographic API by going to "Cryptographic options" from the main menu. You can safely enable most algorithms here. I would recommend that you enable the following:

    
    -- Cryptographic API
         <*>   HMAC support  
         < >   Null algorithms
         <*>   MD4 digest algorithm
         <*>   MD5 digest algorithm
         <*>   SHA1 digest algorithm
         <*>   SHA256 digest algorithm
         <*>   SHA384 and SHA512 digest algorithms
         <*>   DES and Triple DES EDE cipher algorithms
         <*>   Blowfish cipher algorithm
         <*>   Twofish cipher algorithm
         <*>   Serpent cipher algorithm 
         <*>   AES cipher algorithms
         <*>   CAST5 (CAST-128) cipher algorithm
         <*>   CAST6 (CAST-256) cipher algorithm 
         <*>   Deflate compression algorithm
         < >   Testing module
            

    If you decide to make them as modules, make sure you load the appropriate modules (cryptoloop, aes, etc.) at startup before you continue.

  5. Make your kernel and modules and install them. For example, if you are using lilo on a x86 machine, this can be done like this:

    
     make
         make modules_install
         cp arch/i386/boot/bzImage /boot/kernel-2.6.1
         lilo
            
  6. Load the required modules at startup. This is handled differently on the various distributions. For example, on Gentoo these modules can be added to /etc/modules.autoload/kernel-2.6. If you have compiled Cryptoloop as a module, it will have to be loaded first. It will automatically load the basic loop device module as well. You can manually load the module with:

    modprobe cryptoloop
    
Partner

 

Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Moving toward smart and secure continuous software delivery
Stealthy, Razor Thin ATM Insert Skimmers
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2014 Guardian Digital, Inc. All rights reserved.