Skip to content
This repository was archived by the owner on Jan 28, 2021. It is now read-only.

Change destination uri for tracker to Jisc domain#1

Open
Ainmhidh wants to merge 2 commits into
eprints:masterfrom
Ainmhidh:patch-1
Open

Change destination uri for tracker to Jisc domain#1
Ainmhidh wants to merge 2 commits into
eprints:masterfrom
Ainmhidh:patch-1

Conversation

@Ainmhidh
Copy link
Copy Markdown

tracker no longer needs to go via mimas, but should go straight to jusp.jisc.ac.uk/counter/

Comment thread lib/defaultcfg/cfg.d/pirus.pl Outdated
# modify the following URL to the PIRUS tracker location
#$c->{pirus}->{tracker} = "http://cclibweb-4.dmz.cranfield.ac.uk/tracker/";
$c->{pirus}->{tracker} = "http://www.jusp.mimas.ac.uk/counter/";
$c->{pirus}->{tracker} = "http://jusp.jisc.ac.uk/counter/";
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you suggesting it should use https rather than http? whilst it could is there any particular benefit / performance hit from doing this? Is there anything in the tracker ping that needs https?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Insecure http is deprecated

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's just no reason for it not to be https

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having spoken to Paul at IRUS, he suggests that there are components in the tracker message which could potentially be considered 'personal' within Europe, so using https would be advisable.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

insecure HTTP is deprecated, and one day browsers will stop supporting it at all:

Comment thread lib/defaultcfg/cfg.d/pirus.pl Outdated
@@ -66,7 +66,7 @@ =head2 Changes

# modify the following URL to the PIRUS tracker location
#$c->{pirus}->{tracker} = "http://cclibweb-4.dmz.cranfield.ac.uk/tracker/";
Copy link
Copy Markdown

@graingert graingert Jul 12, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#$c->{pirus}->{tracker} = "http://cclibweb-4.dmz.cranfield.ac.uk/tracker/";
# cclibweb-4.dmz.cranfield.ac.uk's x509 is currently self signed, for tofu grab the cert with:
# echo -n | \
# openssl s_client -showcerts -connect cclibweb-4.dmz.cranfield.ac.uk:443 2>/dev/null | \
# sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or just kill this example until cranfield fix their server!

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this connected to the previous comment on use of SSL or a separate suggestion that the example URI is outdated / broken?

Copy link
Copy Markdown

@graingert graingert Jul 20, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This server supports TLS but to get it working requires some client configuration because it's a self signed, expired, wrong domain certificate. So either add the docs I suggested above or remove the line completely until they can get a valid certificate. They could get a free one from let's encrypt.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the commented line, referring to Cranfield, as no-longer required

Also removed comment regarding Cranfield tracker URI
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants