Live data from Hacker News

Basics of Making a Rootkit – From syscall to hook

d0hnuts.com

11–20 of 23 posts

Re: Basics of Making a Rootkit – From syscall to hook

#11
post #9
post #3

Submitted two days ago: https://news.ycombinator.com/item?id=13243654 with (AFAICT) the exact same URL. Why didn't the dupe detector catch this?

No comments, only very few upvotes, then the dupe detector only blocks for a short time AFAIK.

Heh, whaddya know. I thought the dupe timeout was weeks or months but apparently it's <2 days. I wonder what the actual value is.

Re: Basics of Making a Rootkit – From syscall to hook

#13
post #12
post #8

Earlier quoted context omitted.

I hate memes too, but give this article a go. It's pretty good.

Ugh I hate being wrong (and realising I'm impatient and surly). Thanks for the nudge in the right direction, it was nice after all.

Whatever it was, thanks for fixing it.

Re: Basics of Making a Rootkit – From syscall to hook

#14
post #11
post #9

Earlier quoted context omitted.

No comments, only very few upvotes, then the dupe detector only blocks for a short time AFAIK.

Heh, whaddya know. I thought the dupe timeout was weeks or months but apparently it's <2 days. I wonder what the actual value is.

I think the point is that the timeout is not a fixed value but more of an algorithm. No traction, shorter timeout. Other factors probably come into play. HN works in mysterious ways.

Re: Basics of Making a Rootkit – From syscall to hook

#15
I found the suterusu rootkit to be feature-full and very well written. It covers all sorts of things a rootkit would do: https://github.com/mncoppola/suterusu

I never wrote kernel code before, but within 24 hours I was able to write a 'whitekit' that installs and hides as a rootkit and reports on sneaky behavior in dmesg:

https://github.com/matthewaveryusa/whitekit/

Fun stuff!

Re: Basics of Making a Rootkit – From syscall to hook

#16
post #11
post #9

Earlier quoted context omitted.

No comments, only very few upvotes, then the dupe detector only blocks for a short time AFAIK.

Heh, whaddya know. I thought the dupe timeout was weeks or months but apparently it's <2 days. I wonder what the actual value is.

Maybe so people don't spam a link, hoping more people see it. At least that's my guess.

Re: Basics of Making a Rootkit – From syscall to hook

#17
post #12

Earlier quoted context omitted.

Ugh I hate being wrong (and realising I'm impatient and surly). Thanks for the nudge in the right direction, it was nice after all.

Whatever it was, thanks for fixing it.

I moaned about the meme image as an opener :)

Re: Basics of Making a Rootkit – From syscall to hook

#18
post #11
post #9

Earlier quoted context omitted.

No comments, only very few upvotes, then the dupe detector only blocks for a short time AFAIK.

Heh, whaddya know. I thought the dupe timeout was weeks or months but apparently it's <2 days. I wonder what the actual value is.

Submissions without comment can be resubmitted pretty much any time; otherwise I believe it is a year or moderator intervention.

Re: Basics of Making a Rootkit – From syscall to hook

#19
post #11
post #9

Earlier quoted context omitted.

No comments, only very few upvotes, then the dupe detector only blocks for a short time AFAIK.

Heh, whaddya know. I thought the dupe timeout was weeks or months but apparently it's <2 days. I wonder what the actual value is.

Here's what dang said a year ago: https://news.ycombinator.com/item?id=10223645

>> We've adjusted the dupe detector to reject fewer URLs. If a story hasn't had significant attention in about the last year, reposts are ok. That's been the policy for a while, but we've brought the software closer to it. It will still reject reposts for a few hours, though, to avoid stampedes. Allowing reposts is a way of giving high-quality stories multiple chances at making the front page. Please do this tastefully and don't overdo it.

>> When reposting, please don't delete the earlier post. Deletion is for things that shouldn't have been posted in the first place, such as if you regret having said something publicly.

>> When a story is a duplicate—that is, has had significant attention on HN in the last year or so—it's helpful to post a comment linking to the previous major thread, so users and/or moderators can flag the dupe. In addition, when a URL isn't the best source for a given story, it's helpful to post a better URL in the thread. We often see those and change the posts to use them.

Here's a recent comment about what might count as significant attention: https://news.ycombinator.com/item?id=13110615#13141500

> jsnell's correct, and I'll add that reposts are ok on HN if an article hasn't had significant attention yet. 23 points and no comments (which a previous submission had) would normally count as significant attention, but we sometimes relax the criteria when an article is substantive and seems likely to interest the community.

> When we put stories in the second-chance pool (described at https://news.ycombinator.com/item?id=11662380 and earlier posts linked from there), we try to pick the original submission as the one that reaps the benefit.

The guidelines ask that these type of questions are sent to them rather than posted in threads. But I feel guilty about saying (no matter how politely) "email the mods". It feels like I'm dumping work on them.

Re: Basics of Making a Rootkit – From syscall to hook

#20
post #3

Submitted two days ago: https://news.ycombinator.com/item?id=13243654 with (AFAICT) the exact same URL. Why didn't the dupe detector catch this?

Per your comment, I wrote a Chrome extension that creates links to other HN submissions pointing to the same URL. Hovering over the links provides additional details.

This provides similar functionality as the 'past' link in a submission's subtitle, but shows the duplicates automatically.

Here's the extension:

https://chrome.google.com/webstore/detail/hacker-news-duplic...

Here's the source code:

https://github.com/dstein64/hn-duplicate-detector

Post reply on HN