hackerpain's comments

hackerpain | 5 years ago | on: Pidgin – A Universal Chat Client

Using it since a decade, I faced bugs in the PGP encryption add on, they need to work on a lot of things to make it secure. This is my go-to Jabber client.

hackerpain | 5 years ago | on: Ask HN: How did you turn your failed business model into a successful venture?

We spent like 12 years trying to create a medium sized business in electronics and we were at that time in an era when mobile phones were still getting popular. It was a nascent stage of refurb smartphone industry but even then it was a steep climb for us!

But there are companies operating in the same segment that started later, with VC and investor backing who rose quite fast.

hackerpain | 5 years ago | on: Stealing private documents through a bug in Google Docs

I am sorry but that can ruin your career as its illegal. You can't sell or, trade vulnerabilities on live websites like Google as per the terms and conditions of the Google VRP (Responsible Disclosure policy) while it may seem unfair, its illegal to do so.

hackerpain | 5 years ago | on: Stealing private documents through a bug in Google Docs

docs.google.com didn't have X-Frame-Options: DENY nor a restrictive CSP so I think its a browser quirk (rather, a clever bypass) that works here. Also, the author had exploited a postMessage flaw which wasn't validating the host name properly that led to the cross-origin leak of screenshot data

Check this out https://youtu.be/KpkrTUHoWsQ (video about URL validation bypass and SOP)

hackerpain | 5 years ago | on: Stealing private documents through a bug in Google Docs

this one technically requires some user interaction

Anyway, in the past I found a way to takeover an organization account in Google cloud acquisition and they rewarded me $100, saying their "Panel" decided that, Google's VRP panel sucks, so you're right about that.

hackerpain | 5 years ago | on: SolarWinds leaked FTP credentials through a public GitHub repo since 2018

The researcher added there may be some certificates exposed in that repo which may have been used to sign the binaries. It's still a relevant update.

Especially the information that the repo was archived by Web Archive back in 2018. It's not easy to know the "who" but the how can be speculated and investigated.

page 1