<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>Hoxt.com - Open Source Mirrors</title>
	<link>http://hoxt.com</link>
	<description>Apache, CPAN, PHP, MySQL, PuTTY, Linux Virtual Server, Linux Documentation Project, ProFTPD</description>
	<lastBuildDate>Sat, 17 Jul 2010 22:19:47 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0.3" -->

	<item>
		<title>Install OSSEC automatically with expect</title>
		<description><![CDATA[If you want to script the installation of ossec, this script will use expect/spawn to automatically enter values for prompts: #!/usr/bin/expect -d set timeout -1 spawn ossec-hids-2.4.1/install.sh expect "en/br/cn/de" send "en\r" expect "Press ENTER to continue" send "\r" expect "What kind of installation" send "local\r" expect "Choose where to install the OSSEC HIDS" send "\r" [...]]]></description>
		<link>http://hoxt.com/2010/07/17/install-ossec-automatically-with-expect/</link>
			</item>
	<item>
		<title>shell scripting &#8211; Bash alias that takes argument</title>
		<description><![CDATA[Normally, you would have this shortcut in .bash_profile alias sshwww='ssh john@www.example.com' What about you have 100s of www servers: sshwww() { ssh "john@$1".example.com; } Usage: "sshwww web1", "sshwww web2" Even more, you can su directly to root from john: sshroot() { ssh "john@$1".example.com "su"; } Usage: "sshroot web1", "sshroot web2"]]></description>
		<link>http://hoxt.com/2010/07/07/shell-scripting-bash-alias-that-takes-argument/</link>
			</item>
	<item>
		<title>Make an encrypted password for useradd</title>
		<description><![CDATA[Very simple using php: php -r "echo crypt('myplaintextpassword123');" useradd -m -p "$1$abJez234$fD4Dn4IrG3Hzeas3hBjIb0" -d /home/john -s /bin/bash john]]></description>
		<link>http://hoxt.com/2010/07/07/make-an-encrypted-password-for-useradd/</link>
			</item>
	<item>
		<title>su &#8211; Run a command after entering root password</title>
		<description><![CDATA[For a better scripting automation and still retain the security of su/non-root login: su -c "mysql -e 'SHOW STATUS;' " This will return the status of mysql. Now you can run this via a regular user, then su, then mysql. You'll be asked for password twice, one for the regular user, one for root. ssh [...]]]></description>
		<link>http://hoxt.com/2010/07/07/su-run-a-command-after-entering-root-password/</link>
			</item>
	<item>
		<title>Puppet locking problem</title>
		<description><![CDATA[If you run "puppetd --test" manually or via service and get this error: Run of Puppet configuration client already in progress; skipping Problem: the lock file is not removed properly. It's a known bug: http://projects.reductivelabs.com/issues/2888 Solution: manually remove /var/lib/puppet/state/puppetdlock Also, you might need to check /var/run/ for the pid and delete/kill the process if it's [...]]]></description>
		<link>http://hoxt.com/2010/07/07/puppet-locking-problem/</link>
			</item>
	<item>
		<title>mod_security and Apache dummy internal connection</title>
		<description><![CDATA[The core rule looks specially for 127.0.0.1 so if your apache is listening to specific IPs and not 127.0.0.1, this rule will be ignored. Solution: add Listen 127.0.0.1:80 to your httpd.conf, it should be the first line before other Listen's statements You might want to add exceptions or slowly introduce the rulesets. Some core rules [...]]]></description>
		<link>http://hoxt.com/2010/07/06/mod_security-and-apache-dummy-internal-connection/</link>
			</item>
	<item>
		<title>Our thanks to the open source developers</title>
		<description><![CDATA[The development team at AdSpeed uses open source applications daily and to show our support to the great open source creators and developers, we are proud to dedicate a server in our ad server network with redundant bandwidth to host a variety of open source mirrors. This server has been online since 2006. Following is [...]]]></description>
		<link>http://hoxt.com/2006/01/16/hello-world/</link>
			</item>
</channel>
</rss>

