static gchar security

How (in)secure would it be to have a static gchar that would save a
plaintext password?  The gchar would start off null, but could later
contain a password, and is static for the life of the app.  Is there a
better way to do this?

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]