From: "Dave Korn" <dave.korn@artimi.com>
To: "'cygwin-serialz-n-warez-r-us@cygwin.com'" <cygwin-talk@cygwin.com>
Subject: FW: problem with cron
Date: Thu, 12 Jan 2006 18:48:00 -0000 [thread overview]
Message-ID: <SERRANOVUkRacUtI9dm000000ca@SERRANO.CAM.ARTIMI.COM> (raw)
Mike Stathopoulos wrote:
> I having problems running the cron on my system. Can you help?
>
> Thanks, Mike
:-D Did anyone else notice the free registration code for FractaleXtreme in
that post?
Cygcheck is perhaps a bit overzealous in the way it appears to recurse into
any key under HKCU\Software that begins with the string "Cygnus". Cygnus
software != Cygnus solutions, after all.
Then again, we just had a practical demonstration of why stored plaintext
passwords are A Bad Thing, even if they only exist in a file on your own
computer that's protected by ACLs that only let the named user access it. A
valuable lesson in infosec for us all.
(I must remember to point this out on FD next time someone posts a
"plaintext password storage vulnerability" report and someone else says it's
no problem because it's in the user's home dir...)
cheers,
DaveK
--
Can't think of a witty .sigline today....
reply other threads:[~2006-01-12 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SERRANOVUkRacUtI9dm000000ca@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).