On Wed, Nov 26, 2008 at 12:32:44PM +0100, Stanislav Visnovsky wrote:
On Wednesday 26 November 2008 11:57:49 Arvin Schnell wrote:
On Wed, Nov 26, 2008 at 11:47:53AM +0100, Stefan Hundhammer wrote:
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.
I can't remember those times. Was this in libzypp or in YCP? For YCP I don't see the problem you mention. Just add a flag to YCPString and propagate it in all builtins. Then check the flag in the logging functions, in ".target.ycp" and similar. I could use this feature to save the password for encryption in the storage target map. Right now the passwords are saved in an extra map where the key is the device name *or* the file name for crypt files. This is not really straightforward and has caused bugs during the partitioner redesign. ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org