1 - redo root level priv check to include logging and sends a message to root, advising the user that the program was breached, and suggest
possable sanctions (example, using restrictive shell, remove from groups, etc)
2 - Change sourcecode licence from BSD to GPL-2
3 - Change useradd to include skel directory (/etc/skel/)... read more
Plan for syspert 1.5 Trident
question to be asked on start-up for logging the session (Should this session be logged (Y/N) >)
then if statement for logging ( if [ "$log_ans" = "y" ]
then
<cmd> > /tmp/syspert-trident-log.txt
else
<cmd>
fi)... read more</cmd></cmd>
1.0 release date set back about a week, due to printer management, adding access control lists and using flags to go to different areas of programs, will have update soon
fixed unknown bug in group management, close to 1.0 release, hopefully by next week
Creating version 1.0, fixed install.sh now it will ask you if certain programs are installed or not
also creating new function for group management, will be added to usrmgmt
for 1.0 release, I may add group management (in a new function (function grp_mgmt), creating new groups, removing groups, adding users to groups, removing users from groups
Also I have to fix authorisation system, preventing compiling
Coming up with ideas for the 1.0a Revision 1 release, may add ability to make hfs filesystem, add new reporting system for unauthenticated users, ether the user will have to enter the root password, or they will be reported to root as an unauthenticated user and recommend sanctions against that user, may port to mac os x if I get the time would rename to 'syspertx'
syspert launched last night, all looks good, good response on google+, I see bright things in it's future
Today is the day, finally after 2 years of work syspert is finally ready for shipping, only to add mkfs-ufs to create a UNIX filesystem
Any day now, possibly tomorrow (Wednesday 2nd September 2013) syspert will be finished and ready for upload