Following suggestions from the Center for Digital Humanities at UCLA (and generally Google Inc.), CDLI has migrated from the common HTTP protocol to an encrypted HTTPS connection. This means that any information exchanged between a visitor's web browser and CDLI servers through our website is virtually impossible to track from outside this connection. For instance, an internet service provider or a hacker cannot know what information you entered in any of the CDLI forms. Note that because the CDLI search exposes your search parameters in the URL (web address) so you can share the results with colleagues, the information you enter in the search fields is thus exposed by CDLI as a feature of our search policy. URLs of pages visited are not, and cannot be hidden. Forms concerning more sensitive information than the search form, such as editors accounts login forms on the CDLI front page and on the search/transliteration module, are thus safer. The same applies in the case of an editor using forms in the administrative sections of CDLI, for instance when they change their profile information.
As best practice, it is now recommended to encrypt all websites, especially those that have input forms in which users actively interact in some way with the served content. In an age of ever more intrusive surveillance, every bit of information a user exposes in the web can be captured and exploited to create a profile, that can then be used with intentions that may be benevolent (to sell you more of the same kind of soap), or malicious (to track your passwords and enter your bank account). Although the use of CDLI with its open access policies is not likely to attract the interest of particularly offensive actors, we feel it is important for us to establish good web security practice now to protect the privacy of our users going forward. We are committed to sharing information about cuneiform artifacts freely and in the safest way possible for all users, and encrypting the CDLI website fosters unencumbered access while ensuring a good level of user privacy.
The implementation of HTTPS encryption in CDLI pages is now underway. The Center for Digital Humanities at UCLA provided us with a signed encryption certificate for the cdli.ucla.edu subdomain that we installed on our web server. Employing this certificate, we enable secure connections on the server, and redirect incoming traffic from HTTP links to HTTPS. In the next few weeks, we will work on making all of our website fully secure. At the moment, some pages have hybrid content, that is, encrypted data mixed with external information from third parties. These third party data are generally style sheets or java scripts that aid in displaying the CDLI data requested by users. In addition to browsers' behavior with mixed contents, we have had problems with certain versions of the FireFox browser on Apple OS and Windows. In those instances, the website was completely innaccessible and the browser would display a warning indicating the website was not secure. Adding an intermediary certificate resolved the problem, as described in this FireFox help page. Should you receive security warnings from your browser while requesting or viewing CDLI content, please assist us by posting the details of your ‘encounters’ to firstname.lastname@example.org. At the end of this transition process, and in all future iterations of the website, CDLI pages will be fully secured.