xback has quit [Remote host closed the connection]
xback has joined #openwrt-devel
jeff___m has joined #openwrt-devel
jeff___m has quit [Remote host closed the connection]
jeff___m has joined #openwrt-devel
bookworm_ is now known as bookworm
jeff___m has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
goliath has joined #openwrt-devel
jeff___m has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
robimarko has joined #openwrt-devel
f00b4r0 has joined #openwrt-devel
rua has quit [Quit: Leaving.]
jeff___m has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
xback has quit [Ping timeout: 480 seconds]
xback has joined #openwrt-devel
vincejv has quit [Ping timeout: 480 seconds]
goetz has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
goetz has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
goetz has joined #openwrt-devel
rua has joined #openwrt-devel
rua has quit []
<russell-->
hmm. i'm having trouble with the mt7688 linkit. my master branch built vanilla image boot panics, tftp'ing a release image and bootm'ing gives me an "Uncompressing Kernel Image ... LZMA ERROR 1 - must RESET board to recover", which smells like a "kernel too big" error or maybe loaded in the wrong address. clues?
rua has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
jeff___m has joined #openwrt-devel
goetz is now known as Guest322
goetz has joined #openwrt-devel
Guest322 has quit [Ping timeout: 480 seconds]
<russell-->
randomly tftpboot'ing with a loadaddr of 0x84000000 and my initramfs.bin image booted
jeff___m has quit [Ping timeout: 480 seconds]
<russell-->
okay, wacky, sysupgrading from there and it boots
jeff___m has joined #openwrt-devel
jeff___m has quit [Ping timeout: 480 seconds]
goetz is now known as Guest324
goetz has joined #openwrt-devel
jeff___m has joined #openwrt-devel
Guest324 has quit [Ping timeout: 480 seconds]
goetz is now known as Guest325
goetz has joined #openwrt-devel
Guest325 has quit [Ping timeout: 480 seconds]
skynet2 has joined #openwrt-devel
castiel652 has joined #openwrt-devel
enyc has joined #openwrt-devel
<enyc>
Hrrrrrrrrrrrrrm; this may be my-fault but I NOTICE using 23.05-SNAPSHOT r23753-79a7195087 I find ssh key login isn't working; always have to enter password
<enyc>
with a relatively old ssh-rsa keypair
<enyc>
was working on 22.03.6 etc
jeff___m has quit [Ping timeout: 480 seconds]
<mrkiko>
enyc: there where some changes to dropbear check also if the build you're using is compiled with modern crypto noly option enabled
<enyc>
mrkiko rmilecki : AHA thankyou; SO this leads to -- I really just need newer ssh key to stop all this, in short.
<enyc>
HOWEVER, I would NOTE that there is no warning in OpenWRT interface that you've put in an old-algorithm-key etc; IMHO this might be better reverted for 23.xx and put in as change+WARNING in 24.xx
<enyc>
(i.e. keep change in master, revert for 23.05 branch before 23.05.3 released)
<enyc>
no need to upset / lock people out on a 'stable' branch
<jow>
hauke: yeah, seen gcc 13 as well but I don't expect it an issue on x86
<jow>
hauke: I'm also leaning towards mold
<rmilecki>
DROPBEAR_MODERN_ONLY doesn't have default value
<rmilecki>
does it mean it's "n" by default?
<rmilecki>
i just checked, it is:Use modern crypto only [BREAKS COMPATIBILITY] (DROPBEAR_MODERN_ONLY) [N/y/?] (NEW)
<rmilecki>
enyc: are you sure you didn't enable this option accidentally?
<enyc>
rmilecki: fairly sure, where would that config change be stored
<enyc>
rmilecki: i just used the downloads.openwrt.org hidden 23.05-SNAPSHOT build and built a new config
<enyc>
rmilecki: i didn't knowingly change any dropbear settings at all
<enyc>
just put in the authorized_keys .. tried also putting in all of original authorized_keys dropbear_ed25519_host_key dropbear_rsa_host_key in /etc/dropbear and still the same
<enyc>
rmilecki: nowt about it in /etc/config/dropbear in any case, this seems to be a build-config matter