Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Phrack 72

phrack.org

Post reply on HN
Print view View original

21–30 of 34 posts

Re: Phrack 72

#21

Post by jpfromlondon »

supermatou wrote: post #3

Must read https://phrack.org/issues/72/19#article

I can't help but see security professionals as fakers, they seem to mostly be box-tickers rather than the professionally curious, in school and college I was up to no good with tech, but now when my employer is recruiting to establish an in-house cyber team I know I'm not what they're looking for and never was.

I exclude the RE guys who are undoubtedly extraordinary.

Re: Phrack 72

#23

Post by jmclnx »

Odd, did something change with phrack ? I usually go there using lynx, but this time I get "Alert!: HTTP/1.1 308 Permanent Redirect"

Will try dillo but I guess I will be stuck using Firefox.

edit: dillo worked fine.

Re: Phrack 72

#24

Post by awithrow »

jpfromlondon wrote: post #21
supermatou wrote: post #3

Must read https://phrack.org/issues/72/19#article

I can't help but see security professionals as fakers, they seem to mostly be box-tickers rather than the professionally curious, in school and college I was up to no good with tech, but now when my employer is recruiting to establish an in-house cyber team I know I'm not what they're looking for and never was. I exclude the RE guys who are undoubtedly extraordinary.

I think like most things there is a power law distribution when it comes to these sort of roles. I've worked with a few really good security teams in my career. The good ones work with the teams, possibly embedded on improving security. The better ones also write tools and libraries for service teams to consume. The best ones act like internal white hats, constantly probe and assess, and submit patches as well.

Sadly the vast majority of sec teams are not this and exist solely to run some tool that spits out a list of dubious vulns and then dump said list as a pile of tickets into the dev backlog.

One place i worked, the CISO even came up with some slogan for the info-sec along the lines of "observe and report" after I kept trying to show the info-sec how to run, build, test, and patch our various packages and tools their scanners would complain about.

Re: Phrack 72

#28

Post by contingencies »

anthk wrote: post #18
contingencies wrote: post #13

Earlier quoted context omitted.

https://underground-book.net/download.php3

I hate it. It destroys the original concept of hackers, with the original Jargon file, the best relase (1.5). Lisp and Forth hackers are the original thinkerers. The Jargon File https://jargon-file.org/archive/jargon-1.5.0.dos.txt https://hakmem.org/ These are actual hackers and hacks.

That ship had sailed well before the ~1997 launch of the book. See for example https://en.wikipedia.org/wiki/Hackers_(film) (1995) or http://www.takedown.com/ (1996)

Re: Phrack 72

#29

Post by alecco »

jmclnx wrote: post #23

Odd, did something change with phrack ? I usually go there using lynx, but this time I get "Alert!: HTTP/1.1 308 Permanent Redirect" Will try dillo but I guess I will be stuck using Firefox. edit: dillo worked fine.

lynx! Now this is nostalgia. Thank you.

Re: Phrack 72

#30

Post by tgrcode »

alisonatwork wrote: post #6

There is an ASCII chart in https://phrack.org/issues/72/18_md#article which references https://arxiv.org/pdf/2008.07753 [PDF], a 2020 article showing that open source peaked in 2013. In some qualitative sense that feels intuitively correct, but I am skeptical that in the modern world filled with a zillion NPM dependencies and the cloud YAML explosion and now vibe-coded everything that we are actually producing less l…

That is my article. The data source (Open Hub) may not be completely representative of open source, but the precise trend I was aiming to cite was hard to find elsewhere (and especially to find a graph for!)
Post reply on HN