pfsense enable shell history

tayuser

not working. the shell history still gone after logoff. require reboot or restart service?
any method to do in the GUI?

Popolou

The default shell is tcsh and it used to be configurable in the .tcshrc file but subsequently moved into the GUI. If you go into the User Manager and edit the user, there is a tickbox at the bottom: -

The comment within that file is misleading and legacy. It would probably be helpful if it was cleaned up at a later date.

stephenw10

Yup there's a gui option for that now.

You need to log back in after setting that against the user.

tayuser

@Popolou is there a global setting to enable all user login history?

Gertjan

@tayuser said in pfsense enable shell history:

all user login history?

All ?
There is just one user, called 'admin'.
Its a firewall after all, not a file server or something like that.

Popolou

@tayuser said in pfsense enable shell history:

@Popolou is there a global setting to enable all user login history?

I think by adding <keephistory></keephistory> to the end of each of the user's block within the xml config file, it will get picked up on reboot. But, i have not done this myself and would give way to the more experienced here! IMHO for the trouble of a few clicks vs the downtime, i'd probably just do this through the GUI.

stephenw10

There isn't a single check box to enable it for all users though.

jimp

@Popolou said in pfsense enable shell history:

The comment within that file is misleading and legacy. It would probably be helpful if it was cleaned up at a later date.

Curious what you meant here, there is no comment in .tcshrc that says to touch a file. The current content is:

# Enable command history storage and related settings if the user is configured
# to do so. See https://redmine.pfsense.org/issues/11029
set keephistory=`/usr/local/sbin/read_xml_tag.sh boolean system/user\[uid=\'${uid}\'\]/keephistory`
if ( $?prompt && ($keephistory == "true")) then
[...]

So there is no mention of the old method there, and the linked redmine issue also links to the updated behavior.

Popolou

@jimp Yes on reflection i was perhaps vague. I meant i felt there was no longer a need to ref the redmine anymore since it's effectively a legacy issue that you subsequently dealt with and if you agree, could now be removed.

JonathanLee

@Popolou thanks