madwoota has quit [Read error: Connection reset by peer]
Slimey has quit [Read error: Connection reset by peer]
madwoota has joined #openwrt-devel
Tapper has quit [Ping timeout: 480 seconds]
MaxS0niX has quit [Quit: Konversation terminated!]
<Znevna>
no? no :<
<slh>
the situation is quite simple, you need some kind of ssl/ tls provider - among these, we have openssl, wolfssl and mbedtls (and theoretically libressl). mbedtls currently isn't good enough for hostapd (and it's relatively slow and feature limited in general), wolfssl hasn't really held its promises (it's been buggy/ borderline broken in terms of basic features, ABI stability is a joke), openssl is
<slh>
seeing more public scrutiny, it's what most projects are using - it's bigger, but faster and more compatible
<slh>
there are still reasons for either of those
<slh>
but it's not a case of openssl being 'evil'
Tapper has joined #openwrt-devel
floof58 has quit [Ping timeout: 480 seconds]
<yolo>
actually the only option on the table is openssl, forget about the rest for now. yes it's 1MB in size but wolfssl itself is 500KB anyways, we're really talking about 500KB size increase, it's acceptable on 8MB flash I feel
<yolo>
i want to use mbedtls for my MCU/freertos board as there is no way to fit openssl, plus I don't run hostapd there so tls1.2 is good enough for a small https
<yolo>
mbedtls tls1.3 is very partial, it will take a while for hostapd support for sure.
Lynx- has joined #openwrt-devel
csrf has joined #openwrt-devel
minimal has quit [Quit: Leaving]
Slimey has joined #openwrt-devel
Lynx- has quit [Quit: Going offline, see ya! (www.adiirc.com)]
<mirko>
how does openwrt ensure enumeration of network devices stays the same (eth0, eth1, ..) across changes? it doesn't, does it? any way to fix it to a mac-addr without udev or otherly bloated helpers?
<slh>
it depends, in some cases it's defined in DTS (in others it may be a bit of closing the eyes and hoping for the best)
<slh>
even udev on big iron linux isn't always good at doing so...
bluew has quit [Remote host closed the connection]
<enyc>
slh: where does GNUtls fit into your analysis?
<slh>
enyc: gnutls is pretty much a GPLv2 compliant alternative, mature, but very much behind on features and reliability - and in general not very relevant to OpenWrt as a whole (due to it not being supported by hostapd). with msmtp in the spotlight, the situation 'might' be different for that particular use case
<enyc>
slh: Interestingly, Debian decided OpenSSL is component normally supplied with OS and subject to GPLv2 linking exception clause
<slh>
well, that's a fairly recent decision/ re-definition (and imho rather questionable) - and openssl v3 also changes the equation somewhat