|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Major security flaw in Cybercash 2.1.2
Tim Scanlon (tfs
CHARM.SEALSOFT.COM)Sat, 8 Nov 1997 00:35:20 -0500
- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Theo Van Dinter: "Re: xbru vulnerability"
- Previous message: Bjorn Wesen: "Re: Intel Pentium Bug"
- In reply to: Anonymous: "Major security flaw in Cybercash 2.1.2"
- Next in thread: Megan Alexander: "Re: Major security flaw in Cybercash 2.1.2"
On Fri, 7 Nov 1997 , Anonymous said: >In CyberCash's server, when the "DEBUG" flag is on, the contents of >all credit card transactions are written to a log file (named >"Debug.log" by default). > >The easiest workaround I've found is to simply delete the existing >Debug.log file. In my experience with the Solaris release, the >CyberCash software does not create this file at start time when the >DEBUG flag is set to 0. > ln -s Debug.log /dev/null Works easier than deleting over and over I'd hazard. Tim --- ________________________________________________________________ tfssealsoft.com (NeXTmail, MIME) Tim Scanlon tfs
epic.org (PGP key by req) crypto is good Seal Technologies Inc. I own my own words
- Next message: Theo Van Dinter: "Re: xbru vulnerability"
- Previous message: Bjorn Wesen: "Re: Intel Pentium Bug"
- In reply to: Anonymous: "Major security flaw in Cybercash 2.1.2"
- Next in thread: Megan Alexander: "Re: Major security flaw in Cybercash 2.1.2"