After Upgrading to Macos Montery 12.6 HCL Notes crashes during startup. This issue has already been recognized by HCL. An upcoming fix will solve this issue.
Up to now you should NOT update your macOs devices to Monterey 12.6 if you are a HCL Notes customer. Wait until the fix has been releaed.
Read the KB-Article!
Very good news yesterday from big blue.
IBM announced yesterday their strategic partnership with HCL Technologies to develop the future of Domino, Verse, Notes and Sametime. This partnership will lead into a Version 10 of Notes and Domino next year and a roadmap for the future.
Read the announcent of IBM
IBM invites all customers, users and business partners to join the
to create a roadmap for future development around the platforms. If you want to join just click here
This article is the last one discovering the migration of Let's encrypt certificates to a domino environment. The previous artile was about Create Certificates with Let's Encrypt.
Now we can pickup the certificate. It will be stored on the filesystem of your server where you issued the certbot-auto command. The application tells you were you can pickup the certificate. In our case the cerficates are located at
/etc/letsencrypte/archive/<nameOfTheServer>
Switch to that directory and copy all four files to a single file. You can either use an editor to to this or just cat them into the file.
cat firstfile.pem >> all.pem
...
cat fourthfile.pem >> all.pem
Now copy the file "all.pem" to an appropriate Notes client or Domino server. Download the kyrtool from IBM and extract the file into the programm directory. Now you can create a new kyr-file by initiating
c:\Notes\kyrtool.exe create -k c:\cert\ourKeyring.kyr -p appropriateSecuredPassword
This will create a ourKeyring.kyr and ourKeyring.sth file in c:\cert directory. Now we can import the all.pem file into that keyring.
c:\Notes\kyrtool.exe import all -k c:\cert\ourKeyring.kyr -i c:\cert\all.pem
Now, we are done. Just copy the two files ourKeyring.kyr and ourKeyring.sth file to your domino data directory. Ensure the filename is the same as you entered it in your domino directory and that filepermissions are set correctly (notes:notes or what your runtime user is).
That's it. After a restart of Domino's http-task your new certificate is active.
Have fun
This article is the sequel to Let's Encrypt in Domino Environments
To create a certificate is very easy: Instruct the certbot-auto application to create the certificate:
./certbot-auto certonly -d <yourFQDN> --manual
This command (you need internet access) will contact Let's encrypt. It will ask you to create a cryptic file on your server with a much more cryptic content. With this file and it's content Let's encrypt can check whether you have appropriate rights to receive a certificate. They will access the file and compare the content with the content they generated. If both is identical, you will receive the ceriticate immediately.
First, create the necessary subdirectories on you Domino server.
mkdir <notesdata>/domino/html/.well-known/acme-challenge
Then create a file with the filename highlighted in certbot-auto on your filesytem and add the content form certbot-auto to the file
touch <notesdata>/domino/html/.well-known/acme-challenge/<certbotAutoFileName>
cat <certbotAutoContent> <notesdata>/domino/html/.well-known/acme-challenge/<certbotAutoFileName>
On Linux, AIX etc ensure that filepermissions are set correctly.
chown -R notes:notes <notesdata>/domino
This command will correct the permissions. Now you can switch to your server certbot-auto ist running on. When you agree to the test of your environment this will immediatly create the certificate. It is very useful to keep this filestructure and file on your server for later automatic renew of the certificate.
In the last article we will explain how to migrate those certificates to your domino server.
From time to time we have to implement or update a certificate on our Domino and/or Traveler servers. Let's encrypt enables us to get those certificates for free without any charge (Expiration time: 90 days). The first step is to receive those certificates. Depending on your operation system you have to install one of the several clients. We use the certbot-auto client.
The way to install that client is well documented and there is no need to be explained here. After that you need to create your certificate. Here are the steps on how to create and convert them into a domino environment.
In the next article we will explain how to create Let's Encrypt certificates. And in the last article we will explain how to migrate them to domino.