20 Years 141Perfection in Software Protection141Uni147 ed pro - PDF document

1 20 Years Perfection in Software Pr
20 Years Perfection in Software ProtectionUni“ ed protection with CodeMeter and CodeMeterActModular software protection with WUPI for .NETFile encryption with AxProtector 17 2 INTRO Realizing Software Protection Uni“ ed protection with CodeMeter and CodeMeterAct Automatic protection for .NET Assemblies Modular software protection with WUPI for .NET KNOW-HOWThe use of the CodeMeter Core API 10SERVICECodeMeter … token and dongle together CASE STUDYFile encryption with AxProtector BILLBOARD20 Years WIBU-SYSTEMS CUSTOMER STORYCustomer story Cosynus ROADSHOWRoadshow 2009 Dear customers and partners,For 20 years now WIBU-SYSTEMS has embodied Perfection in Software Protection. Beginning with WIBU-SYSTEMS GdbR, founded in 1989, by Marcellus Buchheit and Oliver Winzenried, WIBU-SYSTEMS has evolved and has become a medium-sized enterprise with subsidiaries in the US and China, sales of“ ces in Europe, with many distributors worldwide, and with 50 employees alone at our headquarters in Karlsruhe. Just as in the past, WIBU-SYSTEMS still stands for innovation. The enthusiasm for top security and func-tionality while creating additional bene“ ts is what motivates us. We integrate innovation and continuity. We think in long terms, but with attention to stability. This means that we are not slaves to the quarterly “ nancial statement, but can hold on to objectives and visions, and continue what we are: a closely-held enterprise, economically independent and able to endure the winds of fortune that force others into merger or out of business.Many developers, who began using our solutions from the very start, are still among our top customers. They appreciate that our WibuBox from 1989 is still avail-able today, has been further developed, and works with our latest tools, (not to mention that it also works with our latest CodeMeter solutions). Try to name just For some, we know these are economically dif“ cult times. As your partner, we want to support you even more by reducing revenue lost to pirated copies, and to help you acquire new customers by adopting innova-tive licensing models. For the best, a crisis has always been seen as an op

2 portunity. We want to contribute our par
portunity. We want to contribute our part so that we jointly belong to the best. This latest issue of our KEYnote magazine will provide suggestions on how you can solve your tasks. Now the next step is up to you: ask us your questions, attend one of our road-shows in your area, visit with us during CeBIT, or simply give us a call.With best regards from Karlsruhe, When planning the protection of a software project, the task is always the same. The software needs to be protected as securely as possible... but with little effort. However, solutions are not always the same because sometimes the requirements differ. Realizing software protection vides easy-to-use API functions, allowing for by most developers. The range of this universal API, which can be integrated into simple as well as exotic programming languages, is broad within modular protection schemes. pay-per-use applications, and the ability to query various information are some examples. The functionality behind, what appears at “ rst glance to be simple WUPI functions, is subject to continuous security-related improvements. Thus, a one-time built-in call for a license check a year from “ rst compilation will perform the created today. As with AxProtector, in IxProtec-tor and WUPI you do not have to worry about these improvements of security mechanisms, this we do for you. With each new AxProtector your software.Core APIFurther requirements are met by the Core API. This API available as C-API, .NET API or Java API works with most programming languages and allows for the realization of all other requests: within your application, using altering parame-ters, reading of further data from the hardware, Easy transitions characterize all of the differ-ent protection options. With WUPI you use at runtime the same license entry the AxProtector uses. With a WUPI function (WupiGetHandle) further use in the Core API. These transitions protection layers.AxProtectorTake the case of a standard application or library. You can use AxProtector to envelope the entire project in an encryption layer. This results in a for a deep understanding of the applications architecture. With a minimum of effort you can integrate a great number of security mechan-isms and checks

3 into your product, and easily put your p
into your product, and easily put your protected software on the shelves in a very short time. And AxProtector is a proven technology; hackers by the droves have unsuc-improved and extended protection... without success.IxProtectorAdditionally, when you want to protect separate areas within an application or library, you can use IxProtector. It provides for the encryption of functions, which at runtime, are decrypted shortly before they are executed. Here separate CodeMeter, CodeMeterAct and/or WibuKey licenses. This prevents unlicensed use for non-activated modules utilizing encryption instead of simple con“ guration.IxProtector at runtime, you use the Wibu Uni-versal Protection Interface (WUPI). Along with encryption, the Software Protection API pro- Mr. Thomas HogefeldGastroLohn Datenservices, BocholtWe have been using WibuKey since 1992 to protect our complete product range … payroll accounting, staff planning, table booking, cash accounting and billing. Beginning “ rst with Windows 3.1 and continuing up to the current Vista version, we received secure and reliable protection by WIBU-SYSTEMS. Even better, we also experienced competent and fast support. WIBU writes continuity with a capital C. We always get a continuously improved and downward compatible product. For many years we have the same contact partner at WIBU. We congratulate WIBU-SYSTEMS on 20 years of continuity. Keep it up. 4 Uni“ ed protection with CodeMeter (hardware-based software protection) and CodeMeterAct (activation-base software protection) are identical. For you as the software vendor (licensor) it is easy to protect your software in a way that it simulta-neously runs with CodeMeter and CodeMeterAct. This means, that you have one version of your software, and decide for each customer (licensee) whether he receives a dongle or an activation. The following basics show you how it works, and how easy it is to realize software protection.The security of CodeMeter / CodeMeterAct is based on encryption. The software to be protected, modules or data in the software, are encrypted by the developer before shipping. The key for decryption is part of the license (dongle or license “ le) the developer generates for the end-use

4 r. On the users side, parts of the
r. On the users side, parts of the soft-ware are decrypted only when needed. After use, these parts can be re-encrypted.Uni“ ed License Manager models. The management of licenses at the cus-tomers is provided by a uni“ ed license manager (CodeMeter License Server). You simply access Figure: Security by encryption the interface of CodeMeter License Server, and the management of license “ les and dongles Code. Strictly speaking, a license may hold additional options, such as, license quantity or expiration date. The Firm Code represents a number WIBU-SYSTEMS assigns to you. Now Firm Code. You are free to select any Product Code or further options, and thus map different modules or different products. A license “ le or a dongle may simultaneously hold several Product Codes.The Firm Code with CodeMeterAct differs from the one used for CodeMeter. In case you use both protection systems, you receive two differ-ent Firm Codes. Due to the different Firm Codes whether to search for the license in an activated license “ le or in a dongle.Protection with AxProtectorcrypts your software after compiling … regardless of whether it is a Windows application or a .NET Assembly. In order to create software supported time, simply activate both options.Thats all there is to it, the rest is automatically done for you by AxProtector: the creation of arbitrary keys, the separate encryption of the keys, and the realization of additional security concepts.Protection with WUPIoffers you the option to implement software protection queries into your source code. As a C interface, WUPI is available for all classical programming languages. And as WUPI for .NETŽ, it is available for all .NET programming languages.With WUPI you simply integrate a placeholder (a number, e.g. 1) into your software, and then using the function WupiCheckLicense. After compiling, IxProtector replaces this placeholder with licenselistsŽ. When using CodeMeter and CodeMeterAct at the same time, you simply apply a licenselist with separate CodeMeter or CodeMeterAct license entries.By the way, IxProtector is integrated into AxPro-tector, and next to simple queries, allows you to individually encrypt code fragments,

5 and to control when these fragments are
and to control when these fragments are decrypted at runtime. We recommend using WUPI when you want to control the activation of different modules of your software separately, individually decrement counters, or to increase the security of AxProtector even more. In many cases, ap-plying AxProtector is suf“ cient.standard licensing system. Next to the Firm Code and the Product Code, a licence entry can also hold additional options. These are identical for Each license entry holds all of these options, and all options are combinable. This allows you to realize numerous license models, e.g., test license, single user license, leasing licenses, backup licenses, over” ow licenses, modular licenses.You protect your software once and de“ ne license options in the dongle or the activation “ le. All customers get the same software but individu-al licenses are controlled with CodeMeter. Figure: Uni“ ed license manager License optionDescriptionLicense QuantityNumber of simultaneously avail-. Use, e.g., concurrent network licenses. Optionally machine.Expiration TimeLicense is time-limited until the expiration date.yes, secure comparison Usage PeriodLicense is time-limited for a yes, secure synchroniza-Unit CounterCounter to realize pay-per-use functionalities.yes, secure stored in Cm-Stick, only decrementable.TextDescription of the license. The text he owns several licenses.Further option, for more details Table: License with CodeMeter and CodeMeterAct Mr. Heiko HelbigCEO, BECOM Software AG, WeimarŒWhen the winds of change blow, some people build shelters and others build windmills. (Chinese proverb). Keep up building windmills! Thank you for the excellent and personal cooperation for more than a decade. Mrs. Jasmine Herzog Ziehm Imaging GmbH, NurembergCongratulation to WIBU-SYSTEMS on staying in business for 20 years. After 10 years, we remain a satis“ ed WIBU customer. Keep up the good work! 6 Automatic protection for pirated copiesmodi“ cationmodi“ cation, your executable code should always be encrypted before delivery … with AxProtector.and is available for Windows 32 / 64bit, Mac OS X, NET and Java (applications and servlets).How does AxProtector for clas

6 ses, methods and “ elds are extract
ses, methods and “ elds are extracted from the original assembly.classes are created with the same names, methods and “ elds.the newly created methods, however, do makes calls to the AxEngine.At the “ rst call of the encrypted method, the code inserted by AxProtector for .NET calls the AxEngine (1). AxEngine decrypts the original A .NET Assembly is principally an open book: using appropriate tools (e.g. Reflector) your code can be easily Figure: Screenshot .NET Re” ector uncoded 7 Mr. Christian Deman CEO NeuroCheck GmbH, StuttgartNeuroCheck GmbH is a manufacturer of an interactive Windows software product for industrial image processing. Our software is used for fully automated visual product quality control in almost all manufacturing branches of industry, and has thousands of installations on systems worldwide. From the very “ rst sale of a NeuroCheck software license … shortly after the company was founded in 1994 … we copy-protected with a dongle from WIBU-SYSTEMS. Since then over 8,000 software installations together with WIBU products were delivered. Along the way, we also began to deliver the dongles with a customized corporate design casing. Important for us was, right from the start, the competent support in integrating the WIBU products. Since our systems are integrated in manufacturing processes, we attach great importance to a trouble-free operation of the products. Because we know that problems may eventually occur, we demand a quick and quali“ ed support for us and our end-customer.The WIBU support team has always provided us with high availability and very short response times. We wish WIBU-SYSTEMS 20 further successful years. code, stored in the data section (2), and calls Because the original methods keep their original names, you are still able to call them from the outside. Even the parameters (type and decryp-tion) stay the same! However, disassembly of the encrypted code is not possible (see “ gure). Features and advantages of AxProtector for .NETThe original code is hard encryptedŽ with AES.Decompiling and modi“ cation of the original code is not possible.necessary.To handle exceptions, e.g. a license is not found, AxProtector on reques

7 t is able to manage error messages.The c
t is able to manage error messages.The code is only decrypted on demand. That provides you top security.To increase performance the decrypted improved. This implements state-of-the-art protection mechanisms at your “ nger tip.PerformanceNaturally, the decryption of a method of an assembly protected with AxProtector for .NET requires some time. Measurement shows that approx. 3 ms.This is not much... however too much for some applications.Therefore AxProtector for .NET offers dif-White-listing: You simply de“ ne the methods to be encrypted. The remaining methods in the assembly are then not encrypted. Examples are assemblies holding a few methods with lots of know-how. Most of the other meth-ods do not require protection. Black-listing: You de“ ne which methods are excluded from encryption. All other methods are encrypted.Key-caching: The key for the decryption of the methods can be cached in the memory. This improves the performance.Explicit decryption and encryption: With WUPI (see next double page) you are able to decrypt executable code at any time, and then re-encrypt it (e.g. an application waits With WUPI you decide for yourself when com- Figure: With AxProtector protected Assembly Figure: Screenshot .NET Re” ector coded 8 Mr. Eberhard SchmidtJENOPTIK Laser, Optik, Systeme GmbH, JenaOver the past 12 years we have been using WibuKey to protect our solutions. The drivers worked trouble-free on all of our required platforms. And this always worked in spite of new Microsoft Windows versions or of improved dongles from WIBU-SYSTEMS. Regardless of innovation, the developer environment is still downward compatible. We never had to change things in our software to accomodate a new WibuKey. We use WibuKey to manage privileges. This allows us to control access to functions. In case a staff member is trained and access is enlarged, we simply reprogram the WibuBox. Congratu-lation on the 20th birthday. With our Software Protection API WUPI (Wibu Universal Protection Interface) we offer you a powerful tool to individually protect your software against pirated copies. Modular software protection with WUPI for .NET implementation of pay-per-use functional-ities (decrementing a counter on de“ ned de

8 47; nition when AxProtector executes ant
47; nition when AxProtector executes anti-debug measures.access to the licenses used by AxProtector.easy simultaneous use of WibuKey, Code-queries.WUPI is available for Windows applications and for .NET Assemblies. The basic principle in both versions is the same. While developing, you integrate a dummy DLL, the WupiEngine32.dll, WupiEngine64.dll, or the WupiEngineNet.dll cation to be protected with IxProtector. IxProtec-tor is an integrated part of AxProtector.it substitutes the dynamic library WupiEn-gine32.dll for a static library (this increases adds cryptographic queries into your software (each new version of AxProtector includes changes and improvements). Simply re-encrypt your software with AxProtector to improve protection. You do not have to recompile.For example, you may use WUPI in the following cases in addition to AxProtector:activation of single modules in one application. integration of license queries without cryptography.encryption of code fragments to increase encrypts code fragments.We recommend the simultaneous use of IxPro-tector and AxProtector to ensure an optimum of security. If you do this, the compiled application is encrypted, and AxProtector adds an auto-Integration of WUPI for .NETStep 1: Integration into the source codeThe integration is exempli“ ed with a small C# application. You can check for an existing license by using the simple query: Wupi.CheckLicense. The return value of Wupi.CheckLicense is TRUE when a license exists and FALSE when the license does WupiCheckLicense expects a number as pa-rameter. This number is a placeholder for the later replaced by IxProtector using a license list. In the example we use the number 1Ž.Start the compiled application. Since the appli-the dummy DLL, while testing you will receive the message WUPI license (1) allocatedŽ.Step 2: Realizing license options with AxProtectorAfter compiling the application, encrypt it with AxProtector while at the same time activating IxProtector. On page Licenselists add a licenselist 1. Now IxProtector knowsŽ which license options you refer to when you call Wupi.CheckLicense(1).The placeholder (1) now may be replaced by several license elements, characterized by diffe-ren

9 t license options. This allows you to cr
t license options. This allows you to create an (CodeMeter/WibuKey) or by software activation (CodeMeterAct). On page error messageŽ, you de“ ne if the error message on calling WUPI functions, when no license is available.If you want, for example, check on the start of your application which modules are activated. If you also want to mask menu items, then deac-tivate the automatic error messages. Otherwise the user would receive separate error messages for each module not activated.license management system into your software. Depending on the availability of the license 14) you can execute your favoured actions.Along with Wupi.CheckLicense, WUPI for .NET also provides you with additionial functions. You may also decrypt or re-encrypt code at runtime, read out license information, decrement unit counter for pay-per-use. More on that in the next KEYnote. Figure: Sample in C# for al license request with WUPI Figure: Protection by AxProtector Figure: Protector - add a license list Figure: Authenti“ cation with CodeMeter CodeMeter Core API Some requirements are not completely met by using AxProtector and the Software Protection API WUPI. In such cases you may wish to use the CodeMeter Core API, the grass roots to which all other APIs and protection mechanisms ultimately refer to. And, using this core leaves nothing to be desired.KNOW-HOW For automatic protection and further protection mechanisms AxProtector, IxProtector and WUPI represent the “ rst class and low-maintenance choice. Why? Because the security of your ap-new WIBU-SYSTEMS software release. Thus, using the CodeMeter Core API is best when mentioned above. The CodeMeter Core API is always downward compatible and a code fragment once generated will also run with future CodeMeter Runtime versions. Just as it is with AxProtector, IxProtector and WUPI, there a current CodeMeter Runtime version even; if your application had been generated using an For example, lets say you plan to display the stored in the CmStick in your program, or to send it along when a support request is issued. Such text, varying in length and stored in the CmStick cannot be read with WUPI while with the CodeMeter Core API a query using the call CmGetInfo

10 () is feasible. However, you do not agai
() is feasible. However, you do not again. With the WUPI function WupiGetHandle() you can get the handle number. Which, you Everything under controlWhen your application operates with variable data, the CodeMeter Core API also allows you to encrypt it using CmCrpyt(). This also allows different security features. For example, you sitive data for different customers, i.e. data readingŽ or decryption is enabled for de“ ned customers only.Along with encryption, the CmStick is also able to sign data. This allows you to con“ rm that the data transferred to a control center by different When your customers programs connect to your update server on a regular basis, along with your own updates, you can also download the extensions for CodeMeter licenses. From within your software you can then import these Core API call CmSetRemoteUpdate(). Or, you can generate context “ les and transfer them cation channels. For example, you could do this to read the current values of incrementing or pay-per-use accounting.Practical helperThese are only a couple of ways to utilize the power of the CodeMeter Core API. Should you have questions concerning this tool, our cus-your questions. If you wish, they can list for you the Core API functions and create matching examples. Or, tell them your goals and they Mr. Mitutoyo Messgeräte GmbH, OberndorfSophisticated protection, sound technical support, and especially the driver concept, all that have convinced us. Just like electronic signing, the authentic transfer of the public key is the main issue for authen-Using the right keyCodeMeter is a very powerful tool; providing several ways to save a private key. The choice of the correct key normally depends on usage.When user management takes place on the server, i.e. the locking of expired accounts, management of access privileges, creation of new accounts, etc., then the SerialKey is the best choice.ŽOut of the boxŽ each CmStick already has a separate arbitrary private key, the SerialKey. The related public key can be read out with the CodeMeter Core API. For example, you are able to read out the public key and save it, in case you want to associate the CmStick to a particular user before shi

11 pping. SERVICEsender.The principle chall
pping. SERVICEsender.The principle challenge of signature methods involves the authentic transfer of the public key. This means the association of public keys to users. Here several solutions exist, from third party trust centers to personal transfer of the public key to the receiver.The signature principle is also used with authentication. The client sends a login request.The server generates an arbitrary sequence as a request (challenge). The server sends the challenge to the The client signs the challenge with the CmStick. The client sends back the answer The server checks the response and Therefore, a CodeMeter Stick is able to simulta-authentication token for accessing online ser-vices. The customer would need only a physical device to act as his bunch of keysŽ.The signature principleWhen applying a secure electronic signature process, a key pair is used „ a public key and a private key. The private key is kept secret, while the public key may be widely distributed. Along with symmetric encryption, CodeMeter can also be used to asymmetrically encrypt or sign data. With this additional feature CodeMeter not only provides software protection, but also provides the structure for many other security applications; for example, electronic signature and authentication. token and dongle together Mr. Ulrich Kostka Festo Didactic GmbH & Co. KG, DenkendorfWe are impressed with our cooperation with WIBU-SYSTEMS for 13 years. Fast delivery and always available and competent support … also directly available to our end-customers … are exemplary. This also holds for the products providing sound but easy-to-use software protection. Especially important for us as company operating worldwide, was the option to remotely-customize licenses meeting customer request … which is easily done with WIBU dongles. Also, for our customers, the WIBU-SYSTEMS license solution is easy to handle and widely accepted. The failure of Wibu dongles is extremely rare. But when they happened, our claims were settled in an accommodating manner very quickly. Altogether, WIBU-SYSTEMS is an ideal and reliable partner that we want to cooperate with for another long time. 12 When do I need “ le encryption?Use cases compri

12 se, for example: of a single *.exe and m
se, for example: of a single *.exe and many *.swf “ les.protection of database applications (e.g. Visual Fox Pro applications consisting database “ les).protection of con“ guration data saved to separate “ les to be read by your software.protection of scripts saved to separate “ les to be processed by your software.protection of data (e.g. measuring data) protection of documents the user gener-Taking advantage of this extra protection does not require you to write a single line of code. This is already automatically handled by AxProtector. the encryption and decryption of data “ les.cutable using AxProtector is to activate the checkbox File Protection on the page Ad-vanced Options.With File ProtectionŽ checked, all “ les opened Dateiverschlüsselung mit AxProtector AxProtector How you encrypt and protect your software with AxProtector against hacker attacks has been discussed in previous KEYnote issues. However, are you aware that you can also automatically protect the data files your Mr. Jörn Schindler SPH GmbH, DortmundThe SPH GmbH team congratulates you on your companys anniversary and we say thank you for the long and pleasant cooperation. For 20 years WIBU-SYSTEMS AG has stood for innovative products with user value. Also, your staff always knew how to support us … fast and competently.We look forward to 20 more years of cooperation. 13 Level 1original (the “le is saved as original. Not encrypted “les are saved with the same key Level 2encrypted (independent of previous encryp-tion the “le is always saved with the “xed key you de“ne)“xed key you de“ne)Level 3no saving (the “le is not saved)CASE STUDY Figure: Filetype options Figure: Loading a data“leRules also apply when saving the “le. You de“ne these rules in AxProtector: for existing but also for new “les.Now you encrypt your data “les with AxPro-tector.Select File protectionŽ in the tab Advanced to be encrypted, and the associated license options.You are also able to de“ne rules for writing the “les. At runtime, the more restrictive settings automatically apply.“le. If a mat

13 ching license exists the “le will o
ching license exists the “le will open. Now, next to the application itself, con“dential data is also securely protected. And this without Figure: Selection dataencryption 14 20 Year Anniversary WIBU-SYSTEMS CodeMeter License Central for genera-tion, management and delivery of license, CodeMeter SD- and CF-Card.Introduction of activation solution: CodeMeterAct. A new of“ ce in Spain. Became a Microsoft Gold Certi“ ed Partner; Coordination of BMWi project VitaBIT (secure mobile solutions) and First global Hackers Contest for CmStick started (prize money: 32 768 Euro). CmStick in precious and robust metal casing. Nomination for Design Award Federal Republic of Germany. Fundamental pa-tent for CodeMeter in the United States and Japan was awarded, numerous new patents “ led. Finalist at SIIA Codie Award in category Best Mobile Solu-tionŽ. Establishment WIBU UK.Establishment of WIBU-SYSTEMS (Shanghai) Co. Ltd. Received the iF Design Award Germany. First-time as a “ nalist at SIIA Codie Award in the category of Best DRM SolutionŽ.BILLBOARD 20 Years WIBU-SYSTEMS Twenty years is a good deal of time for an IT company. At WIBU-SYSTEMS, it seems that this time just flew by. We have always been ready for action: to realize our own visions and to meet customer requests. For over 20 years, this has resulted in steady growth: customers … revenue … staff, and know-how. And the end is not in sight.companys history:Establishment of WIBU-SYSTEMS by Marcellus Buchheit and Oliver Winzenried. First WIBU-BOX as a dongle for the LPT interface.Conversion to WIBU-SYSTEMS GmbH.First dongle as a PCMCIA card, introduced at COMDEX/Fall in Las Vegas. Capital increase and conversion to WIBU-SYSTEMS AG.Certi“ cation according to ISO 9001. 10 Year Anniversary and WIBU-SYSTEMS moves into the new company building in Karlsruhe. First announcement of the WibuKey Hackers Contest. Introduction of document protection: SmartShelter. Establishment of WIBU-SYSTEMS USA Inc. Participation in 5th European Union R&D Supporting Program. Market introduction of CodeMeter, CmStick/M: “ rst dongle with integrated Flash Disk, awarded with iF Design Award in China. European patent for

14 CodeMeter issued. Establishment WIBU Ben
CodeMeter issued. Establishment WIBU Benelux. 20062007200820092005 2001199919971995199119892004 Mr. Horst PoppingaPolo Know-How Industrie-Engineering GmbH, RastedeMore than 14 years ago, we decided to use WibuKey to protect our modular built Crane Management and Visualization System, Service Information System (SIS). And we have never regretted this decision. Congratulations on your 20th company anniversary. COSYNUS designs, plans and operates unified communication and mobile business solutions for intelligent enterprise communication. Since 1993, COSYNUS has been successfully and professionally serving more than 25,000 users in 1,000 companies throughout Europe. Their business is primarily centered on informa-tion servers running software from Tobit David from Research In Motion (RIM). The underlying distinction of the COSYNUS soft-ware sales model is the ”exibility and custom-ization brought to every customer install. Each consists of a basic license, a variable number of user licenses, and additional options; including providing for testing or leased licenses, each needing a managed expiration date.information on whether and up to when, soft-ware maintenance has been obtained by the customer. This prevents a customer without a maintenance contract from importing program updates.Previously, COSYNUS relied on a purely soft-ware-based protection and license management system. However, it turned out to be insecure and in daily practice required unreasonable administrative effort.requirements and the claims made by WIBU-SYSTEMS AG of being able to map any license model in CodeMeter, COSYNUS contacted WIBU-SYSTEMS. As a result, COSYNUS was able, in combination with WIBUconcepts, to design an effective CodeMeter-based license support were impressive. This convinced us that with WIBU-SYSTEMS we had found the right partner. Another plus … the hardware-based install and use our license on any PC, anytime. Along with this effective protection, we were in use.3. Your licensing model is rather ”exible and each install is tailored to meet the request of your customers. No, not that dif“cult. The main work involved very effective programming interface. Also, it was important to us, that our customers were a

15 ble anytime they wanted, to view the lic
ble anytime they wanted, to view the licenses stored in their CodeMeter Sticks. This you al-ready provided, with your simple end-user tools, like the CodeMeter WebAdmin.The semi-automated supply of licenses was easily integrated in our existing work”ow. The by WIBU-SYSTEMS considerably eased the in-tegration.4. What is on the agenda? Are there any further CodeMeter projects in the pipe?First of all, we will simplify logistics for ad-hoc test licenses by additionally integrating Code-MeterAct as a software-based protection. This Stick. But still maintain reliable protection.the design requirements.1. Mr. Strohmaier, you have been using CodeMeter for a year now. Can you The options provided by CodeMeter have met my requirements 100 %. Our teamwork with WIBU-SYSTEMS has been professional, constructive, and cooperative. At “rst, our distribution partner voiced their concern with regard to hardware protection. But right from the start, their custom-ers fully accepted CodeMeter. Meanwhile, we have continuous positive feedback here as well. The return on investment in CodeMeter is mea-sured in no small part by the additional software 2. What was decisive when you “nally SecureCode Seminar in Darmstadt. Afterwards, conference with WIBUconcepts. That CodeMeter was very easy to integrate and to embed in us. Also, we wanted to work with a German vendor who speaks our language, who could respond quickly to our requirements, and who has market expertise.In the run-up, we also tested the end-user and partner hotline … availability and quality of Customer Story Cosynus CUSTOMER STORY Mr. Harold Strohmaier CEO Cosynus GmbH, Darmstadt Investing in CodeMeter pays off instruct you how to integral your licensing system into an ERP and/or CRM system. At the end of the day there is a your code with our solutions. You can register for these free seminars, for the morning and/or afternoon session www.wibu.com/roadshow. More dates in Germany and Austria: www.wibu.de/roadshow Impressum17th edition, spring 2009WIBU-SYSTEMS AGTel. +49 721 93172-0Fax +49 721 93172-22www.wibu.comEditors:Frank SemrauWolfgang VölkerDesign and productiontime. They are protected by the press secret. Articles iden-ti“ ed b

16 y name do not neces-sarily re” ect
y name do not neces-sarily re” ect the opinion of the editors.WIBU, CodeMeter and Smart-Shelter are international trade-marks of WIBU-SYSTEMS. All other trademarks belong to their respective holders. (C) 2009 WIBU-SYSTEMS. All rights reserved. ROADSHOWWIBU-SYSTEMS organizes in 2009 a new series of se-minars. During the morning session we will address the challenges in protecting your non-managed or .NET/Java + AxProtector to you. After lunch the different ways of secure licensing of software with CodeMeter and/or CodeMeterAct will be presented. A separate session will Visit us at the following fairs:CeBIT 2009: March 3- 8, 2009: Hall 11 Booth B41March 4, 2009, 3:00 … 5:00 PMBackof“ ce Integration Seminar. Where we discuss the intricacies of generating, managing and delivering software licenses!Embedded: ŒIP Protection using Dongles: Attend the lecture by Rüdiger Kügler, ch 5, 2009, 1:30 - 2:00 p.m.ŒCryptography and Embedded Security WorkshopHannover Messe Industrie: April 20-24, 2009: Hall 17 Booth Product ProtectionSolutions for protection against pirated copies by protection of software and data in the April 21, 2009: Interesting lectures in Robotation Academy, Hall 17 Beginning in March 2009, we will continue our successful roadshows. The seminars will be held in the morning with options for discussion during lunch, and a separate session in the afternoon. Wednesday 25-03 Brussels (B) Thursday 26-03 Utrecht (NL) Wednesday 1-4 Madrid (ES) Tuesday 21-4 Gent (B) Wednesday 22-4 Eindhoven (NL) Tuesday 28-4 London (UK) Wednesday 6-5 Lisbon (PT) Tuesday 12-5 Antwerpen (B) Wednesday 13-5 Delft (NL) Kok Tuesday 16-6 Deventer (NL) Wednesday 17-6 Milton Keynes (UK) Wednesday 24-6 Barcelona (ES) Wednesday 22-7 Valencia (ES) San Francisco9 JunNew York City11 Jun Washington DC21 Jul San Jose27 Jul Dallas29 Jul Austin31 Jul Atlanta7 Aug Seattle27 Aug Salt Lake CitySeminar-dates in EuropeSeminar-dates in the U