| 29 Jun 2025 |
 hexa | to pull multiple gigabytes of outputs from the cache | 15:16:13 |
| hexa | that sounds a bit unrealistic | 15:16:17 |
| hexa | crappy eap support | 15:16:24 |
 @saiko:knifepoint.net | ahh.. :( | 15:16:32 |
 emily | I'm not seeing gigabytes | 15:16:44 |
| hexa | iirc the story is … drop your eap profiles into /var/lib/iwd somewhere | 15:16:51 |
| hexa | and you cannot configure them interactively from networkmanager | 15:16:58 |
| hexa | you know, the profiles, that your infrastructure administrator hands to you | 15:17:12 |
| emily | ModemManager closure is 237.98 MiB which is mostly like: systemd, glibc, etc. | 15:17:19 |
| emily | it doesn't seem to me like it should be adding much at all to NM closure if not for all this weird busted stuff | 15:17:33 |
| emily | that hardcoded OpenConnect path is what makes NM huge | 15:17:41 |
| hexa | otherwise I would gladly use it on the iso, given that it is quite a bit smaller than wpa_supplicant | 15:17:42 |
| emily | ✓ modemmanager-1.22.0 237.98 MiB (22.67 MiB) | 15:17:57 |
| emily | so it adds 22.67 MiB to the NM closure assuming openconnect is there | 15:18:13 |
| emily | and seems like little overlap | 15:18:18 |
| emily | so the networkmanager → modemmanager dep is not problematic | 15:18:27 |
| emily | the modemmanager module may be | 15:18:29 |
 K900 | Yeah, NM doesn't support provisioning 802.1x secrets into iwd | 15:18:45 |
| emily | hm no, module looks benign too | 15:18:59 |
| K900 | And iwd doesn't want to deal with external secret providers | 15:19:00 |
