Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: secure storage of sensitive data in J2EE

Subject: Re: secure storage of sensitive data in J2EE
Date: Mon, 14 Feb 2005 20:24:13 +0100
Michael Silk wrote:
Comments inline.


-----Original Message-----
From: exon [mailto:exon@home.se] Sent: Friday, 11 February 2005 9:33 AM
To: webappsec@securityfocus.com
Subject: Re: secure storage of sensitive data in J2EE


Michael Silk wrote:

Exon said:


Because it's supposed to be encrypted when it arrives over the network.


And how can that happen in such a way that an application

listening to


the incoming information can't get at it first?


It can't, but protecting pieces of memory from prying eyes was what this discussion was about.


Yes, and the sub-discussion with Michael Howard was about the
usefulness of SecureString (this is the discussion where you responded
to me).


SecureString (whatever that is) would, if it works as the name suggests, be useful for keeping the key to decrypt the incoming packets. If data is to be sent in plaintext it's naturally of no use at all.


-- Michael



<Prev in Thread] Current Thread [Next in Thread>