01:01:23 what did 4chan mean by running an ancient version of freebsd and getting hacked? 01:14:46 demido: They had servers running very old and un-patched versions of FBSD? 01:15:16 Not to mention the old software they were also running (which is likely the culprit as opposed to the OS itself.) 01:15:19 supposedly 01:16:07 personally i don't buy it. imo seems like an intentional leak. those vulns were present for years and woulda been used already 01:16:20 so i think an ancient stack was rolled out intentionally to open a door 01:16:47 I've heard from multiple sources recently that it was likely old PHP and/or phpMyAdmin that lead to the compromise. 01:17:05 ya but still, that woulda been found and used already 01:17:28 it's 4chan. it's prolly attacked more than gov mil and banks combined 01:17:32 Perhaps. If someone knew where to find it. Maybe they just found it? Who knows... 01:17:49 i have no inside info but i don't buy it 01:18:16 I'd imagine if anyone really cared, they'd look into it. I couldn't give two s**ts about it, personally. 01:18:38 ya i don't use the site but it's noteworthy 01:58:11 ek: You a dev ? 02:07:10 oxbar: Yes? 02:07:38 I'm not a FBSD dev, though... If that's what you mean. Just a regular, old Joe. 04:03:52 ek: j/w 04:04:06 jehovah's witnesses? 04:35:01 just wondering ? 05:23:08 Just wondering 08:00:56 will pkgbase ship in 15.0? 08:54:52 as far as I know that is currently the plan, but it was already planed for 14.0 and then delayed, well I didn't hear about problems with those pkgbase testrepos for -CURRENT and -STABLE 11:43:27 why is lib32 in base? what breaks if a world is built without it? 11:54:29 that you can run 32bit executables (why shouldn't it be shipped?) and why should anything break if you don't build libaries to run 32bit executables? they are completely optional (if you install a -RELEASE via the installer you get asked if you want to install the lib32 component) 12:26:53 pkgbase is nice 12:31:16 nimaje: ok, thanks 12:31:55 i don't know if i have any 32bit programs installed. how can i check? 12:32:54 i know if i without_kerebos for example, i'll need to build all my own ports with that in mind 13:04:08 f451: what FreeBSD do you have installed? 14.2-RELEASE ? 13:04:32 chances are if you don't specifically know of 32-bit installed programs and it is a recent install -- you have None 13:04:53 64-bit stuff has been the default for like over a decade now 13:13:03 SponiX: 14-stable 13:13:50 n270870 13:14:50 if it can be safely built without it then i'll do that. buildworld takes a while building lib32 and im looking to remove whats not needed 13:15:22 kerebos is another but ill need to remember to build all my own ports - same with hemidal 13:50:40 hey 13:50:51 i'm trying to port some linux code to freebsd 13:51:25 in linux i can dlsym(0,name) and get access to all the symbols in the c standard library 13:51:39 f451: I've never tried excluding anything from world, I just do the normal complete checkout and build 13:51:49 this doesn't seem to work on freebsd and i'm not sure what i'm supposed to pass to dlsym to get it to work 13:51:57 same for dlfunc 13:52:04 is this possible at all? 13:52:12 why do you need all the symbols of the c library? 13:52:20 i need one symbol 13:54:23 ah it looks like RTLD_DEFAULT does what i want 13:54:34 why is this not the same as on linux? am i misreading the docs? 13:54:55 because linus went off and did things his own way 13:58:15 looks like RTLD_DEFAULT is 0 on linux and ((void *)-2) on freebsd 13:58:42 that's perhaps a good reason to use the #define 13:59:47 i mean sure but i didn't realise passing NULL would do things differently from reading the freebsd manual 14:00:01 If dlsym() is called with the special handle NULL, it is interpreted as 14:00:03 a reference to the executable or shared object from which the call is 14:00:05 being made. Thus a shared object can reference its own symbols. 14:00:34 thought this could just access all the symbols that were currently loaded 14:01:07 anyway, thanks for the support 14:36:09 hi there, me again 14:36:22 scanf in freebsd doesn't support %m which is in posix 2008 14:36:36 is 17 years not enough? 14:41:40 <[tj]> https://pubs.opengroup.org/onlinepubs/9699919799/functions/fscanf.html 14:41:47 <[tj]> I can't see it 14:42:18 izabera: there is no %m specifier in C or POSIX 14:42:51 >An optional assignment-allocation character 'm'. 14:42:58 literally in yourlink 14:43:08 and in the version from 9 years prior 14:43:24 you guys are bad at reading 14:44:42 >The %c, %s, and %[ conversion specifiers shall accept an optional assignment-allocation character 'm', which shall cause a memory buffer to be allocated to hold the string converted including a terminating null character. In such a case yadda yadda yadda 14:44:43 izabera: you said %m 14:44:45 <[tj]> that isn't a %m thought 14:44:48 izabera: there is no %m specifier 14:44:56 ? 14:45:01 <[tj]> this really isn't a friendly way to speak 14:45:01 it's m that goes after % 14:45:07 izabera: there is an m flag to the %s specifier 14:45:11 for instance %ms 14:45:22 or %mc or %m[a-z] 14:45:45 either way, can i have that on freebsd 14:46:29 izabera: sure, you'll want to edit lib/libc/stdio/vfscanf.c, open a phab review when you're done and add me (des@) as reviewer 14:47:39 izabera: don't forget to update the manual page 14:48:41 <[tj]> can't believe I was tricked into reading posix 14:56:28 lol 14:58:33 is there a way to detect, in a src Makefile, which toolchain we're using? 15:05:49 [tj]: lol 15:15:39 desdotdev: why do you want to detect it in a Makefile? but I guess COMPILER_TYPE from share/mk/bsd.compiler.mk is the way then 15:20:12 Someone I know updated with pkg update and KDE broke 15:20:27 It seems like the missing core package is pkg install plasma6-plasma 15:20:44 <[tj]> ah, that happened to me too 15:21:07 is there a work around or just wait? 15:21:14 If you know 15:21:39 build from ports 15:21:44 maybe 15:22:21 they have been working on it in #freebsd-desktop 15:22:46 ah thanks for that irc channel 15:22:58 hm, from a system before the unification of kde5/6 into just kde without a version number in the package name? then install kde and remove kde5 or kde6 whichever was installed 15:23:33 It seems kde5 isn't fully there anymore 15:23:46 In packages 15:26:13 yes, that was renamed to just kde 16:14:52 tutorial for 14.1 were wrong 16:14:53 pkg install plasma6-plasma-desktop 16:15:24 @nimaje pkg install -g "plasma6-*" 16:15:59 I also used that and then when the login page came on the bottom left selected plasma 16:16:05 and its working again 16:16:28 I have multiple co-workers using FreeBSD and KDE as their desktop 16:17:16 why not pkg install kde as the handbook says? https://docs.freebsd.org/en/books/handbook/desktop/#kde-meta-install 16:21:55 I just tested that and it looks like the handbook needs to be updated 16:22:04 pkg install kde 'not found' 16:22:06 latest pkg release is missing packages, so that's why things are broken 16:22:29 If you had kde installed before last update, it warned you that it was going to uninstall kde. 16:22:38 pkg install plasma6-plasma 'not found' 16:22:54 mcrane: as I said, there are missing packages that were not built 16:22:56 This one exists pkg install plasma6-plasma-desktop 16:25:17 On the freebsd forum I found this pkg install --glob "plasma6-*" 16:25:21 and it does work 16:25:35 or shorted slightly to pkg install --g "plasma6-*" 16:25:38 or shorted slightly to pkg install -g "plasma6-*" 16:29:13 i thought the package builder issue was meant to be fixed now, although i can't remember where i read that 16:36:44 seems like additionaly to that bug in -CURRENT which made 14.2 jails crash when building packages, there is/was also a go bug where it can't handle the operating system using 5 level page tables, no idea if there where additional issues which coincidentally all happend on start of this month (afaik for the -CURRENT bug the builders were rolled back to some known good version and that shouldn't be 16:36:46 a problem anymore, not sure if the bug was found) 16:38:56 i only knew about the go issue which i believe they fixed by disabling la57 on the builders 16:42:14 maybe that go bug was the suspected -CURRENT bug, but as I understood it, something made the complete build crash, not just "some" packages not building 16:42:55 i recall there were some doubt about this because some of the missing packages didn't appear to depend on go, but a *lot* of stuff uses go and i never saw a definitive answer 16:43:42 webkit-gtk also had issues 16:44:08 I believe it was go and webkit-gtk if I remember correctly 16:47:42 it's fixed, but as of last report a few repos worth of packages were trying to sync at the same time 16:54:14 when did it get fixed? 16:54:19 I just checked yesterday 16:54:46 checking now :) 16:54:56 your definition of fixed and my definition of fixed are probably different 16:55:10 the underlying issue is fixed and the builds are finished, but they may or may not be available yet due to aforementioned package syncing 16:55:26 kevans: that was a couple of days ago though right? i wonder how long the sync takes 16:55:31 fixed == pkg has all missing packages returned. 16:55:51 about 22 hours ago if thunderbird isn't lying to me 16:56:05 oh, timekeeping is hard 16:56:37 "between today and tomorrow, they will be available on all mirrors." -- so presumably within the next 10-12 hours everything should be better 16:56:57 thanks, I'll check then and let people know once it's back working. 16:56:58 :) 16:57:36 maybe this will teach people not to play silly games with pointers 16:58:09 "oh, look at all the spare bits in this 64-bit pointer! i'm sure computers will never come with more memory and start using them!" 17:05:32 when does CHERI come to consumer hardware? then the hardware would disallow such silly stuff 17:11:06 probably never 17:12:27 AMA going on in the Discord FreeBSD right now 17:30:43 why? 17:31:55 who is "me" in that AMA? 17:32:16 la_mettrie: Deb Goodkind from FreeBSD Inc 18:06:49 Thought it was streaming video? 19:15:19 nimaje: https://codasip.com/solutions/riscv-processor-safety-security/cheri/x730-risc-v-application-processor/ 19:25:25 Last week I asked about a problem I had with 'ip moved from hardware address to ' all the time. Suggestion from someone here was to move the ip configuration from vlan interface to the bridge this vlan interface is member of. I did this, and since then those messages are gone 19:25:28 thanks again ! 19:26:30 igb0 up, no ip config. vlan6 up on physical interface igb0, no ip nor ip6 configured. bridge0 has member vlan6 and the ip4 and ip6 configs 19:26:32 problem solved 19:27:22 dstolfa: I can't find prices there, so it doesn't really sound "consumer", but reads like a good step in the direction of CHERI consumer hardware 19:27:43 nimaje: that's because it's not out yet :P 19:27:51 mvanbaak: i intend to advocate that we prevent people from configuring IP address on bridge members by default, so i appreciate your example as a justification for this :-) 19:32:37 it showed the ip address of the vlan interface changing from mac address all the time. from the physical interface mac address to a mac address of one of my vnet jails 19:33:15 ivy: yeah, that would be awesome. would have saved me some hours haha 20:01:02 dch: ivy: helloooo. the thing with capsicumizer is that LD_PRELOAD based filesystem fakery was way too janky. the future of that was being discussed in https://reviews.freebsd.org/D44373 20:01:23 * dch waves 20:01:32 thanks valpackett for the clarification! 20:04:54 valpackett: thanks! iiuc this is basically implementing a chroot for capsicum, which i really don't like, i'd rather have a config file to filter paths like how The Super Capsicumizer 9000 works. maybe i should read the whole thread though... 20:05:07 valpackett: incidentally thanks for your work on getting 9pfs into src, this has been super useful for me 20:11:03 How was the AMA 20:14:19 hi valpackett, your post on getting freebsd working on the pixelbook is what got me into freebsd :) 20:14:22 oxbar: fairly interesting but it was pretty high level and mostly about stuff the foundation is doing most of which you probably already know about if you care enough to hang about here. Setesh or wolfquinn is going to publish a recording later 20:34:11 hm, why does that review want to remove fchdir rights? would that disallow fchdir in capsicum mode or would that allow fchdir on any directory descriptor? both seem wrong to me 22:36:05 desdotdev: are you around? re: traceroute