00:53:21 <rtprio> dont use brave
00:57:36 <LXGHTNXNG> better to think twice before usingit, but yea i'm biased to think it's malware
01:42:09 <Macer> kerneldove_: i never had to do anything to get my ix devices to work
01:42:43 <Macer> they just worked out hte box
01:43:11 <Macer> what i'm curious about is fbsd arc (a310) support
01:52:20 <Macer> https://github.com/freebsd/drm-kmod/issues/364 ☹️
02:46:34 <kerneldove_> got ix working out of the box, tyvm
02:46:46 <kerneldove_> 10gbps of sultry bandwidth yess
03:48:26 <Matt|home> https://ibb.co/album/Kb5fLX <-- okay let's see if this works. first time baking a cake, had to improvise a lot, recipe looked insane but i guess we'll see
09:22:25 <TommyC> I don't hear much about browsers outside of Chrom{e,ium} and Firefox. What's wrong with Brave?
09:22:58 <ivy> TommyC: a lot of people dislike it because of its association with cryptocurrency
09:23:26 <dh> Brave is Chromium
09:24:13 <ivy> TommyC: also because it was founded by Brandon Eich, a famous homophobe
09:24:23 <ivy> Brendan
09:25:27 <TommyC> ah, lotsa controversies around it I see
09:26:43 <ivy> Vivaldi (a Chrome reskin, but with a fair amount of custom UI work) seems quite popular, but it's closed source and there's no freebsd version
09:29:13 <Macer> firefox esr is all that is needed :)
11:54:13 <Macer> https://reactos.org/forum/viewtopic.php?t=22603 <- i wanted to see if this was possible just to see if i could use rsat in it
11:54:31 <Macer> i doubt the ad bits are in it though
12:45:32 <JetpackJackson> Macer: why ESR over latest, out of curiosity?
13:34:29 <polarian> JetpackJackson: bullshit gets merged into it slower
13:34:39 <polarian> means your configs do not need to be updated as often
13:34:52 <JetpackJackson> Oh
13:34:59 <polarian> also less features == less places for code to be attacked
13:35:03 <polarian> and new code is what is easiest to attack
13:35:11 <polarian> so there are security benefits
13:35:19 <polarian> to not always taking the latest features
13:38:33 <LXGHTNXNG> new code isn't necessarily easier to attack by virtue of being new
13:38:49 <LXGHTNXNG> code does not age, it is changed
15:13:55 <polarian> LXGHTNXNG: new code has not had as many eyes on it, furthermore it has not existed for as long. A new feature is more likely to have vulnerable code over code which has been looked over and patched for many many years...
15:21:02 <ivy> i don't know if that's really true.  code that comes from 4BSD might not have been looked at for years and was developed before modern security context
15:21:29 <ivy> like, how long have we had rtsold?  did that come from KAME?
15:30:35 <polarian> ivy: we are talking about browsers here
15:31:00 <polarian> many of the changes made are features, not security improvements
15:31:39 <polarian> also I didnt say old code is secure, legacy crypto is a big issue
15:31:48 <polarian> legacy features which are not patched or maintained
15:31:56 <polarian> all have their own security concerns
15:32:38 <polarian> but comparing firefox and firefox esr which have the same underlying code but one has the latest features and one doesn't, I would trust the one without the new features
15:33:04 <polarian> if there is a vuln in legacy code, it will likely be in both firefox versions
15:33:08 <polarian> in which case... shit :)
15:51:51 <LXGHTNXNG> old or new code is not *inherently* less or more secure, it's less or more secure because of the literal nature of the code. code written in a time when networks could be trusted is more likely to be insecure because of the inherent trust that one won't put something malicious in it.
15:52:08 <LXGHTNXNG> not because it's old. it was insecure then and it's insecure now
15:54:43 <ant-x> Hello, all. Does not FreeBSD have strace? What can I use instead?
15:54:53 <ivy> ant-x: truss(1), ktrace(1)
15:55:29 <clapont> hi, everyone. I wish you happy christmas and a better new year!
15:55:33 <ant-x> ivy, thanks.
15:55:49 <ant-x> clapont, well seasoned-greating to you and all.
15:55:53 <ant-x> * greatings
15:56:16 <ant-x> * greetings
15:56:34 <clapont> yep, I prefer the last, thanks :-)
15:56:55 <ant-x> ktrace to truss :-)
16:06:44 <ant-x> ivy, which package provides the truss utility? ``pkg install truss'' on 14.3 complains that there is not such package.
16:10:07 <rtprio> FreeBSD-utilities
16:17:14 <ant-x> Is it available via pkg in 14.3? I can't find it.
16:19:01 <isley> it's part of base it should already be there you don't need to install it.
16:27:00 * ant-x slaps his forehead
16:29:30 <LXGHTNXNG> valid.
17:22:51 <kerneldove_> what causes state-insert (failures) in the output of pfctl -si? (state-insert    state insertion failure)
19:09:41 <nimaje> ivy: well the security bug is in resolvconf, rtsol only gives attackers an attack vector for it
21:02:44 <dogg0> so weird im using freebsd15 (happened with 14 too) guest, linux host.  terminal only.  when exiting vm i often get stuck in this weird purgatory that i dont even know how to get out of
21:03:51 <dogg0> looks like this: https://pastebin.com/BnLLifSq
21:06:25 <vkarlsen> dogg0: You're stuck in vi?
21:08:38 <dogg0> its ben happening alot only in this particular circumstance... i end up mashing keys and somestimes come out of it or reset
21:09:11 <dogg0> freebsd on bare metal or any other os as guest it never hahpens
21:29:58 <Liaf> If I want to fully encrypt the discs of my server, I want to use geli instead of gdbe, right? Also is there a way to enter the passphrase via ssh during boot? I have seen setups for this on some linux servers and wonder if those are individual solutions or if there's something like that already integrated :-)
21:31:25 <ant-x> dogg0, I don't understand. Is it inside the vi editor? Try: ESC : q ! (four keys in sequence)
21:31:48 <ant-x> vkarlsen, /Stuck in Mobile/ -- /Stuck in vi/
21:32:26 <ant-x> dogg0, as to how you can have got into vi -- it may be your default $EDITOR.
21:33:14 <ant-x> dogg0, how exactly did you cope that text to pastebin? Is it literally what you see in the terminal?
21:35:31 <ant-x> Usually, vi displays special characters with a ^ prefix, so that REG is ^M
21:35:33 <ant-x> * RET
21:59:02 <dogg0> ive been using vi for years.  but his happens only with freebsd guest in qemu.  and yes thats literally what i see in the terminal. i just highlight iwth mouse and paste here
21:59:31 <rtprio> sounds like your terminal is not entirely functional
21:59:34 <rtprio> what's $TERM ?
22:02:41 <dogg0> xterm-256color ?
22:03:23 <dogg0> idk im using everyting just ootb
22:07:49 <ant-x> My terminal is frequently broken in FreeBSD, but I never cared to establish a stable reproduction scenario.
22:23:56 <ant-x> I feel totally disoriented in my shell: <https://paste.c-net.org/ShermanJudgment> . Where am I?
22:29:40 <cyric> ant-x: you likely removed the directory you are in (ad1), easy to reproduce
22:31:09 <ant-x> Ah. Thanks. I did not mean that as an instance of a broken terminal though. A broken terminal is a situation where I cannot type normally.
22:35:10 <rtprio> ant-x: is this a quiz or did you make a broken symlink on purpose?
22:35:48 <ant-x> I did not make a symlink!
22:35:56 <ant-x> Nor is this a quiz.
22:36:43 <rtprio> looks like the directory was removed elsewhere while you were still in it
22:36:46 <ant-x> I got this in the middle of trying to trace why svn hangs at checkout with ktrace and truss.
22:37:00 <ant-x> rtprio, this is possible.
22:37:19 <ant-x> rtprio, I have read and accepted your suggestion earlier.
22:40:54 <vkarlsen> ant-x: Stuck in the middle with vi
22:46:22 <ant-x> vkarlsen, I was tyring to joke about this and the Bob Dylan song.
22:57:58 <voy4g3r2> ant-x: and the best rednition of that song, with pop culture, is reservior dogs
23:03:07 <ant-x> I dislike Bob Dylan and that song, but I love the movie!
23:28:15 <vkarlsen> ant-x: I followed up with Stealers Wheel