Category: Archive

Using sudo

Most Unix systems have some way of letting ordinary users perform certain tasks as root or some other privileged user. SCO Open Server has “asroot” and can also directly assign “authorizations” such as backup privileges or being able to change other user’s passwords. SCO Unixware/Open Unix 8 have a similar facility in “tfadmin”. Many Unixes, and Linux, use “sudo”.

The configuration of sudo is by the /etc/sudoers file. I’m sure that there are more poorly written man pages, but “man sudoers” is among my all time favorites for obfuscation and poor explanation. The creation of the file and the actual use of sudo isn’t all that bad though.

Backlinks (http_referrers)

When a web page is accessed by a link from some other page, the address of the other page (the “referring page”) is made available to the web server. We can pick that information up from logs or as the page is being displayed. For example, if we have Server Side Includes or php, we can pickup the referring page from an environment variable. Here’s a snippet of Perl code that does that:
$frompage=$ENV{HTTP_REFERER};
$thispage=$ENV{REQUEST_URI};

Yes, there’s a missing R in HTTP_REFERER. Yes, that’s wrong, but that’s what the variable is so that’s what you use.

Documenting Your Network

Undocumented networks are extremely common. Many times this is related more to the difficulty of keeping the documentation up to date rather than to the difficulty of the documentation process itself. Many LAN Administrators had big dreams at one time of keeping elaborate drawings detailing every last aspect of the network. However, networks tend to change too frequently for such drawings to stay current. In spite of the difficulty, having a well documented network can help you solve problems quickly when they arise and is vital to the overall security of your network. In this article, we’ll discuss some alternative documentation methods that are more practical in the ever changing world of networks.

Back To Top