Re:Non-technical security best-practices for open source pro...
by gus_massa on Saturday June 05, 2021 @07:43PM
(#27409361)
Most of these times, these request are unseen or forgotten. It's better to send it in an email to [email protected]
Re:Non-technical security best-practices for open source pro...
by vlmutolo on Saturday June 05, 2021 @06:27PM
(#27408924)
I wonder if the right approach here is for HN to just use the public suffix list [0], and then sites like SourceHut should be added to it.
Re:Non-technical security best-practices for open source pro...
by Jtsummers on Saturday June 05, 2021 @06:39PM
(#27408999)
Looking at that, it would work (to the extent the list is complete) for things like GitHub pages (at github.io, like foo.github.io) but it doesn't work for GitHub user pages and repositories like github.com/foo or github.com/foo/bar. If the URL included a ~ like old school user sites then it could be automatically detectable (assuming others don't randomly throw a ~ in to their paths) like our university websites back in the day with foo.edu/~bar or math.foo.edu/~bar. Of course, now you've got sites using @ (Replit) instead of ~ to indicate a similar notion (that it's a user page and not, properly, the work of the main server hosts/owners), and GitHub and others don't include any kind of sigil providing this kind of information.
Re:Non-technical security best-practices for open source pro...
by dredmorbius on Saturday June 05, 2021 @09:14PM
(#27409864)
Email the HN mods directly at [email protected]
Since GitHub submissions were altered to show more of the URL (enough to show user/team/organization name), could the same be done with other repository hosts like sr.ht?