Changes for page Announcements

Last modified by hbpadmin on 2025/01/09 12:12

From version 3.1
edited by mmorgan
on 2020/07/02 18:38
Change comment: There is no comment for this version
To version 7.1
edited by mmorgan
on 2020/12/10 14:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,19 +1,41 @@
1 -== Announcement ==
1 +(% class="wikigeneratedid" %)
2 +== SSL certificates (2020-12-04) ==
2 2  
3 -On the 14th of May 2020, several High Performance Computing centres across Europe suffered a cyber-attack. The attack affected the infrastructure which hosts multiple HBP and EBRAINS services. As a precaution, and in order to ensure the continued security of the HBP and EBRAINS services, all users with an HBP and/or EBRAINS user account are requested to change their password, both in Collaboratory 1 ([[https:~~/~~/collab.humanbrainproject.eu>>https://collab.humanbrainproject.eu]]) and Collaboratory 2 ([[https:~~/~~/wiki.ebrains.eu>>https://wiki.ebrains.eu]]).
4 +Our SSL Certificate provider (Let's Encrypt) has been rolling out a new algorithm for signing SSL certificates as described on their [[website>>https://letsencrypt.org/certificates]]. This requires updates on our servers and on your web browsers. The updates on your web browsers often go unnoticed by the user but in some cases your browser may inform you that it needs to fetch a new certificate. You can accept this safely; most browsers don't even mention it to the user.
4 4  
5 -The current passwords were deactivated in Collaboratory 1 on May 26. Please request a new password by clicking //Forgot password// at the login prompt.
6 +Note that this is not the same as accepting an exception in your browser because of a bad certificate. Accepting such exceptions can put your data and credentials at risk of a person-in-the-middle attack.
6 6  
7 -Users logging in to Collaboratory 2 starting May 27 will be asked to reset their password.
8 +We believe we have addressed all the issues that may arise from this change in SSL certificates. If you experience any issue, especially when accessing EBRAINS APIs, don't hesitate to contact [[support>>https://ebrains.eu/support]].
8 8  
9 -Select a password that you do not use on other accounts and that cannot be easily guessed by someone knowing your other passwords.
10 10  
11 -Select a password sufficiently long and complex with a mix of lower case, upper case, digits and punctuation.
11 +== Files locked in the Drive (2020-09-30) ==
12 12  
13 -Remember that you are responsible for protecting your password. Do not write your password in clear form.
13 +A few users have reported issues in saving OnlyOffice edits to the Drive of a collab.
14 14  
15 -Thank you for your cooperation.
15 +We are looking into this. At the time being, it seems that a small number of files are locked by the Drive which prevents OnlyOffice to update these files when they are edited online.
16 16  
17 -The Collaboratory team, updated May 26 2020
17 +We are actively trying to correct the problem as promptly as possible.
18 18  
19 -
19 +==== The temporary workaround ====
20 +
21 +When you open a file in OnlyOffice:
22 +
23 +1. check if other users are editing the same file. The count appears at the top right corner.
24 +1. perform a trivial edit and save
25 +1. if you are the only user with that file open, you can trust the presence/absence of a warning message from OnlyOffice
26 +1. if multiple users have the file open simultaneously, you can:
27 +11. choose to trust the first user who opened it to have checked, or
28 +11. check in the Drive the timestamp of the file that you just saved
29 +
30 +OnlyOffice will notify you when you try to save a file and the save fails. If that happens:
31 +
32 +1. read the message
33 +1. use File > Download as ... > docx or pptx or xlsx to save the file to your computer
34 +1. close OnlyOffice. (% style="color:#e74c3c" %)**DO NOT KEEP LOCKED FILES OPEN IN ONLYOFFICE.**(%%) It would mislead others.
35 +1. rename the file by adding (% style="color:#3498db" %)//**_UNLOCKED**//(%%) at the end of the filename, before the extension
36 +1. upload the file with its new name
37 +1. work on this new file
38 +
39 +We apologize for the inconvenience and thank you for your understanding.
40 +
41 +The Collaboratory team