Thanks to the new DBGENCKEY parameter, you can now debug your customers' code while protecting your source.
Written by Gina Whitney
If you stop and think about what some of your most important assets to your company are, your source code would most likely be on that list. Protecting your code is essential. Unfortunately, there are times when one of your customers encounters a problem. The easiest way to figure out the problem would be to put a debuggable version of your code onto the system. But now, your code isn't protected anymore. So you either expose your code or figure out another way to diagnose the problem. Wouldn't it be nice to just ship a debuggable version of your code and have it secure? In 7.1, the ILE compilers (RPG, COBOL, CL, C, and C++) and precompilers have a new parameter that allows you to encrypt your debug views. This means that you can ship debuggable code and know that your code is not exposed.
The chances of travelers losing sensitive data riding on laptops, mobile devices, or USB drives are running high today for anyone who doesn't effectively encrypt their data.
Written by Chris Smith
Editor's Note:Chris Smith is on vacation this week, so we have revived one of his more popular columns pertaining to laptop and flash-drive security and data encryption that first appeared in June 2008 as "Hardware Encryption Offers Benefits over Software Encryption." The topic has as much relevance today as it did then.
We usually think of encrypting data as a way to protect it from hackers and criminals, but did you ever consider that the U.S. federal government can now search your laptop without probable cause?