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. |

| Subject: | Re: Credentials for Application use |
|---|---|
| Date: | Wed, 18 May 2005 18:11:30 +0300 (IDT) |
On Tue, 10 May 2005, Mikey wrote:
This is a broad question around the current practices and recommendation of what not to do when it comes to credentials used by applications to gain access to a resource or data stored elsewhere.
As you can guess similar questions were discussed countless number of times on securityfocus :-) The usual practice is to create an account for your program and store the `secret' in the file which is readable only by that account owner. -- Regards, ASK
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Pandora 1.1 released!, acid_lemon |
|---|---|
| Previous by Thread: | Credentials for Application use, Mikey |
| Next by Thread: | Detecting SoftICE ?, Bruce Klein |
| Indexes: | [Date] [Thread] [Top] [All Lists] |