Monday, December 17, 2018

Notes/Domino security vulnerability patched by IBM. You should apply this fix soon.

IBM has discovered and (on Friday, December 14, 2018) released a patch for a security vulnerability in NSD (Notes System Diagnostics) for Windows. So now is a really good time to upgrade your Windows-based Domino servers to 9.0.1FP10IF5 and your Windows-based Notes clients to version 9.0.1FP10IF6. (Or you could upgrade them to version 10.) Here's the Technote with the details. 

Friday, October 12, 2018

Beware of stray cables

I just watched this scary video demonstration by Kevin Mitnick of KnowBe4 of a lightning cable that infects any computer you plug it into (well, the demo used a Windows 10 computer) with malware. In the demo Kevin suggests that we stop leaving cables plugged into our work computers, implying that the demo lightning cable could be swapped in when our back is turned. And don't use any old cable that you might find lying around? "You need to stop, look, and think", he says, "before you plug any device into your computer."

But Kevin leaves a lot of other questions unanswered:
  • How can we determine if a cable is malicious?
  • How can we tell if a cable we buy in a store is malicious or not? 
    • Do we have to stop buying non-Apple branded lightning cables now?
    • Are Apple branded cables save, even?
  • Can we use anti-malware software to protect ourselves if such a cable is plugged into our machine?
Hey, reader, sleep well tonight!

Tuesday, February 20, 2018

IBM Notes 9.0.1, MacOS High Sierra, and Java 8. Part 2.

After I wrote my Jan 24 post about running Notes on MacOS in Basic Mode, IBM released Notes 9.0.1 for MacOS Interim Fix 13. IF13 provides a fix for the problem I described in that post, which was that upgrading Java on the Mac to a version higher (more recent) than Java 8 Update 151 caused Notes to fail to start. That surprised me because, on the Windows platform Notes provides its own JVM; you can install whatever Oracle JVMs you like under Windows without affecting Notes at all. But it turns out that Notes running on the MacOS platform does not come with its own JVM and does rely on the Oracle JVM that you install on the machine. And, of course, Java 8 Update 152 caused Notes to choke and die.

In any case, the workaround at that time was to run Notes in Basic Mode, which effectively reverts Notes to running the old Release 7 Notes client written in C++, naked of the Expeditor wrapper that provides the new features of  Notes that debuted in Release 8. In Basic Mode, Notes does not use any Java-based features.

Another odd thing that I discovered since writing my last post is that the Notes 9.0.1 installer for the MacOS platform is "broken" with respect to MacOS High Sierra. The first time you run it on a machine running MacOS, it fails in the Provisioning stage, with the following error message:
File /Applications/IBM Notes.app/Contents/MacOS/rcp/rcplauncher.properties not found. Provisioning process failed to launch or was terminated before status could be determined.
Then the installation fails.

The fix for this is, of all things, to rerun the installer. The second time around it succeeds all the way through. Go figure.

Wednesday, January 24, 2018

How to run IBM Notes in Basic Mode on MacOS

Late last week a RockTeam client notified me that a user upgraded Java on his Macintosh to Java 9.0.1, then discovered that IBM Notes would no longer start on the machine. The client is a software publisher and the user is a developer. He figured out how to run Notes in Basic Mode (i.e., without the Eclipse wrapper that provides additional, Java-based functionality to the Notes client, which is known as "Standard Mode") and concluded that his upgrade of Java must have caused the problem.

My client asked me to help figure out what the problem was and how to get Notes running again in Standard Mode. With IBM's help (I opened a PMR) I soon discovered two things:
  • This IBM document states that 64-bit Notes running on MacOS does not support Basic Mode.
  • This IBM document states that 64-bit Notes will not run on MacOS if you upgrade Java to version 8 Update 152 (or later).
The first document above turns out to be inaccurate; Notes will in fact run in Basic Mode on the Mac. The second document is accurate; Notes will not currently run in Standard Mode if you install Java 8 Update 152 or later on your Mac. So the user has two options: Downgrade or remove Java; or settle for running Notes in Basic Mode. Running in Basic Mode, one loses the Open button, the full-text search field in the upper right corner of the Notes window, and the right sidebar and all the Java-based apps that it contains.  The subject user has decided for now to live with Basic Mode. The company isn't a big user of the "Social Edition" features of Notes, so Basic Mode probably meets all of this user's current needs.

What interested me about this was that, from the way he described the problem, it was obvious that our user was not a Notes guru, knowledgeable about Notes's different running modes. He is a developer, though, and knowledgeable about Java and Eclipse. So he was able to just figure out how to get Notes to run without Eclipse. I thought that was pretty ingenious of him and asked how he managed to do it. So far the only answer I've received from him is "by brute force".

But I did some testing myself and learned that you can indeed start Notes in Basic Mode on the Mac. Here are the two ways I found:
  • Set the variable UseBasicNotes=1 in Notes Preferences. Notes Preferences is the Mac equivalent of notes.ini, where one would set this variable on the other supported Notes platforms. When you set this variable, Notes always starts in Basic Mode, i.e., without trying to wrap itself in Eclipse. If you want to run Notes in Standard Mode, you have to remove this variable or reset its value to "0".
  • Issue this command in Terminal:
    "/Applications/IBM Notes.app/Contents/MacOS/notes" -basic
    • NOTE: The quotes are necessary because of the space between "IBM" and "Notes.app". 
    • Notice also (my fellow geek) that I appended "-basic" to the command. Under Windows you could append either "-sa" or "-basic", but "-sa" did not work for me under MacOS.
I know there's a way to create a script to run the above command with a mouse click (or two). I'm not a UNIX guru, so I don't know how by heart. When I find some time, I'll figure it out and post that information here.

Friday, December 15, 2017

How to locate a document with a bad NLO reference (or What to do when fixup -d -j fails)

A user has a local mail database. Every time it replicates with the mail server, replication takes 5-8 minutes as it tries repeatedly to replicate the same 1500+ documents. Running fixup, compact, updall against the mail database on the server revealed this error message:
The database <pathname>.nsf attempted to access a missing file: H:\DAOS\0007\E5128368DF400D54DE01F369AFAAF560FCB85F350007FAC9.nlo: File does not exist
It seems that the replication process was getting hung up because of a document contained an invalid NLO reference.
The quick and dirty way to deal with a problem like this is to issue the following fixup command, which deletes documents that contain invalid NLO references:
load fixup -d -j <pathname>.nsf
This command did not, however, resolve the problem for us because (I discovered later) the problem document included two attachments, both pointing to NLO objects. But the second pointer was valid, so fixup decided not to delete the document.
The solution to this problem was to locate the document that had the bad NLO reference. Here is the way to do that:
  1. Set the following notes.ini variable on the mail server (no server restart needed): Debug_DAOS_Diagnostics=1
  2. Run the following command at a console prompt: Tell DAOSMgr listnlo MAP -V <pathname>.nsf
    • This causes the creation in the mail server's Data folder of a text file, listnlo.txt, that contains a list of all NLO references in <pathname>.nsf.
  3. Make a local copy of listnlo.txt. It is a comma-delimited file. Open it in a spreadsheet program or a text editor.
  4. Search for the NLO's hash key, which is the file name of the NLO file.
    • In my case, I searched for "E5128368DF400D54DE01F369AFAAF560FCB85F350007FAC9".
  5. The Note ID (hex format) of the document appears in the second column of the row that contains the search term.
  6. In Domino Administrator under the Files tab, select the database in question and use Find Note (Tools pane, Database section) to find the problem document by its Note ID. Alternatively you can use a third-party tool, such at Ytria's ScanEZ.
  7. Open the subject database on the mail server and use the information provided by the Find Note dialog (document date, subject, etc.) to locate the problem document in the database.
  8. Decide what to do about the problem document. Possible fixes include:
    • Delete the problem document.
    • Delete the problem attachment from the document.
    • Restore the problem attachment from backup.
  9. Optional but recommended: Reset  the notes.ini variable, Debug_DAOS_Diagnostics, to 0 or NULL.
    • se co Debug_DAOS_Diagnostics=0; OR
    • se co Debug_DAOS_Diagnostics=
Thanks to the following bloggers for this fix: Cristian D'Aloisio, Ralf Petter, Ulrich Krause

Copyright 2017 by Rob Kirkland

Friday, September 1, 2017

Here are four good reasons to upgrade your IBM Notes mail clients to the latest Fix/Feature Pack

Reason #1: It fixes a Denial of Service vulnerability.

Reason #2: It fixes another Denial of Service vulnerability.

Reason #3: It fixes an Open Source zlib vulnerability.

Reason #4: It fixes an Open Source libpng vulnerability.

If your users are running Notes 9.x for Windows, you want to upgrade them to Notes 9.0.1 FP9.

If your users are running 64-bit Notes 9.x for Mac, you want to upgrade them to Notes 901 64-bit Mac IF11.

If your users are running Notes 8.5.3 for Windows, you want to upgrade them to Notes 8.5.3 FP6 IF15. Then start preparing to upgrade your Domino servers and Notes clients to 9.0.1, because Domino/Notes 8.5.3 will be going out of support soon. You can upgrade your users to Notes 9.0.1 before you upgrade your servers to Domino 9.0.1.

If your users are running earlier than Notes 8.5.3, you want to upgrade them because you are running an unsupported version of Notes/Domino. Plus, the four vulnerabilities listed above are just the four most recently fixed vulnerabilities. Your old, unsupported copies of Notes harbor others too.

If your mail databases are hosted in IBM Connections Cloud or if you have implemented IBM Verse on-premises, you could migrate your users from IBM Notes to IBM Verse. But if you are running IBM Verse on-premises, I recommend that you upgrade your Domino mail servers to Domino 9.0.1 FP9. (I'll tell you why in my next post.)

And remember that, if you are hosting your Notes mail on on-premises Domino servers, your Notes/Domino licensing probably includes IBM SmartCloud Notes licensing. That means you can migrate your users' mail databases to IBM Connections Cloud-based Domino mail servers at no additional cost beyond your current licensing costs. If you are not sure what your Notes/Domino rights and restrictions are, ask me; I can help you to sort that out.

Also, if you don't think you can migrate away from Notes to Verse because you are still running Notes-only Domino applications, that's okay, because Notes is a great product. But if you would like to upgrade your apps, ask me about your options for browser-enabling your Notes applications. There are lots of options available.

Finally, if you are thinking about migrating from Notes/Domino to Exchange/Outlook or Office 365 or Google Apps or SoHo or whatever, ask me why you should reconsider. IBM Connections Cloud is superior to those other platforms -- runs circles around them, in fact -- in any number of ways. And it is getting better at an accelerating pace.

Addendum: I can help you automate (or at least streamline) your users' Notes upgrade process, so you don't have to babysit each upgrade.


Friday, August 25, 2017

IBM Notes 9.0.1 Feature Pack 9 is available and here is my favorite enhancement

IBM Notes 9.0.1 Feature Pack 9 includes this:
High resolution support for the Notes® ClientThe Notes® client on Windows correctly scales text and icons when high resolution monitors or custom DPI settings are used. 
 This might seem like a minor fix, but for me it is great news. If you have shopped for Windows computers lately you may have noticed that many of the laptops now sport fantastically high screen resolutions. I recently bought (then regrettably returned) an HP Spectre laptop (aircraft carrier, really - it was BIG) with a 4000x3000 pixel display. Then I bought (and kept) a Microsoft Surface that has a 3000x2000 pixel screen. The problem I had with both of them was that IBM Notes, which is my bread-and-butter software, couldn't cope with such high resolution screens. Either the text would be so small that I needed a magnifying glass to read it or, if I tried to use Windows or Notes text resizing tools to enlarge the text, it would enlarge in unsatisfactory ways. For example, the text would be large enough to read, but the line height would not change, resulting in the tops of the letters being hidden and the whole exercise of reading the text very unsatisfactory.

I had found two workarounds for the situation. At first I simply reduced the screen resolution of my new laptop to an old-fashioned 2048x1024 (or less) so that I could read the content in my Notes windows. That worked fine. But it irritated me to have spent all that money and to be unable to use one of the nicest features of my new laptop. 

Later I noticed that, if I started my computer in high resolution mode with no external monitor attached, the text and icons in my Notes window would be properly sized and would look okay. But then if I attached an external monitor (my highest resolution one being 2048x1024) and moved the Notes window onto it, it would not resize properly. But then if I rebooted with the external monitor still attached, the Notes window, when reopened on that monitor, would display properly sized text and icons. But then if I moved the Notes window back onto the native monitor, the text in it would again be improperly sized. Or if I simply unplugged the external monitor, forcing the windows on it to move onto the native monitor, same result. But rebooting would again fix the text sizing issue.

In other words, my second workaround was to reboot the laptop (or, as I later discovered would also work, to simply log out of Windows, then log back in) whenever I wanted to connect to and use my external monitor or to disconnect from it. Doing so would fix the text in the Notes window. But it was a hassle to have to shut down and reopen the various programs I typically run every time I needed to connect my laptop to or disconnect it from my external monitor. All in all, a pretty unsatisfactory situation.

All that is fixed now with the happy release of Notes 9.0.1 Feature Pack 9. Now, if I unplug my external monitor, Notes repositions itself to the native monitor and resizes its text and icons exactly as it should. And if I plug the external monitor back in, Notes reverses the process exactly as it should - everything properly formatted and sized, all text easily readable. I am a very happy camper.