Re: email from cracklib cron
On 29 Apr 1999, Gary L. Hennigan wrote: My question is why hasn't this been fixed? Or perhaps it has and somehow my system just isn't up-to-date? Or was it deemed too simple a fix to warrant a new version of cracklib-runtime? It has been fixed and uploaded to potato. There has since been another bug found which I've tracked down to a bug in the find package. A new upload should be coming shortly. I'm not clear on when its ok to upload a fix to a stable distribution. This is clearly not a security issue or even a serious problem. Would it still be appropriate to upload to slink? -- Jean Pierre
Re: email from cracklib cron
I'm not clear on when its ok to upload a fix to a stable distribution. This is clearly not a security issue or even a serious problem. Would it still be appropriate to upload to slink? It's the eternal debate about what the word 'stable' means in a software distribution. One definition is, non-experimental, but up to date. Another is, Changes only for security reasons. Debian seems to use the latter definition. Perhaps the package developer has some say; I'm not sure how that works. -- Pete Harlan [EMAIL PROTECTED] http://www.artselect.com/ http://www.mealsforyou.com/
Re: email from cracklib cron
[EMAIL PROTECTED] (Gary L. Hennigan) wrote: I have a system that I hadn't bothered adding dev/null to the appropriate place in /etc/cron.daily/cracklib to avoid the email (slink distribution). It's on a seldom used system and I just never bothered. I had hoped that the simple fix would be quickly uploaded and I wouldn't need to bother. Well, it finally got to the point that it was driving me crazy so I looked in the Debain mailing list archive and applied the /dev/null. Sorry to be a little dense, but where in the /etc/cron.daily/cracklib file do I put /dev/null? This is the first I have heard about the problem, though I have noticed a lot of mail on my system for root originating from the cracklib cron entry. Many thanks. -- Phillip Deackes [EMAIL PROTECTED] Debian Linux v.2.1
Re: email from cracklib cron
Phillip Deackes [EMAIL PROTECTED] writes:
| [EMAIL PROTECTED] (Gary L. Hennigan) wrote:
| I have a system that I hadn't bothered adding dev/null to the
| appropriate place in /etc/cron.daily/cracklib to avoid the email
| (slink distribution). It's on a seldom used system and I just never
| bothered. I had hoped that the simple fix would be quickly uploaded
| and I wouldn't need to bother. Well, it finally got to the point that
| it was driving me crazy so I looked in the Debain mailing list archive
| and applied the /dev/null.
|
| Sorry to be a little dense, but where in the /etc/cron.daily/cracklib
| file do I put /dev/null?
|
| This is the first I have heard about the problem, though I have noticed
| a lot of mail on my system for root originating from the cracklib cron
| entry.
Here's the whole section. It's toward the end of
/etc/cron.daily/cracklib
if [ -n ${cracklib_dictpath_src} -a -n ${cracklib_dictpath} ]
then
/usr/sbin/crack_mkdict ${cracklib_dictpath_src} |\
/usr/sbin/crack_packer ${cracklib_dictpath} /dev/null
fi
Gary
email from cracklib cron
I have a system that I hadn't bothered adding dev/null to the appropriate place in /etc/cron.daily/cracklib to avoid the email (slink distribution). It's on a seldom used system and I just never bothered. I had hoped that the simple fix would be quickly uploaded and I wouldn't need to bother. Well, it finally got to the point that it was driving me crazy so I looked in the Debain mailing list archive and applied the /dev/null. My question is why hasn't this been fixed? Or perhaps it has and somehow my system just isn't up-to-date? Or was it deemed too simple a fix to warrant a new version of cracklib-runtime? Gary
Re: email from cracklib cron
In foo.debian-user, you wrote: I have a system that I hadn't bothered adding dev/null to the appropriate place in /etc/cron.daily/cracklib to avoid the email (slink distribution). It's on a seldom used system and I just never bothered. I had hoped that the simple fix would be quickly uploaded and I wouldn't need to bother. Well, it finally got to the point that it was driving me crazy so I looked in the Debain mailing list archive and applied the /dev/null. My question is why hasn't this been fixed? Or perhaps it has and somehow my system just isn't up-to-date? Or was it deemed too simple a fix to warrant a new version of cracklib-runtime? Alas, it was a part of Debian for so long that we must now leave it in for backward compatibility. It is now a standard macro for configure to grep the root mailbox for 'cracklib' to determine if the macro is being run on a Debian system. -Mitch -- The above is both unhelpful and untrue --Mitch Blevins
