Hmm, how about no? "We launched an encrypted file transfer tool, but we forgot to sanitize input" is somewhat pathetic in 2019. What else has saferequest.net fucked up?

(hi, I'm one of the creators)

Hopefully we fucked up nothing else but please do let us know if we did :-) We do sanitize all input but unfortunately this one slipped through.

> You should give them some advertising.

I showed the article to the company before publishing it, and it included many references and links to their website.

The contact explicitly stated he didn't like it to get published, as it might damage their product image on quick Google searches by someone researching it (even though I praised the company in the article).

Removing direct references was a nice middle ground they accepted.

Why did you need their approval at all?

I didn't need it, but at the same time, I didn't want to be a d*ick and immediately expose their product without contacting them first.

Which is highly appreciated ;-)

(one of the creators of SafeRequest says hi!)

Because their intent was to provide a secure service, as is proven by their quick turnaround time well outside work hours.

Despite the lapse, they score high in authenticity, and given their small size, they deserve a second chance. Megacorps probably wouldn't have my sympathy.

He gave a pretty big hint on how to find the company.

"On the 24th of October, an article was posted on Tweakers (a Dutch tech website) showing off a newly released service to securely request files from someone through the web."

https://saferequest.net/

By the way, this is the article they are referring to [1].

[1] https://tweakers.net/nieuws/159002/amsterdams-bedrijf-start-...

The path in the thumbnail really gives it away - /var/customers/webs/timvisee/saferequest