full-disclosure - I think some one might have screwed-up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

From: runowsk at a.cs.okstate.edu (Rick Runowski)
Subject: I think some one might have screwed-up

Adam/David,

I agree with David to a point.  It seems to me that this is ok so long
as the employee's know it goes out to the web live, or there is some
standard as to what is and is not allowed to be put into the logs.  A
(very brief) look through a few of the pages suggest this to be the
case.

I don't however feel that I would be OK with the company I work for
doing the same.  I know we (or at least I) put data into the CVS logs
that I wouldn't want on the internet.  However, I'm a just a newb
programmer, whatta I know. ;p

On Thu, 2004-05-06 at 15:44, David wrote:
> Adam wrote:
--SNIP
> > can some one tell me is this a good thing to leave in public?
> 
-- SNIP --
> It's not like you can get access to their code using it. I don't see the 
> big problem.
> 
> > 
> > http://recruiterdirect.com/module_sizes.html
--SNIP--
-- 
Rick Runowski <runowsk@...s.okstate.edu>
OSU Computer Science Department Student