set shell with chsh to /opt/bin/zsh, ssh stopped working (refuses password shown in xochitl), switched back to /bin/sh, still broken
#can't access ssh after switching shell
peak slate
shy bramble
peak slate
after switching back still seems to be broken though ...?
shy bramble
Have you checked /etc/passwd to make sure it's been changed back?
peak slate
Have you checked /etc/passwd to make sure it's been changed back?
seems like it to me
shy bramble
Have you checked any logs to see what the error is?
peak slate
Have you checked any logs to see what the error is?
dropbear logs orrrr?
ssh -v told me nothing
shy bramble
ssh -v told me nothing
how about ssh -vvv
peak slate
packet type 51, but i just fixed this with openssh
shy bramble
dropbear logs orrrr?
Ideally yes
shy bramble
packet type 51, but i just fixed this with openssh
This statement is confusing me, you fixed it, or you are still getting an error that is packet type 51?
packet type 51 is not an error though, it's a request to negotiate the compression algo
peak slate
fixed it, but when i tested with vvv while dropbear was still installed the error mentioned packet type 51
ah, nevermind then
shy bramble
dropbear was still installed?
peak slate
before i set up openssh server yes
shy bramble
Please tell me you haven't tried to remove dropbear from the device
shy bramble
I would highly recommend you don't do that
if you do have openssh installed, run it on a different port
and make sure dropbear continues to work
peak slate
dropbear won't save me if systemd fails
shy bramble
as the next time you update, you will be back to dropbear
shy bramble
dropbear won't save me if systemd fails
Expand on this please
peak slate
i'm probably not going to update for a while considering this is a version with toltec
shy bramble
if systemd fails, the tablet will not boot
shy bramble
i'm probably not going to update for a while considering this is a version with ...
Toltec will add support for newer versions eventually
shy bramble
but if it does boot openssh will run xd
if systemd fails it will not boot
systemd is the init system
peak slate
that's what i'm saying
shy bramble
If it doesn't boot, openssh wont run either
peak slate
if systemd fails then neither dropbear nor openssh will save me from that, if it doesn't fail both or either work fine
so no real point in hacking away at dropbear if ssh works either way
shy bramble
I don't see how this is relevant to the statment that I made about not recommending you disable dropbear
peak slate
so no real point in hacking away at dropbear if ssh works either way
or rather, doesn't on dropbear
shy bramble
so no real point in hacking away at dropbear if ssh works either way
If you are going to reject my recommendations and ignore my warnings, I will no longer be helping you with issues
peak slate
yes, i know that rootfs will be wiped on an update
in that case i can reenable dropbear
as of current i don't really need it running
peak slate
at that point remarkable themselves is more likely to break dropbear on an update lol
but yes i understand that it can break on an update
shy bramble
If they break it with an update, it gets pulled as part of beta before it gets out
peak slate
worst case i don't mind having to recover it manually, i'm just using openssh as a hackfix that will work for the foreseeable future
and like
if an entware package explodes i feel like the likely >10k people running it on routers would notice before me anyway
shy bramble
if an entware package explodes i feel like the likely >10k people running it on ...
This has not been my experience
peak slate
yes it's reckless, yes i understand the issues but its better than a broken dropbear install :P
has entware ever even broken ssh packages xd
shy bramble
Okay, so you've decided to ignore my warnings and recommendations, and are choosing to run without a working dropbear. I will now be muting this thread and others can help you if they choose.
peak slate
👍
peak slate
🎉 and of course now something breaks and i have no ssh access