Live data from Hacker News

Show HN: URL Canary – Get an alert when someone finds your secrets

urlcanary.com

51–60 of 122 posts

Re: Show HN: URL Canary – Get an alert when someone finds your secrets

#53
post #45
post #19

You might think about embedding bounties in crypto blockchains. For example, create BTC wallets that can be unlocked using a secret sitting next to (or steganographically embedded in) the secret you're trying to protect. This gives the person uncovering the secret an incentive to activate the canary. {RI,MP}AA are apparently doing this with their music and movies, so they know when they are showing up on pirate sites…

As skeptical as I am about crypto currencies, this is a really interesting application. Basically exploiting human greed. Thank you for sharing it.

That's some awfully pessimistic and dehumanizing language. I just consider it to be paying someone for the trouble rather than jumping straight to "exploiting greed."

Re: Show HN: URL Canary – Get an alert when someone finds your secrets

#54

Is following a URL common practice for someone who accesses documents? I mean if I come across a repository, my first inclination isn't to find all of the hidden URL's and chase them.

It's common practice for robots and vulnerability analysis

Re: Show HN: URL Canary – Get an alert when someone finds your secrets

#55
post #33

Earlier quoted context omitted.

Not true. I know bitly and googl have those info pages, so I'll check them out when I am curious but am not sure whether I want to alert whereever it leads. I know I'll get more info at best, and don't lose anything at worst. For random URLs, I guess I could try whois lookups, but I'd be much more likely to just check it out than with a short URL which is easily checked out.

I think you missed my point. If seeing that the bit.ly URL redirects to a known-urlcanary domain would put you off visiting the URL, then seeing the raw known-urlcanary domain (not behind bit.ly) would also be enough to put you off visiting it.

Ah, yes, if that is the alternative, then of course. I thought it was between some shortened link and an unknown domain.

Re: Show HN: URL Canary – Get an alert when someone finds your secrets

#57
post #33

Earlier quoted context omitted.

Not true. I know bitly and googl have those info pages, so I'll check them out when I am curious but am not sure whether I want to alert whereever it leads. I know I'll get more info at best, and don't lose anything at worst. For random URLs, I guess I could try whois lookups, but I'd be much more likely to just check it out than with a short URL which is easily checked out.

I think you missed my point. If seeing that the bit.ly URL redirects to a known-urlcanary domain would put you off visiting the URL, then seeing the raw known-urlcanary domain (not behind bit.ly) would also be enough to put you off visiting it.

So, doesn't this mean you need to have a bunch of domains, none of which look like urlcanary domains? If you hide behind something like namecheap's whoisguard (customer, not affiliated with them), that would do the trick, right?

Re: Show HN: URL Canary – Get an alert when someone finds your secrets

#58

Is following a URL common practice for someone who accesses documents? I mean if I come across a repository, my first inclination isn't to find all of the hidden URL's and chase them.

It's common practice for robots and vulnerability analysis

[deleted]

Re: Show HN: URL Canary – Get an alert when someone finds your secrets

#59
post #56

So what happens when the three offered domains become widely known to be fake? Can this service be federated and use custom domains or is it just another game of whack-a-mole?

From the landing page: "...and it's easy to setup a URL Canary on a custom domain name."

Re: Show HN: URL Canary – Get an alert when someone finds your secrets

#60

Hah, that enterprise pricing is insane.

Indeed, at £1k (€1136, $1403) one might as well run an internal application. At a very basic level, it can be achieved with three lines of bash:

    while echo -en "HTTP/1.1 200 OK\r\n..." | nc -l $IP $PORT; do
        cat $MESSAGE | sendmail -i -t
    done
More complex configurations could still be worked out in <50 lines of Python.
Post reply on HN