You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The USB Boot Maker that comes with the SeaChest Utilities from https://www.seagate.com/support/software/seachest/ includes various files in the home directory for the tc user which shouldn't be in there, for example some previous shell history in .ash_history:
There's also some other files which should be deleted in the .config and .local directories within the home directory (e.g. Midnight Commander history).
Those files seem to be extracted during boot from /tce64/mydata_CLI64.tgz.
Expected behavior
No previous history and other user data should be included in the home directory.
How to reproduce
Write image with USB Boot Maker.
Boot from the created USB boot medium.
Pressing Cursor Up shows shell commands which the user has never entered before.
cd ~
ls -la shows various files which should be sanitized before being included in the USB Boot Maker files.
Deployment information
Not relevant.
Additional information
No response
The text was updated successfully, but these errors were encountered:
Problem
The USB Boot Maker that comes with the SeaChest Utilities from https://www.seagate.com/support/software/seachest/ includes various files in the home directory for the
tc
user which shouldn't be in there, for example some previous shell history in.ash_history
:There's also some other files which should be deleted in the
.config
and.local
directories within the home directory (e.g. Midnight Commander history).Those files seem to be extracted during boot from
/tce64/mydata_CLI64.tgz
.Expected behavior
No previous history and other user data should be included in the home directory.
How to reproduce
cd ~
ls -la
shows various files which should be sanitized before being included in the USB Boot Maker files.Deployment information
Not relevant.
Additional information
No response
The text was updated successfully, but these errors were encountered: