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