From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] user agent spoofing
Date: Wed, 26 Aug 2015 22:34:35 -0700 [thread overview]
Message-ID: <87y4gxwaz8.fsf@mushroom.localdomain> (raw)
In-Reply-To: <alpine.LRH.2.03.1508261542090.18174@carhart.net> (Kevin Carhart's message of "Wed, 26 Aug 2015 16:19:31 -0700 (PDT)")
Kevin Carhart <kevin@carhart.net> writes:
> In addition to reading the settable user agent string, they test
> hundreds of things over javascript, and create a unique hash based on
> the answers.
Well, this is true. But spoofing the user-agent header is still often
quite effective. There are sites out there that block edbrowse for no
good reason. I seem to remember that in the past an example was
kpfa.org or kpfk.org, don't remember which one, but it was one of the
Pacifica stations. They fixed this at some point.
But spoofing user-agent turned a 403 to a 200.
There are other sites that autoblock edbrowse; I find them from time to
time. They don't autoblock lynx. So I wonder, is someone using
edbrowse for "questionable" purposes? Five will get you ten that they
are. It's also possible that someone has preemptively added edbrowse to
some sort of list or lists of "browsers that should be blocked", after
deciding that it had a possibility of "mis-use". Let's not kid
ourselves here; I'm sure there are those who consider edbrowse highly
subversive.
-- Chris
prev parent reply other threads:[~2015-08-27 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 23:19 Kevin Carhart
2015-08-27 5:34 ` Chris Brannon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4gxwaz8.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).