No, it was not me who implemented fw in le.
You can open a ticket here if you want: Ticket System - LibreELEC Forum
No, it was not me who implemented fw in le.
You can open a ticket here if you want: Ticket System - LibreELEC Forum
Looks ok here
You can also change timestamp format in awk/strftime.
[2019-06-04 14:49:25] Server listening on 0.0.0.0 port 22.
[2019-06-04 14:49:25] Server listening on :: port 22.
[2019-06-04 14:49:26] Accepted password for root from 192.68.1.2 port 56393 ssh2
[2019-06-04 14:49:58] Failed password for root from 192.68.1.3 port 56405 ssh2
[2019-06-04 14:49:58] Connection closed by authenticating user root 192.68.1.3 port 56405 [preauth]
[2019-06-04 14:49:59] Failed password for root from 192.68.1.4 port 56407 ssh2
[2019-06-04 14:49:59] Connection closed by authenticating user root 192.68.1.4 port 56407 [preauth]
I keep few things in my head. But in this case I was using sshd(8) - OpenBSD manual pages and few suggestions from Google ![]()
Well, then one option is to fix sshd service file.
First remove added SSH_ARGS value from /storage/.cache/services/sshd.conf file.
Then copy sshd service file to storage and change ExecStart line.
cp /usr/lib/systemd/system/sshd.service /storage/.config/system.d/
vi /storage/.config/system.d/sshd.service
ExecStart=/bin/sh -c "/usr/sbin/sshd -D $SSH_ARGS -e 2>&1 | awk '{print strftime(\"[%%Y-%%m-%%d %%H:%%M:%%S] \") $0}' >>/var/log/sshd.log"
systemctl daemon-reload
systemctl restart sshd
systemctl status sshd -l --no-pager
Can you post both outputs of iptables -L and ip6tables -L to compare?
Check if you can add StandardOutput to file in sshd.service file.
I don't know if there is any such log file. BUt i see with command above
Jun 02 11:25:22 LibreELEC sshd[1340]: Failed password for root from 192.168.2.3 port 47442 ssh2
Jun 02 11:25:22 LibreELEC sshd[1340]: Connection closed by authenticating user root 192.168.2.3 port 47442 [preauth]
Maybe some cron job could create log file with grepping systemctl status.
Anyone can point me where accepted and failed logins to ssh are stored ?
Maybe
Would not be easier to restart Kodi at 3AM every night? It is not a fix but still ![]()
Compare the content of both archives to see what is the difference ![]()
I updated build Milhouse #0528and removed kodi profile folder. After new start I could install whatever addon version was in the repository.
No. Intel is still working on kernel HDR support ....
Intel is also working on S9xxx SoC? ![]()
Do you have any explanation for that?
No actually. I just look around how other docker services are started and saw this small change. Maybe