![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Encrypting DXL Topic Summary: Created On: 23-Mar-2007 12:42 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Recently I have downloaded Telelogic's DXL encryption tool.
For some of my scripts it works just fine, but for others, when I try to run the encrypted inc-files I get messages like: -E- DXL: <scriptname.inc:1> badly formed token (EOF) or -E- DXL: <scriptname.inc:1> undeclared variable (uE) while the original script runs without complaining. Does anyone have any experience with the encryption tool? all hints are welcome Karl |
|
![]() |
|
![]() |
|
Karl,
I've used it with no problems. Did you do the following: The first three bytes of the DXL file that you want to encrypt must be: //< If these characters are missing DOORS will not be able to execute the DXL. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Where can I get information on this tool?
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
David -
Here you go. It is for DOORS 8.1 only. https://support.telelogic.com/en/doors/dxl/ Click on "DXL Encryption Tool" ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
|
![]() |
|
Are you trying to run the encrypted file diirectly?
You cannot run an encrypted file directly, you must #include it in another script. The interpreter will only decrypt scripts as necessary when performing the #include. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Thank you for your responses, Michael and Tony, |
|
![]() |
|
![]() |
|
Hi Karl,
with Doors 8.x I had sometimes problems on using german special chars like ä, ö, ü. Sometimes the code did not run, even if the chars are in strings! Another thing, is that sometimes the code did not run, if the last line was a line comment. So inserting an empty line as last line has solved this problem. And last but not least - Doors seems to use always UTF-8 file format with its header. In some Editors it may appear as:  in the beginning which represents the UTF-8 Header "EF BB BF 42" But never tried the encryption tool ... may be it is sensitive for the described items?! Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Thanks Pete.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
The problem is probably because of some unicode (UTF-8) character that got embedded into you text because of some cut and paste.
Easiest solution to remove these characters for most people will be to open the source in microsoft word and select radio button MS-DOS for text encoding. Then remove the unicode characters and save the file. |
|
![]() |
|
![]() |
|
Thanks Reik and Ron,
the problem apparently was because of some UTF-8 characters at the very beginning of the file... I only do not understand how those got into this particular file but not into the others. Another thing I observed: in some cases a blank line at the end of the file caused a complaint and in some cases a blank character after the first three bytes did that.. thanks again Karl |
|
![]() |
|
![]() |
|
DOORS 8.1 dxl editor may put the following 3 characters at start of a saved file: 
|
|
![]() |
|
![]() |
|
DOORS Editor adding UTF character to dxl script was logged as a defect on 04/04/07 (Case VT6016578)
The DXL encryptor has problems with the UTF marker at the start of the file. The only current workaround is to make sure that the file is not UTF-8. Edited: 4-Apr-2007 at 17:38 by ron lewis |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Encrypting DXL
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.