On Wednesday 26 November 2008 11:57:49 Arvin Schnell wrote: > On Wed, Nov 26, 2008 at 11:47:53AM +0100, Stefan Hundhammer wrote: > > On Mittwoch, 26. November 2008, Ladislav Slezak wrote: > > > And of course, this won't help if Y2DEBUG is enabled. We would need a > > > new datatype or a flag in the interpreter to fix it with Y2DEBUG > > > enabled. > > > > I don't think this can be done in the general case: Both the YCP > > interpreter and the UI are logging entire statements or statement > > snippets. You can never tell what part of that might contain confidential > > data like passwords. > > > > Example: > > > > UI::OpenDialog(`VBox(..., `Password( _( "Password:" ), "b1g*s3cr3t", > > ...); > > > > In full debug mode, the YCP interpreter will write this to the log, and > > if there is a YCP or a UI syntax error or another UI exception, the > > offending statement (which might easily contain something like the above > > example) will be logged. > > A nice feature would be to tell YCP that a string is a password > and thus the string is never logged.
We had there a long time ago, but turned out to me a quite some hassle because you have to deal with a fact that you cannot use this type as a normal string. And we don't have any way to attach flags to string values to identify passwords or similar. Stano -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
