“TrueCrypt is not secure,” official SourceForge page abruptly warns
OPEN SOURCE AND THE PROFESSIONAL AUDIO/VISUAL ENVIRONMENT EVENT – 18 JUNE 2014
Room booked – need to discuss details in terms of organisation on the night and publicity to other groups.
- Possible Linux Bier Wanderung meet up, in Talybont on Usk – July. I’ve emailed their group and they are happy for us to come down that Wednesday evening .
Ubuntu has released version 14.04 LTS (Long Term Support) which means the OS will be supported for at least 5 years. Ubuntu 14.04 is available to download from:
A background on LTS, and the roadmap for other Ubuntu releases can be found here:
The Linux operating system has a built-in logging facility. The aim of logging is to log system events, in addition to application events and user events.
Why Log Events?
Having a log of events is very important for the system administrator, in order to troubleshoot errors, system faults and to understand activities performed by a user i.e. last login.
View Log Events
Log events are recorded in /var/logs
If you navigate to this folder using the CLI and ‘ls‘ you will see a number of log files.
messages – This is the generic log file for recording startup events, application events
dmesg – This records kernel messages, including boot up messages, hardware information
boot.log – This records the information that you see when Linux boots
cron – Lists cron job events
To view the above log files simply enter ‘more messages‘ to view the messages log.
Special note: dmesg is also a command i.e. typing ‘dmesg | grep -i usb‘ will return a selected list of event messages containing the keyword USB.
To search the messages for ‘usb’ try the following command:
tail -f messages | grep ‘usb’
Familiarization with the following commands will help you navigate around the various log files:
less, more, cat, tail – use for viewing files at the CLI
grep – a very powerful utility that can be used for pattern matching/text searching
logger – enables the use to log events via the CLI
The above covers the basic principles of Linux logging. These log files underpin IT security monitoring capabilities and used on an enterprise scale. The next articles will cover the use of ‘syslog’ that can be used to harvest log files for intrusion detection.
The terminal under Linux provides a Command Line Interface (CLI) for entering commands to navigate around the file system, perform troubleshooting activities and to execute scripts.
There are many different types of terminals, one of my personal favorites is the ‘Terminator’, which provides advanced layout features and the loading of profiles. If you spend a lot of your time using the CLI, for example I have an IRC application, htop (CPU performance counter), emacs (script editor) and a CLI mp3 player all running in various terminal windows. Using the terminator I can split the main window into different segments, with each segment for its own command/application.
An example is illustrated below:
For Debian OSs (Ubuntu/Crunchbang etc)
sudo apt-get install terminator
sudo yum install terminator
Once installed, run the application ‘terminator’
Split the screen by right click, select vertical or horizontal. When a new screen is created, follow the same process again.
Once the layout is created, right click then choose preferences. A dialog box is displayed, select Layouts tab, select Add to create the layout, and enter a name. For each terminal option you can specify a custom command i.e. top. Click close to save your changes.
To load your terminator layouts simply enter ‘terminator –layout=mylayoutname’
This can be assigned to an application launcher or desktop shortcut, or an alias via the CLI. You could have multiple layouts, maybe one for development/coding, another for personal use.
- HTML5 should soon replace Flash in videos, this article shows how to enable HTML5 for Youtube Videos…
What’s wrong with Flash?
- It’s not an Open Standard
- It requires propriatery Software
- It causes vendor lock-in
- It’s insecure
- It threatens privacy