Escolar Documentos
Profissional Documentos
Cultura Documentos
Sent
/OITHAKA/OUFIRST
GROUIP/CNRECIPIENT
Sunday
October
S/CN
PM
ADMINISTRATIVE
10 2010 137
To Cc
Subject
RE MIT
is
currently
denied
JSTOR
Access
Thanks
for this
background
few thoughts
for
all
of
us
Id
like
us to
think
in
about
ramping
up
how we
deal
on
is
case-by-case reaching
to
basis
is
doing fyi
activity
its
job
et
modifying
as
thresholds as needed
it
out to librarians
learn that that
al
alerted
is
well But
that
some
instances
the
its
has
stopped
Where
the content
will
was downloaded
In
living
not on
someones
that
go
back
to say China
of
they commit to
being cooperative
If
dealing of
with matters
articles
in
abuse
and
we may want
reasonable
--
to
someone
is
downloading
us or
bOOs
what seems
collaboration
like
with us search
alerting
law
and
initiating
having
is
cop
retrieve
any
hard drive
of
contains
Our content
by savvy
in
extraordinarily
valuable
by the sweat
ones
brow
duplicated
hackers
pirating think
and
do
weve
touch
already
witnessed
our content
this
officials
China....
like
So
to
beginning
us to
about
or
One
time
realize
but
would
be law
in
with university
about
initiating
some form
of
enforcement Are
investigation to
we
prepared
Its
create an
deal as
alt
method
to
for
MIT
users
to
make
while this
is
being have
or
resolved
big
we know
Can
shut down
limited
will
whole
password
university
and
do
only
one OP address vs
other mechanisms
Is
range
so that notice
we
offer
access
heavy
us
some
we dont
lose
good
here
the MIT
library
site
there
of
way
for
to go out or be
making
users
it
clear
that
we
this
are
down
will
as
result
extreme
hacking
by someone
in
community
Otherwise
wont know
and
think
were
unreliable
From
Sent Sunday
October
10
2010
1052 AM
To Cc
Subject
RE MiT
is
currently
denied JSTOR
Access
Thanks
Just
to
clarify
at
the outset
the
1st
incident
that
happened
2nd incident
weeks ago
started
9/25
9/26
incident
they
reported
visiting scholar
responsible
for the
yesterday
was mistaken
was not
weeks ago
it
was
weeks
The
1st
incident
was excessive
institution
but seen
as
one
and
off
and
part
of
abuse
of
it
protocols
Robot
being used
of
IP
access
being denied
being responsive
asserting
they
care
We
have
any number
these on
weekly
few hundred
PDF5
per case
This
was
to
the tune
of several
thousand
from
what
understand
recognize
that
this
is
should
have
looped you
in
on
it
at
my
part
Ill
be
sure to do
It
was
satisfied
was
and
to
the
activity fantastic
did
not recur
was seen
an
efficient
robot
just using
new
patter
and
with access
bandwidth
through
MIT
Definitely
not any
kind
of service
attack
Basically
when
to
you
on
session
as
we have
the natural
progression
is
to
adjust
the pattern
one
of
which
is
simply start
new
sessions
more frequently
and
against
it
last
year when
of
abuse
protocols requiring
were
first
put
in
place
we
have and
some
version This
is
CAPTCHA
1st
download
every session on
that
once
if
again
randomly every
isolated
downloads
barrier
would prevent
for
this particular
scripting
My
opinion
is
that
these are
incidents that
special efficiency
too high
of
the regular
of scripting that
user
may
have seen on any
way From my
first
perspective the
live site
MIT
with
is
case and
the
will
first
this kind
we
and
the
to
threaten
its
They
likely
be embarrassed
this
has recurred
It
is
also
not clear
are
to
me
if
the
to
site
heavily
for
metadata
but
stable
URL5
PDF5 order to
or
all
of
the
above
prevent provide
We
adjusting of of
the abuse
pattern
down
try and
we
need end
precise
will
both
to
this kind
abuse
and
not disrupt
normal
To that
hit
and
rules
recap have
the incident
and
the numbers
surrounding
as
they never
our abuse
the
1st
or
time
no
window
into
the numbers
themselves
The second
occurrence
as
will
it
stands
us
started
at
some
point
yesterday
but
am
unclear
as to
when
that
was The
summary
give
that
to
this
point
began
communicating
chain
broadly from
about
it
shortly
before
pm
yesterday
and
the
IP
645
pm
and
first
began
communicating blocked
until
to
MIT
they
pm
will
remain
do made
will
be
sure to keep
you
both
looped
in
as
progress
is
against
both resolving
this issue
and
providing
summary
report
From
Sent Sunday
October
10
2010
933 AM
Access
To
Subject
Re MIT
is
currently
denied JSTOR
Thanks
Very troubling
Also
to
this
is
the
first
lye heard
of this
needs
to
be
This
involved
is
earlier of
in
to
ensure
activity
we
adhere
is
contract
pursue appropriate
call
remedies
part
we
established
The
noted
outright
theft
may merit
--
with university
counsel
left
--
and
isnt
even
leaving
the activity
has stopped
but that
who
with
containing
our database
please
in
clarify
the history
of
this activity
What
happened
weeks
ago How
did
we respond What
has happened
the intervening
time
three weeks
as
And what
lye heard
is
the
last
time
incident
Is
this
ago
Again
this
is
the
first
of this
is
Going
forward we need
are
make sure
that
is
aware
need
component
critical
other avenues
often
to
concurrently
From
Sent
Saturday October
09
2010
1118 PM
Access
To
Subject
Fw
to
MiT
is
currently
denied JSTOR
Just
want
be
sure
is
aware
of
the situation
From
Sent
Saturday October
09
2010
1030 PM
To Cc
Subject MIT
is
currently
denied JSTOR
Access
Good
Evening
want
to
make
at
you
aware
that Half
the MIT
of
abuse
case that
showed up
this
weeks ago
afternoon
came
to
back
today
forcing that
to
deny
up
18.0.0.0/8
Manchester
needed
at
restarting
address servers
got
jammed
due
to
this activity
emailed
our contacts
MIT and
informed
them
of
the situation
Just
for clarity
thats and
we
have
Last
that
visiting
scholar
was responsible
as
the scholar
am
when
pages
in
conversation
with
block
and
of their
is
range
reporting
that
this scraping
is
very intensive
control
and
threatening
the website
getting
unblocked The
and
has brought
the incident
under
and
deny
not threatening
the website
The
pattern
is
simple..
they start
session and
download
start
new
session
download
pdf on
and
on
can
comment
on
the specific
volume
duration
Also
in
after
the
last
incident
at
MIT we implemented
Literatums
of
sessions
per hour
is
IP
blocking
is
rule to applied
5000
sessions
60
minutes
It
did
not fire
We
are
digging
earliest
speculation
that
this rule
per server
this incident
which and
we
did
not anticipate
the number
down
based
on
data gathered
from
elsewhere
dont
know
as
if
this
will
cause
any
to
negative sure
reaction
in
the public on
and
havent heard
page and
that
anything
through
our feedback
channels extreme
yet
to
but wanted
make
we were
all
the same
there are no
surprises
here
This
is
an
block
combat
an extreme
attack
More
as
the situation
gets
resolved
Best
JSTOR
Portico
@ithaka.org