jcs

21 September 2018 at 10:46am
WE ENCOURAGE CUSTOMERS TO VALIDATE DOMAINS IN ADVANCE TO AVOID POSSIBLE LENGTHY DELAYS IN PROCESSING CERTIFICATE REQUESTS Q1) What is the change? From 1 August, new industry regulation states that Certificate Authorities (CAs) must no longer rely on checking a public WHOIS record to validate domain ownership. Instead, customers requesting a certificate must demonstrate a ‘positive interaction’ to show they have control over/ownership of the domain to be used in a certificate.
27 June 2018 at 10:20am
Change to Certificate Service – from 1st March 2018 Q1) What is the change in the maximum duration of certificates?     A) The maximum duration will be limited to 2 years, currently this is 3 years. Q2) What certificates are affected?     A) Only medium assurance Organisation Validated (OV) certificates. High assurance Extended Validation (EV) and Wildcard  certificates are already limited to 2 years. Q3) Who is driving this change?
15 August 2017 at 9:46am
The change to the number of credits required for certificates with 5 or more domains takes effect from 5 September 2017. The cost of Mixed certificate credit bundles will remain unchanged. The only changes are as follows:
13 February 2018 at 2:34pm
We're pleased to announce that from today the service can provide end user certificates, which are used for digitally signing and encrypting emails. These are called S/MIME (Secure/Multipurpose Internet Mail Extensions) certificates. S/MIME are installed on email clients which then enable the end user to send digitally signed emails, giving recipients assurances that the email originated from the sender's account. By signing emails, recipients can also have confidence that the contents of the email has been been altered in transit.
24 January 2017 at 2:07pm
The service changed certificate provider to QuoVadis in 2015, and as part of that transition Jisc is obliged to ensure all organisations that use the Certificate Service comply with and agree to a QuoVadis ‘Sub-LRA Agreement’. We have therefore updated the Certificate Service Terms & Conditions to reflect this.
25 May 2016 at 11:12am
I'm pleased to announce that from the 12 May 2015 the Janet Certificate Service will be providing SSL certificates signed by QuoVadis CA.
20 November 2014 at 4:56pm
SHA-1 and Google Chrome: 20 November 2014 On 18 November Google released Chrome 39 which will now result in users visiting web services secured with SHA-1 certificates that expire in 2017 being shown a grey padlock with a yellow warning triangle, instead of the usual recognisable green padlock.
30 March 2015 at 1:32pm
Availability of SHA-256 certificates: 14 October 2014We’re pleased to announce an agreement has been reached between TERENA and Comodo which will enable customers to obtain SHA-256 certificates. This is available with immediate effect and all certificates obtained from the service will be by default SHA-256.
17 April 2014 at 4:39pm
If you have been affected by the OpenSSL bug, dubbed ‘heartbleed’ and need to replace SSL certificates as a result of this vulnerability, we are happy to replace the certificate credit used to obtain the replacement certificate. Registered authorised users should first obtain the new SSL certificate in the usual way from their Janet Certificate Service account using the following link:  https://community.ja.net/apps/janet-certificate-service.  
Subscribe to jcs