in reply to Authorize.Net Credit Card
ummm ... errr ... no.
Seriously if it's in a variable, it's in system memory. And it will be in memory, theoritically, until the end of its scope (possibly until the end of the process or depending on how you've configured your system and what happens to the process, possibly forever in a core dump).
This is why you have to take a "layered" approach to security.
then stop worrying ... or worry less.
-derby
update: I forgot:
0. batten down your app. Ensure you use the correct scope and handle faulty input (including signals) correctly.
another update: Just saw a review of this on slashdot ... may be worth the buy.
|
|---|