Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: DXL Encrypter
Topic Summary:
Created On: 13-Nov-2007 21:47
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 13-Nov-2007 21:47
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

The DXL encrypter supplied by Telelogic seems a bit clumsy. I figure to write a DXL front end to it, where the 'input' would be a Windows directory housing the deployed DXL (target of 'addins' and 'projectaddins'), and my DXL would prepare the DXL for encrypting and encrypt it into a parellel windows folder. Each un-encrypted DXL would generate two files; one was encrypted and the other one a skeleton un-encrypted dxl, which had the comment line and comment block from the original DXL and an #include statement to the encrypted file.

Then I wonder about inserting the < as the 3rd character, as dictated by the encrypter.

Anyone have any luck actually using the encrypter for lots of DXL?

- Louie
Report this to a Moderator Report this to a Moderator
 14-Nov-2007 14:08
User is offline View Users Profile Print this message


David Pechacek

Posts: 674
Joined: 5-Dec-2006

I use the encrypter for all my code. I've been meaning to write a quick VB tool that lets me pick a DXL file or group of DXL files and encrypts them. For my encrypted code, at the end of the file name I put a "-e" so I know it's encrypted.

-------------------------
David Pechacek
AAI Services Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
Report this to a Moderator Report this to a Moderator
 14-Nov-2007 14:56
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

So when you write a new script you manually encrypt it and then deploy the encrypted file?

You need an unencrypted skeleton file that includes the encrypted file in order for it to appear in the menues. Do you maintain two files, the skeleton and the one with the meat that gets encrypted?

- Louie
Report this to a Moderator Report this to a Moderator
 14-Nov-2007 16:06
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

I maintain 2 files.
script.dxl contains nothing but #includes.
script.inc contains the meat.

Two reasons for having 2 files:
1. I can have a good long comments and version information, dates etc that remain readable in the dxl file.
2. I can encrypt all .inc files whether they start with //< or not.

Originally I started doing this way merely because that was the way Telelogic seemed to do it.

Just thought of a 3rd reason:
You can plug and unplug functionality by (un)commenting out a single #include.

-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 14-Nov-2007 16:27
User is offline View Users Profile Print this message


David Pechacek

Posts: 674
Joined: 5-Dec-2006

Originally posted by: Louie Landale

Do you maintain two files, the skeleton and the one with the meat that gets encrypted?


Yes. I do what Tony does.

-------------------------
David Pechacek
AAI Services Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
Report this to a Moderator Report this to a Moderator
 14-Nov-2007 18:30
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Just renamed one of my *.dxl to *.inc and encrypted it. using DOS 'fc' I see the encrypted is exactly the same for *.dxl as for *.inc; specifically if it doesn't start with //< then it encrypts but gets a wierd 'EOF' DXL error.

Not sure I want to maintain two files in configuration management; where the version info of the real one is captured in the 2nd.

The alternative, however, does seem pretty clumsy: have one source ascii *.dxl file that, when deployed, is split into two files [1] unencrypted *.dxl with the version comment line and comment block info and an #include statement to the encrypted version [2] the encrypted version.

Mmmmm. What to do...

- Louie
Report this to a Moderator Report this to a Moderator
 16-Nov-2007 09:47
User is offline View Users Profile Print this message


Oliver Röpke

Posts: 42
Joined: 23-Nov-2005

Hi Louie,
hi all :-)

I was wondering about the discussion about one file/two files, since it is quite usual to me to have at least (!) two files which build up a Dxl user function.

My approach of deploying Dxl files to our customers is the following:
1. All the mentioned directories are located beneath a relative root directory which will be the root for all values for the "Addins" and "ProjectAddins" registry keys.

2. One directory for all (popup) menue definition files for the DB explorer window

3. One directory for all (popup) menue definition files for formal module windows

4. The menue definition files have the extension ".dxl". They contain version information/file header and one include statement to an include file which is the entry point to the user's functionality. Location of the file: see point 5.

5. One directory which contains a directory structure to store "real" Dxl code placed in different files to achieve the goal of high amount of code reuse and very good maintainability (programmers sometimes love forget about these points ;-).

5.1 Example of directory structure for code:
CoreFunctions
AdminFunctions
Interfaces
COM
ChM
CM
Miscellaneous
UserFunctions
Baselines
Stakeholder
Traceabilty
....


So, if we decide to hide the code from our users we simply encrypt all the files beneath the directory mentioned in point 5 during our release procedure. That's all.
Of course all the files are prepared to be encrypted.


Cheers,
Oliver

-------------------------
Greetings,<BR>Oliver<BR><BR><BR>Oliver Roepke<BR>Axis Engineering AG, Munich
Report this to a Moderator Report this to a Moderator
 8-Oct-2008 15:08
User is offline View Users Profile Print this message


Douglas Perez

Posts: 47
Joined: 20-Feb-2008

What if i'm running DOORS client from a server and not from my machine, does the program works the same with or without DOORS installed?

I read the readMe file and apparently is not possible, I'm just wondering if someone had the same situation and was able to control it.
Report this to a Moderator Report this to a Moderator
 8-Oct-2008 16:03
User is offline View Users Profile Print this message


David Pechacek

Posts: 674
Joined: 5-Dec-2006

I'm a little confused at what your asking doug. Are you asking if DOORS will work if you are running the doors.exe off a server or if encrypted files will?

-------------------------
David Pechacek
AAI Services Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
Report this to a Moderator Report this to a Moderator
 8-Oct-2008 19:03
User is offline View Users Profile Print this message


Douglas Perez

Posts: 47
Joined: 20-Feb-2008

I read this and I was wondering if i'm going to be able to install and use the encrypted tool, even though DOORS client is running from a server in batch mode not from my machine.


Encrypted Tool Readme File
--------Important Information---------
The DXL Encryption tool is for DOORS 8.x on Windows platforms


Use the DXL Encryption Tool to encrypt DXL files you have written. The tool can be used to encrypt DOORS 8.0 or 8.1 DXL files. The tool is a one way encryption tool, and does not decrypt files. Customers are advised to keep the original DXL that they encrypt in a safe place.


Files that have been encrypted by the tool are decrypted by the DOORS client, which can run any DXL files that have been encrypted by the tool. Encrypted DXL cannot be loaded and run from the DXL Interaction window, it must be #included.


It is not possible to execute encrypted DXL from a menu item. If this is required, a wrapping un-encrypted DXL file must be used.


The encryption tool is not unicode enabled. This means that all paths and filenames must be ASCII.


The encryption tool uses similar security to the encrypted DXL that is shipped with DOORS.
Report this to a Moderator Report this to a Moderator
 8-Oct-2008 22:04
User is offline View Users Profile Print this message


David Pechacek

Posts: 674
Joined: 5-Dec-2006

You must have the DOORS client installed where you are installing the encryption tool. If you have write access to the server, you can install it there. But you must do it from the server or while remotely logged in.

Once installed you will need to run the encryption tool from the command line on the server.

-------------------------
David Pechacek
AAI Services Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
Report this to a Moderator Report this to a Moderator
 10-Oct-2008 19:57
User is offline View Users Profile Print this message


David Jakad

Posts: 94
Joined: 20-Jul-2007

I managed to write a Windows batch file that will encrypt an entire source directory (and subdirectories) of DXL files, and builds the proper addin menu file structure with all the .hlp files, .idx files, and wrapper .dxl files which #include the encrypted files. It uses the source directory structure to determine the addin menu structure, and it uses the comment lines and blocks at the top of the source .dxl files to determine the text for the menu options and the text for the .hlp files. It can be done.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.