News for hackers. Stuff that matters.
Re:Using Goatse to Stop App Theft by NGRhodes on Tuesday October 17, 2023 @12:07PM (#37917239)
> This blog is now STATELESS. The entire post is contained in the URL that you are visiting now. All my "blog" is now is a hard-coded main page that contains links to posts I claim authorship of. Of course the entire post is contained in each of these links.

https://joshcsimmons.com/post/H4sIAAAAAAAA%2F3xV227cRgx911cQ...

Re:Using Goatse to Stop App Theft by chatmasta on Tuesday October 17, 2023 @12:11PM (#37917317)
Re:Using Goatse to Stop App Theft by bombcar on Tuesday October 17, 2023 @12:17PM (#37917445)
Yep, Josh has given everyone (apparent) write access to his site.
Re:Using Goatse to Stop App Theft by joshcsimmons on Tuesday October 17, 2023 @04:35PM (#37921203)
Awesome - and the first time I've actually had someone "post" on my site.
Re:Using Goatse to Stop App Theft by chatmasta on Tuesday October 17, 2023 @04:47PM (#37921367)
You're welcome. :D

The client-side XSS is mostly harmless (assuming you don't have any other sensitive services running with cookies scoped to this domain), although it's technically a persistent XSS, which means it could be indexed by search engines.

But is there a server-side component to this? I noticed that the "disclaimer" is added in the source returned by the server, so I assume there is some code that checks whether the post is present on the home page? If so, that could be dangerous, if there is a bug in that code such that a malicious payload in the URL could get RCE in your server process.

Re:Using Goatse to Stop App Theft by joshcsimmons on Tuesday October 17, 2023 @06:53PM (#37922641)
I've just added some defensive programming to the site. Sorry to say. Appreciate that you hacked it with your image onerror, pretty clever.

TBH I haven't thought about most of these things. Nobody typically reads my blogs when I've made them before and this is likely the only interest it will get for quite a while.

Re:Using Goatse to Stop App Theft by chatmasta on Tuesday October 17, 2023 @06:58PM (#37922684)
lol :) nice fix

Can't promise I won't circumvent it when I've got some time...

Re:Using Goatse to Stop App Theft by jeroenhd on Tuesday October 17, 2023 @05:48PM (#37922068)
Watch out: virus/scam/spam sites can detect sites like yours and write tons of redirects, link them somewhere, and use your site's good reputation to get their scams on the home page. This is also a huge problem for redirect services.

If the wrong person publishes the wrong link, you can get your domain banned from Google and tons of other sites as a "security risk", which can spread to your email (if you use @joshcsimmons.com).

It's fine if you don't care about blacklists of course, but this kind of abuse can easily sneak up on you.

Re:Using Goatse to Stop App Theft by mortallywounded on Tuesday October 17, 2023 @12:16PM (#37917426)
https://joshcsimmons.com/post/H4sIAAAAAAAAAyXMQQrCMBCF4b2neO...

Doesn't need to release tools... gzip, base64 and uri encode uh huh.

Re:Using Goatse to Stop App Theft by Quarrelsome on Tuesday October 17, 2023 @12:10PM (#37917299)
doesn't this mean I could embed salacious material into a link and fool people into thinking the person who owned this website wrote it?
Re:Using Goatse to Stop App Theft by generalizations on Tuesday October 17, 2023 @12:29PM (#37917613)
> Anything can be generated here. You could even host your own blog that uses my website as a renderer if you really wanted to. It supports markdown.

> Every post that I want to publicly claim authorship of lives at the root of this site. If you are reading a post that I have claimed it will look like this page. Posts of unknown authorship have a disclaimer at the top of the page.

https://joshcsimmons.com/post/H4sIAAAAAAAA%2F3xV227cRgx911cQ...

(His permalinks are horrible, lol)

Re:Using Goatse to Stop App Theft by jbarrs on Tuesday October 17, 2023 @12:42PM (#37917791)
>Posts of unknown authorship have a disclaimer at the top of the page.

Problem is, the posts can contain <script> elements. So it's easy to just write a little JavaScript that removes the disclaimer at the top. See this hastily-made, immature example of mine:

https://joshcsimmons.com/post/H4sIABO8LmUC/3VT0W7aQBB85yu2QV...

As it stands, this really isn't the most secure system. Something much more malicious could be injected into this!

Re:Using Goatse to Stop App Theft by pjot on Tuesday October 17, 2023 @01:24PM (#37918426)
I was halfway expecting goatse
Re:Using Goatse to Stop App Theft by latexr on Tuesday October 17, 2023 @04:14PM (#37920909)
Shouldn’t it be “shat”?

Either way, considering the submission we’re commenting on, the author of the blog may appreciate your humour.

Re:Using Goatse to Stop App Theft by joshcsimmons on Tuesday October 17, 2023 @07:00PM (#37922705)
Correct
Re:Using Goatse to Stop App Theft by joshcsimmons on Tuesday October 17, 2023 @06:59PM (#37922703)
This gave me a pretty good laugh. I have some sanitization and guards set up now. TBH I never really expected anyone to visit my blog.
Re:Using Goatse to Stop App Theft by bravetraveler on Tuesday October 17, 2023 @12:15PM (#37917406)
XSS as a feature, neat
Re:Using Goatse to Stop App Theft by hundchenkatze on Tuesday October 17, 2023 @12:48PM (#37917884)
Re:Using Goatse to Stop App Theft by joshcsimmons on Tuesday October 17, 2023 @06:54PM (#37922653)
unfortunately patched now
Re:Using Goatse to Stop App Theft by aosaigh on Tuesday October 17, 2023 @12:13PM (#37917367)
I don't understand how this helps ownership of content? What situation is this trying to avoid? You already "own" your URL if you own your domain?

EDIT: understand you are not the OP btw, just wondering out loud.

Re:Using Goatse to Stop App Theft by dinkleberg on Tuesday October 17, 2023 @12:40PM (#37917769)
The only thing I can think of is if they want to share controversial posts while having the ability to deny that they wrote it (as long as they don’t actually create a link to it from their own site).

It’s not a good use case IMO, but that is all I can think of lol

Re:Using Goatse to Stop App Theft by hk__2 on Tuesday October 17, 2023 @12:20PM (#37917489)
So if the author fix a small typo in the post, they break all the links to it. The blog is not "stateless", it’s just that its state is stored in the homepage. Having all posts on that page with anchor links would achieve the same thing with shorter links that don’t depend on the content.
Re:Using Goatse to Stop App Theft by cbsks on Tuesday October 17, 2023 @12:30PM (#37917630)
It won’t break any existing links. It just means that existing links will still have the typo.
Re:Using Goatse to Stop App Theft by perlguy9 on Tuesday October 17, 2023 @12:14PM (#37917382)
Tranlsation: This guy is insufferable
Re:Using Goatse to Stop App Theft by molo on Tuesday October 17, 2023 @12:12PM (#37917345)
If you're going to do that, you should at least generate shortened URLs as well.
Re:Using Goatse to Stop App Theft by hk__2 on Tuesday October 17, 2023 @12:18PM (#37917451)
But then it’s not stateless anymore.
Re:Using Goatse to Stop App Theft by Dylan16807 on Tuesday October 17, 2023 @12:25PM (#37917556)
It's not stateless at all because of the main page, so this is more of a weird anti-optimization.
Re:Using Goatse to Stop App Theft by amatecha on Tuesday October 17, 2023 @01:57PM (#37918964)
Huh, cool. I think it's a pretty terrible idea, but I'm glad people are still doing fun/creative things with websites. Keeping the spirit of the early web alive. haha :)
Re:Using Goatse to Stop App Theft by foxtrottbravo on Tuesday October 17, 2023 @02:35PM (#37919533)
But how does it know whether it should print the pretext?