<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Password on Evan Hoffman</title><link>https://evan.wtf/tags/password/</link><description>Recent content in Password on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Wed, 12 Feb 2014 11:06:07 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/password/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting user Postgres passwords via MD5</title><link>https://evan.wtf/2014/02/12/setting-user-postgres-passwords-via-md5/</link><pubDate>Wed, 12 Feb 2014 11:06:07 +0000</pubDate><guid>https://evan.wtf/2014/02/12/setting-user-postgres-passwords-via-md5/</guid><description>&lt;p&gt;Say you want to create a Postgres account for a user but you don&amp;rsquo;t want them to have to reset it after logging in, and you don&amp;rsquo;t want to do the &amp;ldquo;come type in a password on my computer&amp;rdquo; routine. Well, here&amp;rsquo;s one way around this.&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&#10;&lt;p&gt;Have the user generate an MD5 of their password on their local computer. Postgres uses the username as the salt for the hash, so the command to generate the md5 on a Mac would be (assuming a username of &amp;rsquo;ehoffman&amp;rsquo; and a password of &amp;lsquo;abcdefg&amp;rsquo;):&lt;/p&gt;</description></item><item><title>Victory! Change Active Directory Password via LDAP through browser</title><link>https://evan.wtf/2010/01/13/victory-change-active-directory-password-via-ldap-through-browser/</link><pubDate>Wed, 13 Jan 2010 13:51:43 +0000</pubDate><guid>https://evan.wtf/2010/01/13/victory-change-active-directory-password-via-ldap-through-browser/</guid><description>&lt;p&gt;I had to give up on PHP and go to Perl, but it turned out not to be so bad. Users can now change their Active Directory passwords via a self-service web page that doesn&amp;rsquo;t require admin credentials. The Perl code is below. Authentication to the script is done via .htaccess LDAP authentication, so the REMOTE_USER env variable is assumed to contain the user&amp;rsquo;s username (sAMAccountName) by the time this script is called. There is a simple check for $ENV{HTTPS} to ensure the script is called via SSL, and AD requires password changes to be done via ldaps, so the whole thing &lt;em&gt;should&lt;/em&gt; be encrypted end to end.&lt;/p&gt;</description></item></channel></rss>