EPrints Technical Mailing List Archive
Message: #07794
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, "Denis Munyua" <denis.munyua@gmail.com>
- Subject: Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Fri, 12 Apr 2019 12:53:35 +0000
Excellent!
A question for others (possibly to David or other core-committers): This issue has come up a few times previously on the tech-list. It's quite a bad situation in terms of the impact of this issue. Should we attempt to introduce a warning somehow e.g. at Apache startup, or from a 'bin/epadmin test' that warns of possibly dangerous
configuration like this? This specific issue is difficult - the repository appears to be normal - and working as expected… Cheers, John From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Denis Munyua via Eprints-tech Thank you, It was broken and commenting the "$r->connection->remote_ip' line under ~/archives/[ARCHIVEID]/cfg/cfg.d/security.pl fixed
the issue. Sincerely, On Fri, Apr 12, 2019 at 1:53 PM <eprints-tech-request@ecs.soton.ac.uk> wrote:
-- Denis Munyũa |
- Follow-Ups:
- Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- References:
- Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- From: Denis Munyua <denis.munyua@gmail.com>
- Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- Prev by Date: Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- Next by Date: Re: [EP-tech] Eprints-tech Digest, Vol 127, Issue 17
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):