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
During manual install, a temporary login banner is installed in /root/.bashrc:
To continue using teslausb setup, edit the file /teslausb/teslausb_setup_variables.conf with ...
Instead of editing the file, i wanted to copy a pre-made version using sftp.
However, i can't because of this error:
$ sftp root@teslausb
Received message too long 724380973
Ensure the remote shell produces no output for non-interactive sessions.
After commenting out the banner, it started working.
Edit:
The error does not happen with the "pi" user. However, that user does not have permissions to overwrite the file, nor can they be added due to how the file system is mounted.
Device
Raspberry Pi Zero 2 W
OS Image
other
Car Model
Model 3
USB connection
Glove box
Logs
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
I usually just scp file.dat pi@teslausb:/tmp, then ssh into the Pi and copy the file from /tmp to its final destination, given that the root user is normally prohibited from login for security reasons, and enabling root login requires modifying several system settings.
Given that, I'm not inclined to make any changes accommodating this use case, but you're welcome to submit a PR.
Describe the problem
During manual install, a temporary login banner is installed in
/root/.bashrc
:Instead of editing the file, i wanted to copy a pre-made version using sftp.
However, i can't because of this error:
After commenting out the banner, it started working.
Edit:
The error does not happen with the "pi" user. However, that user does not have permissions to overwrite the file, nor can they be added due to how the file system is mounted.
Device
Raspberry Pi Zero 2 W
OS Image
other
Car Model
Model 3
USB connection
Glove box
Logs
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: