199 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
Blog Certificate updated and Let’s Encrypt Update
Tue, Aug 8th 2017 19
SLES 12 SP2 Issues with Domino running with Systemd
Mon, Jul 24th 2017 6
Microsoft fixes Notes Client Windows 10 Creators Crash
Wed, Jun 28th 2017 4
Traveler 9.0.1.18 with new Security Mode for Mail-File Access
Thu, Jun 22nd 2017 7
Notes Client/Windows Crash with Windows 10 Creators update
Thu, Jun 1st 2017 14
Security Bulletin: IBM Domino TLS server Diffie-Hellman key validation vulnerability (CVE-2016-6087)
Thu, Jun 1st 2017 4
Important Security Fix for IMAP
Sat, Apr 22nd 2017 2
Top 10
Details about JVM 1.8 Update in Notes/Domino 9.0.1 FP8
Sun, Feb 5th 2017 26
Blog Certificate updated and Let’s Encrypt Update
Tue, Aug 8th 2017 19
IBM Notes V9.0.1 Mac 64 Bit English (CN6VDEN )
Tue, Sep 29th 2015 18
TLS 1.2 Connection Issues with mail.protection.outlook.COM
Thu, Jan 7th 2016 15
Notes Client/Windows Crash with Windows 10 Creators update
Thu, Jun 1st 2017 14
DAOS NLO Encryption and Decryption
Wed, May 28th 2014 9
IBM Notes/Domino 9.0.1 Feature Pack 8 Preliminary Release Notice
Fri, Jan 27th 2017 9
Passing a document to an agent without saving it first
Sun, Apr 6th 2014 8
Symantec Backup Exec End of Life
Sat, Dec 5th 2015 8
Notes and Domino 9.0.1 Feature Pack 8 shipped
Tue, Mar 7th 2017 8


Traveler 9.0.1.15 available with some important changes
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
Daniel Nashed    

Traveler 9.0.1.15 has been released with some important fixes and also changes. The Release documentation has some interesting details.

Here is the extract from the release documentation with some comments.

What's New


"Device wipe is no longer an option for iOS 10.x devices as support was dropped by Apple. You can still use the Wipe Traveler Data option."

For security reasons Apple disabled wipe over ActiveSync which is understandable. Before that change every server could wipe any device connected via ActiveSync.
With this Apple side change Traveler could not delete the device any more and the status from the device was not interpreted correctly by the server.
Traveler does now check if the device still supports the wipe (running iOS earlier than 10.x) and does only allow the Data Wipe over ActiveSync if the full wipe is not supported on the device.


"Yellow status message if the IBM Traveler server is not listed as a Trusted Server for an end user's mail server. This is required for future security and feature enhancements planned for 2017. The status message will include information about how to correct."

Sounds like IBM is planning a bigger change in 2017 for Traveler. I am curious what this higher security requirements are needed for. Trusted Servers are a quite high requirement which allow the Traveler servers to fully authenticate as any user on the mail server. It's much higher than just granting manager access to an individual mailfile.

I have removed the Trusted Servers entry on my mail-server but I did not yet see the warning.

"Database schema updates to improve data integrity.

Tablerepair tell command to support the above schema updates. A warning message will be displayed at startup if any of the schema updates were not applied with instructions to run the tablerepair command. The server will continue to function properly if no action taken.


NOTE: IBM Traveler 9.0.1.15 does include a database schema update. Action may be required if you manually manage your database schema (this is not common). If you use auto schema updates (default behavior) there is no action required. See Updating the Enterprise Database for more information (http://www.ibm.com/support/knowledgecenter/SSYRPW_9.0.1/UpdatingTheEnterpriseDatabase.dita)"


So this is an important information. This new version requires a schema change. If you are running stand-alone that should not cause any issues.
If you have automatic schema update enabled the schema update should also happen automatically.
And if you are switching from manual schema update to automatic schema update you should be careful. There is one ARPA fixed for DB2 and you should be aware of the default schema name differences for manual and automatic schema configuration.

I guess with this schema change the issue has been discovered and the fix is that the NTS parameter with the schema name will be automatically set.
(See -> http://www.ibm.com/support/docview.wss?uid=swg1LO90497 for details).


The fix-list contains some other important fixes! Check the fixlist link below for details.

My server is already updated but I had not much time to test.


IBM Traveler Fixes 9.0.1.15

http://www.ibm.com/support/docview.wss?uid=swg21700212#90115

IBM Traveler 9.0.1.15 Server Release Documentation

http://www.ibm.com/support/docview.wss?uid=swg21994070


---------------------
http://blog.nashcom.de/nashcomblog.nsf/dx/traveler-9.0.1.15-available-with-some-important-fixes.htm
Nov 15, 2016
5 hits



Recent Blog Posts
19
Blog Certificate updated and Let’s Encrypt Update
Tue, Aug 8th 2017 9:30a   Daniel Nashed
My certificate expired after 90 days because I did not track it. And the Let's Encrypt original client configuration did not work any more when I was looking into renewal today. The client was Python based and there is a newer client --> https://certbot.eff.org/ which is officially recommended by Let's Encrypt. It's still complicated to use and you need to have Python installed. But since I first implemented it there are many other ACME clients that properly integrate with Let's Encr
6
SLES 12 SP2 Issues with Domino running with Systemd
Mon, Jul 24th 2017 10:01a   Daniel Nashed
There is a new feature introduced in SLES 12 SP2 which could lead to issues with larger Domino or Traveler servers. The default nproc size is still set to 7400. So in most cases this tunable does still not need to be set in your Domino service file. But there is a new security feature introduced in SLES 12 SP2 which will cause processes fail to start or not able to span more threads. The error you might see is the following: Jul 20 11:02:41 dom-srv kernel: cgroup: fork rejected by pi
4
Microsoft fixes Notes Client Windows 10 Creators Crash
Wed, Jun 28th 2017 8:16p   Daniel Nashed
Today I got feedback from IBM that the fix that Microsoft releases does solve the blue screen issue with Notes and the customized home page issue. There have been multiple situations in which the client crashed or caused a blue screen because of some Windows UI calls in Notes after the Windows creators update. I am interested to get feedback if the fix does solve all your Notes Client on Windows creators update. Here is a link for the update: https://support.microsoft.com/en-in/help/
7
Traveler 9.0.1.18 with new Security Mode for Mail-File Access
Thu, Jun 22nd 2017 9:07a   Daniel Nashed
Traveler 9.0.1.18 comes with a couple of minor fixes and a big change in the way Traveler Server access mail-databases. In 9.0.1.15 IBM introduced a new check if the Traveler server is listed in Trusted Servers (Server Security Tab) to show a warning if not. Now we know what IBM was preparing for. The server now acts as the user instead of the server. That's only possible if listed in Trusted Servers. You still need the Traveler server to be listed in the ACL of the mail databases. Trus
14
Notes Client/Windows Crash with Windows 10 Creators update
Thu, Jun 1st 2017 12:00p   Daniel Nashed
Just got that question today at DNUG. There is an issue with the Notes Client with the current Windows 10 Update - aka Creators Update (Build 1703). According to the responsible person who is at DNUG today, this happens because of changed Windows graphics APIs. IBM is working on a fix which will be available in FP9. FP9 will also have full High Resolution support! We saw a demo with FP9 which really looked great! Here are the two relevant SPRs: SPR LHEYALMCEP : Domino Designer cra
4
Security Bulletin: IBM Domino TLS server Diffie-Hellman key validation vulnerability (CVE-2016-6087)
Thu, Jun 1st 2017 6:27a   Daniel Nashed
There is a vulnerability in the TLS stack which could lead an exploit which could lead a less secure connection. The good news is that the fix is already included in FP8. So you should upgrade to 9.0.1 FP8 if you have a public facing Domino Server with HTTPS. See the details and reference below. -- Daniel A vulnerability in the IBM Domino TLS server's Diffie-Hellman parameter validation could potentially be exploited in a small subgroup attack which could result in a less secure conne
2
Important Security Fix for IMAP
Sat, Apr 22nd 2017 9:13a   Daniel Nashed
In case you are running IMAP on a server that is reachable over the internet you should look into this fix ASAP. It might not be that critical for internal services. See details about this vulnerability here --> http://www.ibm.com/support/docview.wss?uid=swg22002280 All versions of Domino are affected!
4
NIFNSF Supported Maximum Size above 64 GB!
Fri, Apr 21st 2017 9:02p   Daniel Nashed
After getting that question offline and having a discussion on my blog, I checked with IBM if they plan support NIFNSF sizes above 64 GB. Since it is kind of a database container and needs a database handle someone could think that the maximum limit is also 64 GB. That would give us at least 64 GB room for the NIF index -- which would be already a big improvement. But from what I recall from some comments at Connect some years ago the maximum limit was not around 64 GB when they designed it
6
Disclaimer Attachment Issue not yet fixed in IF1
Fri, Apr 14th 2017 6:28p   Daniel Nashed
As Rob Kirkland commented in one of my last blog posted, the fix in IF1 does not solve the iusse. We both checked with IBM and got the reply that the SPR just changes back the default and disables the change introduced in FP8 for Google calender integration. IBM is working on a fix hopefully makes it into FP9. So for now you should keep the notes.ini Parameter MIMEDisclaimersNoEncode=0 disabled. Thanks to Rob to bring this up! -- Daniel TPONAKFJLP After upgrade to FP8, with
0
Get Notes FP Version in @Formulas
Wed, Apr 12th 2017 6:19a   Daniel Nashed
In C-API and Lotus Script, Java developers the version information already shown for each FP. For example Lotus Script returns the full version string with session.NotesVersion. But if you want to check the version information in @Formulas @Version will still return 405. There is a new optional parameter which returns the Feature Pack version. So you use @Version to check the version and if it is 405 you check @Version(1) which will return 8 for Feature Pack 8. It is used in the new ma




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition