May 21, 2008 in the wee hours
· Filed under CLI, command line, linux, unix
More often nowadays, I found that I need to deal with something ‘foreign’ in unix/linux servers I manage professionally. One thing in particular is an increased number of files whose names have white spaces in them. Most unix/linux utilities use any white space (tab, new line, space) as their delimiter character of choice, hence the problem.
These files are either legal immigrants from the other operating systems (uploads to a CMS/wiki/blog, for example), or some native programs or utilities with “foreign” roots (vmware server).
The common way to deal with it, is to opt to use ASCII NUL as delimiter when invoking command line utilities. This capability is a built-in for more unix/linux utilities than I knew when I started to research to resolve a problem I had.
- grep -Z
- find . -print0
- xargs -0
- cut –output-delimiter=”\0″
“find . -print0 | xargs -0 ls -ltr” does work well, while ’svn status | cut -b8 –output-delimiter=”\0″ | xargs -0 ls -ltr’ doesn’t. Read the rest of this entry »
Permalink
February 20, 2007 around lunchtime
· Filed under LAMP, OpenSSH, PKI, centos, fedora core linux, information security, linux, unix
As discussed in my earlier articles on how to secure wordpress server and other LAMP application servers (part I, part II), it is imperative to protect the big ‘L’ in the LAMP, the Linux host server itself. One main step is to restrict and secure access to the server. On a Linux server, OpenSSH (sometimes in couple with a VPN solution) is the most commonly vetted choice. It should be used in lieu of telnet and FTP.
The OpenSSH that comes with mainstream Linux distributions may not be as tailored as you want to afford maximum security you desired. This should not be much of a surprise, since any pre-packaged software needs to reach broader audience and wider range of use cases, plus the packager may not share the same information security principles as you and may assess the risks differently. Read the rest of this entry »
Permalink
January 20, 2007 around mid afternoon
· Filed under CLI, command line, unix, windows, windows 2003 server, windows xp
Being a unix- and linux-centric person, I have been spoiled by various useful small utilities. It’s a bit frustrating to find their Windows‘ counterparts, when I need to do some quick work on Microsoft Windows platforms (such as Windows XP or Windows Server 2003).
While studying for MCP 70-290 certification, I hold my nose and read the Microsoft’s self-study guide. Surprise, surprise! Once I RTFM (read the fine manual) line by line, I found them magical utilities. Some with different names, while some are just an oddly-named switch away. Read the rest of this entry »
Permalink
