Mac and Windows - cloud or local
The Security Update
We are pleased to introduce version 7.4, which brings you major improvements and new features. Thanks to its original architecture, Office Maker is the first Swiss management software native to Windows and Mac.
Certified for macOS Sequoia
and Windows 24H2
Versions 7.4 are optimized for the latest processors and operating systems. Their native operation in a dedicated client application rather than a web browser offers unique advantages in terms of performance, ease of use and security.
The security of your data is our top priority, and version 7.4 make it even more so. It's also worth remembering that Office Maker is a 100% Swiss-independent solution, and that our cloud servers and backups are also hosted in Switzerland.
QUIC Network Protocol
This network protocol, developed by Google some ten years ago, is now used by major names such as Microsoft and Meta, and Office Maker is the first major Swiss ERP to use it.
​
It provides more stable connections, enhanced security thanks to its encryption against man-in-the-middle attacks, and improved performance, especially for slow Internet connections.
Security improvements
Administrators can now force users to define more secure passwords by setting a minimum length (between 6 and 60 characters in Unicode, including any special symbols), the presence of numbers and letters, and upper and lower case letters.​
​
We recommend personal, impossible-to-guess “passphrases” of at least 15 characters, which are easier to remember than a shorter, complex password, and just as secure. Passwords or passphrases are stored on the server in encrypted, one-way form (hashing), and cannot be known to anyone (including us) except the user who set it.
​
In both client-server and cloud modes, the login dialog has been strengthened against any hacking attempt or brute-force penetration.
The login dialog for cloud versions has been extended to local servers and single-user versions. As a result, it no longer displays user account names, which could have facilitated intrusion attempts. The user name can, however, be stored locally on the workstation.
User authorization management can now prevent an account from accessing the Action>Apply command, which - if misused - can cause damage to the database.​
​
The method for verifying an account's access authorizations to certain records has been optimized to speed things up considerably when there are a large number of records.
The encryption key (2048 bits in TLS 1.3) for communications between client workstations and the server is now unique to each company and program, and is replaced each time the server application is started.
With versions 7.4, we continue to improve our software, always at the cutting edge of user-friendliness and technology.