Jump to content

hugh

Members
  • Posts

    3
  • Joined

  • Last visited

    Never

Posts posted by hugh

  1. QUOTE(Mikkel @ Nov 15 2007, 03:35 AM)

    I have heard that C is much easier to reverse engineer than Labview so I do not think I would. i also have contacted Labview and here is their reply

    Hey Hugh,

    This is Ryan from National Instruments. As in my previous email, in

    version 8.0 and less you can change the file name of the .exe

    application to .llb and see a list of the vi's that are used in the

    program. You cannot get back to the block diagram from a .exe. If

    you want to add a further layer of protection then you can completely

    remove diagrams from the source code before you even compile down

    into a .exe. Make sure you back up your program because when you

    remove the block diagrams you can't get them back.

    Here is a link on how to remove the block diagrams from the source code:

    And here is a link to what is exactly happening when you remove them from

    the source code:

    I have verified this information with a LabVIEW Platinum member. Let me

    know if this answers your question.

    Regards,

    Ryan Northington

    Applications Engineering

    National Instruments

  2. Assuming that someone really wanted to reverse engineer my executable like a large corporation. they send it to Russia and throw a ton of money at it.

    But I dont make any sense of my internal VI names would they be able to accomplish this and could I make it even harder for them to do this. I am a small company and the last company my partner started got ripped off by a huge company who just infringed on our patents and put us out of business and we just did not have the money to battle them in court.

    QUOTE(MikaelH @ Nov 14 2007, 03:45 PM)

    You can extract all VIs from the executable very easy, but of cause you access see the block diagram (since it's not included)

    But you can see the hierarchy of you VIs and if you haven't renamed the VIs name and modified the icons, you could get a quite good idea how the code is constructed.

    But to understand the algorithm you use, you have to look into the compiled code in every VI and understand it. And only NI has the capability to do that.

    So I would say your code it really safe.

    Cheers

    Mikael

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.