<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Felipe Alfaro Solana &#187; x86_64</title>
	<atom:link href="http://www.felipe-alfaro.org/blog/category/x86_64/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.felipe-alfaro.org/blog</link>
	<description>A little bit of technology, security and networking with Linux, FreeBSD and Mac OS X, plus some personal opinions.</description>
	<lastBuildDate>Sun, 23 Oct 2011 16:46:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Postfix and Cyrus-IMAP interactions on x86_64</title>
		<link>http://www.felipe-alfaro.org/blog/2006/05/22/postfix-and-cyrus-imap-interactions-on-x86_64/</link>
		<comments>http://www.felipe-alfaro.org/blog/2006/05/22/postfix-and-cyrus-imap-interactions-on-x86_64/#comments</comments>
		<pubDate>Sun, 21 May 2006 20:56:21 +0000</pubDate>
		<dc:creator>Felipe Alfaro Solana</dc:creator>
				<category><![CDATA[Cyrus]]></category>
		<category><![CDATA[Postfix]]></category>
		<category><![CDATA[x86_64]]></category>

		<guid isPermaLink="false">http://felipe-alfaro.org/blog/2006/05/22/postfix-and-cyrus-imap-interactions-on-x86_64/</guid>
		<description><![CDATA[The file /etc/postfix/master.cf of postfix-2.1.5-4.2.RHEL4.x86_64 contains a hard-coded path to Cyrus-IMAP LMTP deliver agent, /usr/lib/cyrus-imapd/deliver. However, this causes problems on x86_64 systems since Cyrus-IMAP LMTP deliver agent path is /usr/lib64/cyrus-imapd/deliver. Fixing this problem is easy: just edit /etc/postfix/master.cf and replace /usr/lib/cyrus-imapd/deliver with /usr/lib64/cyrus-imapd/deliver. I have filled in a bug report against Red Hat&#8217;s Enterprise Linux [...]]]></description>
			<content:encoded><![CDATA[<p>The file <code>/etc/postfix/master.cf</code> of postfix-2.1.5-4.2.RHEL4.x86_64 contains a hard-coded path to Cyrus-IMAP LMTP deliver agent, <code>/usr/lib/cyrus-imapd/deliver</code>. However, this causes problems on x86_64 systems since Cyrus-IMAP LMTP deliver agent path is <code>/usr/lib64/cyrus-imapd/deliver</code>.</p>
<p>Fixing this problem is easy: just edit <code>/etc/postfix/master.cf</code> and replace <code>/usr/lib/cyrus-imapd/deliver</code> with <code>/usr/lib64/cyrus-imapd/deliver</code>.</p>
<p>I have filled in a bug report against Red Hat&#8217;s Enterprise Linux 4:</p>
<p><a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192601">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192601</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.felipe-alfaro.org/blog/2006/05/22/postfix-and-cyrus-imap-interactions-on-x86_64/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Cyrus-IMAP and PAM interactions on x86_64</title>
		<link>http://www.felipe-alfaro.org/blog/2006/05/20/cyrus-imap-and-pam-on-x86_64/</link>
		<comments>http://www.felipe-alfaro.org/blog/2006/05/20/cyrus-imap-and-pam-on-x86_64/#comments</comments>
		<pubDate>Sat, 20 May 2006 17:53:04 +0000</pubDate>
		<dc:creator>Felipe Alfaro Solana</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[PAM]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[x86_64]]></category>

		<guid isPermaLink="false">http://felipe-alfaro.org/blog/2006/05/20/cyrus-imap-and-pam/</guid>
		<description><![CDATA[In Red Hat Enterprise Linux ES 4.1 Update 3, both /etc/pam.d/imap and /etc/pam.d/pop contain hard-coded paths pointing to pam_stack.so, actually /lib/security/pam_stack.so. This causes problems on x86_64 since pam_stack.so is located under /lib64/security/pam_stack.so. A workaround is to modify /etc/pam.d/imap and /etc/pam.d/pop to look like this: #%PAM-1.0 auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth I filled [...]]]></description>
			<content:encoded><![CDATA[<p>In Red Hat Enterprise Linux ES 4.1 Update 3, both <code>/etc/pam.d/imap</code> and <code>/etc/pam.d/pop</code> contain hard-coded paths pointing to <code>pam_stack.so</code>, actually <code>/lib/security/pam_stack.so</code>. This causes problems on x86_64 since <code>pam_stack.so</code> is located under <code>/lib64/security/pam_stack.so.</code></p>
<p>A workaround is to modify <code>/etc/pam.d/imap</code> and <code>/etc/pam.d/pop</code> to look like this:</p>
<pre>
<div>#%PAM-1.0
auth       required     pam_stack.so service=system-auth
account    required     pam_stack.so service=system-auth</div>
</pre>
<p>I filled in a bug report against Red Hat Enterprise Linux 4:</p>
<p><a target="_blank" onclick="return top.js.OpenExtLink(window,event,this)" href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192550">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192550</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.felipe-alfaro.org/blog/2006/05/20/cyrus-imap-and-pam-on-x86_64/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

