Attempt to Log Handling Compromise Severely Resisting Discovery
I have just videotaped bash removing a command from my bash history every time I execute it, using a phone that has been in airplane mode since factory reset, and also most of its life since purchase.
The command is working after re-copy-pasting it after sending this email.
Seems it was related to the first copy-buffer or somesuch.
The system is an olimex teres running armbian ubuntu 18, and has had the
radio disabled using 'nmcli radio all off; sudo systemctl disable
NetworkManager;" for some time now. it is running the same install it was
when the keyboard, which has a usb-programmable avr chip, was sending
incorrect keycodes. the incorrect keycode behavior has stopped.
On Wed, Jun 17, 2020, 6:14 PM Karl
I have just videotaped bash removing a command from my bash history every time I execute it, using a phone that has been in airplane mode since factory reset, and also most of its life since purchase.
On 6/17/20 17:14, Karl wrote:
I have just videotaped bash removing a command from my bash history every time I execute it, using a phone that has been in airplane mode since factory reset, and also most of its life since purchase.
If you start a command with a space, bash will not add it to the
history. They apparently consider this a feature.
--
Shawn K. Quinn
participants (2)
-
Karl -
Shawn K. Quinn