 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: as400 password change history</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/as400-password-change-history/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-password-change-history/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 16:32:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: dand</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-password-change-history/#comment-62359</link>
		<dc:creator>dand</dc:creator>
		<pubDate>Thu, 16 Apr 2009 19:23:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-62359</guid>
		<description><![CDATA[Set the system value QPWDEXPITV  *SEC     Password expiration interval to the desired number of days for all profiles, change all profiles expint to *SYSVAL and you will force a regular pwd change.  The industry standard is pretty much 90 for normal users and 30-45 for power users.  You could also turn on user auditing for Security dump and query your audit journal on a regular basis and track pwd changes.

BTW, i5OS finally went to a UNIX style encrypted pwd file, so several of the third party security packages allow you to see pwds and to check for pwds that are too &#039;simple&#039;.  You usually must be signed on as QSECOFR to use these functions.]]></description>
		<content:encoded><![CDATA[<p>Set the system value QPWDEXPITV  *SEC     Password expiration interval to the desired number of days for all profiles, change all profiles expint to *SYSVAL and you will force a regular pwd change.  The industry standard is pretty much 90 for normal users and 30-45 for power users.  You could also turn on user auditing for Security dump and query your audit journal on a regular basis and track pwd changes.</p>
<p>BTW, i5OS finally went to a UNIX style encrypted pwd file, so several of the third party security packages allow you to see pwds and to check for pwds that are too &#8216;simple&#8217;.  You usually must be signed on as QSECOFR to use these functions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: woodengineer</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-password-change-history/#comment-62344</link>
		<dc:creator>woodengineer</dc:creator>
		<pubDate>Thu, 16 Apr 2009 16:12:52 +0000</pubDate>
		<guid isPermaLink="false">#comment-62344</guid>
		<description><![CDATA[The i Series does not store passwords in a way the users can retrieve and de-crypt them.  It keeps the list internally somewhere.  Maybe someone knows how to hack into this data.  I suspect some sort of hash total is used, which is not reversable according to the experts I heard.

If you really want to keep a history, you can write an command validation program to capture the data at the time the use changes their password.

The system does a great job of this automatically.
I strongly recommend against trying to work around this security feature.]]></description>
		<content:encoded><![CDATA[<p>The i Series does not store passwords in a way the users can retrieve and de-crypt them.  It keeps the list internally somewhere.  Maybe someone knows how to hack into this data.  I suspect some sort of hash total is used, which is not reversable according to the experts I heard.</p>
<p>If you really want to keep a history, you can write an command validation program to capture the data at the time the use changes their password.</p>
<p>The system does a great job of this automatically.<br />
I strongly recommend against trying to work around this security feature.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: djac</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-password-change-history/#comment-62341</link>
		<dc:creator>djac</dc:creator>
		<pubDate>Thu, 16 Apr 2009 16:00:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-62341</guid>
		<description><![CDATA[The only system value I can think of that in any way fits this query is the QPWDRQDDIF sysval, which sets how many different passwords must be used before they can be re-used.

DSPSYSVAL (or WRKSYSVAL) QPWDRQDDIF...

If this is not what you are after then you will need to provide more information on what it is you are wanting to do.....]]></description>
		<content:encoded><![CDATA[<p>The only system value I can think of that in any way fits this query is the QPWDRQDDIF sysval, which sets how many different passwords must be used before they can be re-used.</p>
<p>DSPSYSVAL (or WRKSYSVAL) QPWDRQDDIF&#8230;</p>
<p>If this is not what you are after then you will need to provide more information on what it is you are wanting to do&#8230;..</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.012 seconds using memcached
Object Caching 296/299 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 17:24:55 -->