I've had a string of requests from Linode support staff that I block access
to certain IP addresses. They've restricted traffic to my exit node several
times when I've been slow to respond to their requests.
--Lee
On Sat, Aug 27, 2016 at 4:25 PM, Sarah Alawami wrote:
> Keeping an eye on things.
Keeping an eye on things. Support asked me how I would prevent the copyright
material from being accessed or even gotten to on the server. I gave them
something about firewalls and keeping an eye on ports and blocking unnecessary
ones. They will close the case after 48 hours of no complaints. Th
No they did not as you saw in the excerpt I posted. I told them now all is well
with out going into detail. I had 24 hours to send them an all clear or they
would restrict my network bandwidth and I want the gigabit connection for all
the services I run on my vps. So it has ben up and running I
That is not a DMCA complaint, a complaint under the DMCA is required to
be specific, and reports are made under oath and penalty of perjury that
the complainer owns the copyright for the item in question.
However, your host may not be passing on all the details to you, that's
a matter of discussio
No, the DMCA was not specific. That's all they told me was that copyright
material were going through the vps and I was breaking the TOS.
> On Aug 22, 2016, at 5:19 PM, Mike Perry wrote:
>
> Sarah Alawami:
>> Hello to all. Sadly I have to shut down my tor relay after less then 24
>> hours, as
Sarah Alawami:
> Hello to all. Sadly I have to shut down my tor relay after less then 24
> hours, as I received a copyright violation and I don't want any network
> restrictions placed on me as I want the 150mbps speed.
>
> Sorry to all who were using it, but yeah there it is.
Was this a DMCA
Nah I'll just wait to see if I get any more complaints. I think it was torrent
stuff using it. I have receed nothinge else from them so far and I assume that
the problem has ben resolved. I guess I could go log diving if I'm wanting
something to do. Lol!
> On Aug 21, 2016, at 8:58 PM, Mirimir
On 08/21/2016 09:33 PM, Sarah Alawami wrote:
> Actually, no ip complained. It was the VPS I am hosting this thign on. I'll
> keep an eye on logs I gguess when I have the time.
Well, presumably someone complained to the VPS provider, triggering
their complaint to you. So you could request a copy
Actually, no ip complained. It was the VPS I am hosting this thign on. I'll
keep an eye on logs I gguess when I have the time.
> On Aug 21, 2016, at 3:26 PM, Mirimir wrote:
>
> On 08/21/2016 04:13 PM, Sarah Alawami wrote:
>> Well I could be nasty and reject port 443 and 80, but that's like cho
On 08/21/2016 04:13 PM, Sarah Alawami wrote:
> Well I could be nasty and reject port 443 and 80, but that's like chopping
> off someone's head when they have a headache. I believe i added those ports
> as excepts. I can't remember now.
One approach is blocking traffic to IP ranges that complain
Well I could be nasty and reject port 443 and 80, but that's like chopping off
someone's head when they have a headache. I believe i added those ports as
excepts. I can't remember now.
> On Aug 21, 2016, at 10:02 AM, Flipchan wrote:
>
> Dont forget port 993 for imaps(imap with ssl) so You can
Yeah I used debian for this I did issue a sudo service tor reload. And all
worked as expected according to the log anyway.
Blessings and happy Sunday
> On Aug 20, 2016, at 5:17 PM, Anthony Papillion
> wrote:
>
> One last thing: don't forget to restart Tor after you modify the file.
> If you're
Yeah, the exit policy you gave me essentially does that. We'll see. Is there
anyware I can look in /var/log/tor/log for me to keep an eye on things? I I'm
not good at log diving, but I've had to do my share.
Blessings and happy Sunday
> On Aug 20, 2016, at 3:49 PM, Anthony Papillion
> wrote:
Dont forget port 993 for imaps(imap with ssl) so You can use ssl with imap
Anthony Papillion skrev: (21 augusti 2016 01:39:01
CEST)
>It's actually pretty easy and you definitely don't have to be a coder:
>
>1. Find your torrc file and open it in a text editor
>2. Search for 'ExitPolicy' (all one
Quoting Sarah Alawami (2016-08-21 01:53:33)
> Ok, I modified it. We'll see what happens I guess. Bleh I have to start over
> with the tor cycle. Oh well, it's all a lyearning process. Eh?
> > On Aug 20, 2016, at 4:39 PM, Anthony Papillion
> > wrote:
> >
> > ExitPolicy accept *:80
> >
One last thing: don't forget to restart Tor after you modify the file.
If you're using Ubuntu just issue a
service tor restart
Good luck!
On 8/20/2016 6:53 PM, Sarah Alawami wrote:
> Ok, I modified it. We'll see what happens I guess. Bleh I have to start over
> with the tor cycle. Oh well, it'
Ok, I modified it. We'll see what happens I guess. Bleh I have to start over
with the tor cycle. Oh well, it's all a lyearning process. Eh?
> On Aug 20, 2016, at 4:39 PM, Anthony Papillion
> wrote:
>
> ExitPolicy accept *:80
> ExitPolicy accept *:443
> ExitPolicy accept *:110
Thanks. Yeah I'm not that bright. Lol! Anyway for those that want to know
hwere is the message I received from my vps. *frown* I'll work on this tonight
Hello,
We have received a report of copyright-infringing materials being accessed by
your Linode. We ask that you investigate this matter and
It's actually pretty easy and you definitely don't have to be a coder:
1. Find your torrc file and open it in a text editor
2. Search for 'ExitPolicy' (all one word) to find the right section
3. Enter a list of the ports you want to allow. Example:
ExitPolicy accept *:80
ExitPolic
Well I'm no coder. How do I then do this? I'm going to start over from scratch,
maybe. I dont' know much about the exit policies as I'm quite new to this tor
thing lol! I wonder what is trigering this to happen on our vps's, at least o
my vps. Lol!
> On Aug 20, 2016, at 4:23 PM, pa011 wrote:
>
Made the same experience this week within 24 hours as well on Bit Torrent
Changed my Exit-policy - never had that before...
Go on...
All the best
Paul
Am 21.08.2016 um 00:49 schrieb Anthony Papillion:
> On 8/20/2016 5:47 PM, Sarah Alawami wrote:
>> Hello to all. Sadly I have to shut down my to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 8/20/2016 5:47 PM, Sarah Alawami wrote:
> Hello to all. Sadly I have to shut down my tor relay after less
> then 24 hours, as I received a copyright violation and I don't want
> any network restrictions placed on me as I want the 150mbps
> speed.
Hello to all. Sadly I have to shut down my tor relay after less then 24 hours,
as I received a copyright violation and I don't want any network restrictions
placed on me as I want the 150mbps speed.
Sorry to all who were using it, but yeah there it is.
Blessings.
--
tor-talk mailing list - to
23 matches
Mail list logo
