http://qa.mandrakesoft.com/show_bug.cgi?id=4392
Product: msec
Component: msec
Summary: HISTFILESIZE wrong because of set_shell_history_size(-1)
not handled properly
Product: msec
Version: 0.38-5mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msec
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
When the security level is < 3, a call is made to
mseclib.set_shell_history_size(-1) at msec.py:180 that puts
libmsec.set_shell_history_size(-1) in the FAKE stack.
But when the FAKE stack is parsed in mseclib.commit_changes(),
libmsec.set_shell_history_size(-1) is not evaluated, because f =
[libmsec.set_shell_history_size,-1)] doesn't match any of this tests :
if len(f[1]) >= 1 and f[1][0] != -1:
apply(f[0], f[1])
elif len(f[1]) == 0:
apply(f[0])
This is a contradiction with libmsec.set_shell_history_size definition :
def set_shell_history_size(size):
''' Set shell commands history size. A value of -1 means unlimited.'''
Because of this, HISTFILESIZE isn't restored to -1 (= let bash decide) in
security levels < 3. So HISTFILESIZE is set to 10, barely usuable ...
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
