[00:46] *** Guest15855 has joined #arpnetworks [00:47] There's been a font vuln every three weeks for the past, I dunno, four months. [00:48] mnathani_: There's not a lot of C _to_ learn. It's a dumb, simple language. I'd start by reading the code and looking up what you don't know. [01:34] mnathani_: While C wasn't my first language, I got myself to a functional point in a few weeks [01:35] the problem is that knowing how to do a few programs in C isn't the same as working on existing code bases. [01:35] The gotcha is it "wears well", in that the curve to mastery is slightly elongated [01:35] mercutio: I agree with that [01:35] I wouldn't characterize it as a problem necessarily however [01:35] and generally those that don't already know c are going to be a way off [01:36] at least in this day of ages [01:36] -s [01:36] https://www.securecoding.cert.org/confluence/display/c/SEI+CERT+C+Coding+Standard - here's a lot of reading on how to write better C. [01:36] 20 years ago not knowing c people used to generally have assembler knowledge. [01:37] but now days people tend to use higher level languages, with more distance from the system, so system coding is more foreign. [01:37] also things have got more complicated. [01:38] mike-burns: Thank you for the link. It looks very interesting [01:38] i suppose you could in theory do some stuff without knowing much C. [01:38] mercutio: My plan has been to learn both low and high level languages to glean what each experience had to offer [01:39] i learnt C when i was a teenger [01:39] teenager [01:39] it didn't take long. [01:39] i used the ANSI C book. [01:40] but i still get confused looking at things like network drivers. [01:40] Lots of moving parts :-) [01:41] and like i was checking out tcp source code on openbsd and linux [01:41] and the linux stuff is so hard to follow compared to the openbsd stuff. [01:41] it's more modular [01:42] well lots of stuff is only kind of documented. [01:47] probably if you look around you can find more documentation. [02:11] OpenBSD is super easy to read. It's a great introduction. [02:14] Preferences between URLs of the style: 1) /books and /books/$book 2) /books /book/$book 3) Other? [02:15] I prefer whatever Rails does by default. [07:09] * brycec <3's OpenBSD source, very clean, very easy to read [07:09] Though in my opinion, my preferred style that I find even more readable puts curly braces on the next line, so they obviously line up with the closing curly brace [08:12] *** tellnes has quit IRC (*.net *.split) [08:12] *** meingtsla has quit IRC (*.net *.split) [08:16] *** meingtsla has joined #arpnetworks [08:25] *** Guest15855 has quit IRC (Quit: WeeChat 1.0.1) [10:11] kind of neat: https://share.sandia.gov/news/resources/news_releases/tamper_detection/#.VaTr1LAU_UM [11:24] *** tellnes has joined #arpnetworks [12:59] brycec: I also put braces on their own line [14:35] *** sorressean has quit IRC (Read error: Connection reset by peer) [14:36] *** sorressean has joined #arpnetworks [14:54] i put braces on new line for functions, not for normal code [14:54] so many variations are around [17:36] ok USBIP rocks [17:39] makes things so much easier to add around the place w/o too much cabling [17:41] slowly adding USB ports around the place and decided to back the powered hubs into a data source too [17:41] devices plugged in anywhere could technically be attached to any computer on the network [17:41] (OS dependent ofc) [20:08] *** m0unds has quit IRC (Quit: brb) [20:10] *** m0unds has joined #arpnetworks [20:12] https://www.freebsd.org/security/advisories/FreeBSD-SA-15:13.tcp.asc in case anyone missed it [20:27] netstat -nxp tcp | \ [20:27] awk '{ if (int($NF) > 100) print "tcpdrop " $4 " " $5 }' [20:27] running that in cron is the recommended solution [20:28] oh the source has been fixed too [20:29] i didn't even know there was a tcpdrop command in freebsd [20:29] oh it's in openbsd too [20:29] but not linux [20:34] yea [20:34] i did the binary update right after i received the notification