EPrints Technical Mailing List Archive

Message: #08739

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Antwort: RE: Antwort: Re: Spam to submitter via "Copy request" form

  • To: John Salter <J.Salter@leeds.ac.uk>
  • Subject: [EP-tech] Antwort: RE: Antwort: Re: Spam to submitter via "Copy request" form
  • From: <jens.witzel@uzh.ch>
  • Date: Mon, 13 Sep 2021 16:19:13 +0200
CAUTION: This e-mail originated outside the University of Southampton.

Thanks again John

i just looked at the request table ... very interesting :-) Storing the the privacy statement is a good idea.

Kind regards
Jens


--
Jens Witzel
Zentrale Informatik
Universität Zürich
Stampfenbachstrasse 73
CH-8006 Zürich

mail:  jens.witzel@uzh.ch
phone: +41 44 63 56777
http://www.zi.uzh.ch

Inactive hide details for "John Salter" ---13.09.2021 16:00:07---Yes - the privacy statement is a field that was added to the r"John Salter" ---13.09.2021 16:00:07---Yes - the privacy statement is a field that was added to the request dataset. It is stored as the ve

Von: "John Salter" <J.Salter@leeds.ac.uk>
An: "jens.witzel@uzh.ch" <jens.witzel@uzh.ch>
Kopie: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
Datum: 13.09.2021 16:00
Betreff: RE: Antwort: Re: [EP-tech] Spam to submitter via "Copy request" form




Yes - the privacy statement is a field that was added to the request dataset.
It is stored as the version of the privacy statement that was agreed e.g. 'request_v1'.
We only have one version at the moment, but if we revised this to make a v2 statement, we would store 'request_v2' in the database.
 
Cheers,
John
 
 
From: jens.witzel@uzh.ch [mailto:jens.witzel@uzh.ch]
Sent: 13 September 2021 14:47
To: John Salter <J.Salter@leeds.ac.uk>
Cc: eprints-tech@ecs.soton.ac.uk; jens.witzel@uzh.ch
Subject: Antwort: Re: [EP-tech] Spam to submitter via "Copy request" form
 

Hi John

thanks a lot for your quick answer. I'll keep an eye on it. Q: Do you store the "Privacy Agreement" click?

Of cause we analyse apaches logfiles and feed our badbot list, but unfortunately at the moment of sending the form it's to late ;-)

Anybody else doing the same or something different?

Cheers
Jens

--
Jens Witzel
Zentrale Informatik
Universität Zürich
Stampfenbachstrasse 73
CH-8006 Zürich

mail:  jens.witzel@uzh.ch
phone: +41 44 63 56777
http://www.zi.uzh.ch

Inactive hide details for "John Salter" ---13.09.2021 15:30:46---Hi Jens, We use the recaptcha stuff e.g. https://eprints.white"John Salter" ---13.09.2021 15:30:46---Hi Jens, We use the recaptcha stuff e.g. https://eprints.whiterose.ac.uk/cgi/request_doc?docid=23483

Von: "John Salter" <J.Salter@leeds.ac.uk>
An: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, "jens.witzel@uzh.ch" <jens.witzel@uzh.ch>
Datum: 13.09.2021 15:30
Betreff: Re: [EP-tech] Spam to submitter via "Copy request" form





Hi Jens,
We use the recaptcha stuff e.g. https://eprints.whiterose.ac.uk/cgi/request_doc?docid=2348396 .
The google.com version and recaptcha.net are essentially the same thing - but recaptcha.net isn't blocked in e.g. China, so we use that.

This does work well for us, and we also use recaptcha.net on our account creation and 'contact us' pages on our eTheses repository.

As the request details are stored in the EPrints database, you could do some analysis of these spam requests, and see if there are common themes - e.g. links in the request reason, or email addresses supplied?
You could also look at historic Apache logs and see if they all originate from the same place?

Cheers,
John




From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of jens.witzel--- via Eprints-tech <eprints-tech@ecs.soton.ac.uk>
Sent: 13 September 2021 13:34
To: eprints-tech@ecs.soton.ac.uk <eprints-tech@ecs.soton.ac.uk>
Subject: [EP-tech] Spam to submitter via "Copy request" form 

CAUTION: This e-mail originated outside the University of Southampton.
Hi out there

we have received some feedback regarding spam via the "Copy Request". Lots of emails gone to one submitter. Does anybody use any capture or something else in this direction?

First I found something in /usr/local/eprints/lib/workflows/request/default.xml (line 22ff.) - using googles capture https://www.google.com/recaptcha/about/ but for sure we will have problems with data privacy.

Second i found some hints in the Eprints wiki: A captcha pseudo-field based on http://recaptcha.net/
https://wiki.eprints.org/w/New_Features_in_EPrints_3.2

Anything else? Cookies, Perl driven stuff? What do you guys use?

Every hint is welcome

Jens

--
Jens Witzel
Zentrale Informatik
Universität Zürich
Stampfenbachstrasse 73
CH-8006 Zürich

mail:  jens.witzel@uzh.ch
phone: +41 44 63 56777
http://www.zi.uzh.ch