AnsweredAssumed Answered

vrf Dongle protection

Question asked by VRFuser on Feb 2, 2006
This topic has come up in the past, both in the Vrf and with my own software, and the answer usually came down to trusting your customer.

Every VEE program I ever wrote or heard of was a customized product tied to a specific customer, product, or both.  It is not something I expect to see copied in the mass market the way music or common software is.  The other issue is ownership in general.  Most of my VEE production has been as a contractor and the software falls into the catagory of a "Work for Hire"
owned by the company that hired me.  I never worry about someone copying the programs that I own.

Put a "Do not copy" clause in your contract, a copyright notice on your product, and then just keep an eye out for your product appearing in some other form in the same marketplace as your customer.

Robert Reavis
Warm Springs Computer Works



----- Original Message -----
From: "Stan Bischof (Richard S)" <rsb@soco.agilent.com>
To: "VRF" <vrf@agilent.com>
Cc: <vrf@agilent.com>
Sent: Friday, January 27, 2006 7:35 AM
Subject: Re: [vrf] Dongle protection


> Michele Gobbi <gobbi.michele@gmail.com> wrote:
>> Hi VRF,
>>
>> I was wondering if anyone has never tried to protect a vee application
>> with an usb key. I need to do it to protect and license my software. I
>> need to use the key to be sure that my software cannot be used in two
>> PCs at the same time.
>>
>> If somebody had the same problem before, which dongle do you advice to
>> purchase?
>>
>> Thanks and Regards
>> Michele
>
> You may be looking at this backward. Unless you are planning to
> invent your own protection software, you should start by selecting
> the software first than use whatever dongle(s) that software
> supports.
>
> If you are looking at writing your own software then you
> might look at Rainbow Technologies ( www.rainbow.com )
> as they have been doing dongles for a very long time. I believe
> that they also have software solutions, though the clear
> industry leader is flex ( www.macrovision.com ).
>
> One thing to watch out for: licensing is NOT value added for the
> end user and can be a major support issue for you. It could easily be
> your single biggest support issue since there are many things that
> can fail- such as competing license schemes/dongles if user has
> other software that uses similar schemes. Hence you'll want to
> keep things as absolutely simple and foolproof as possible- and
> very fully test the installs and usage before shipping. And make
> sure your support team is very well versed in all the things that
> can go wrong. Ideally put a troubleshooting guide in your docs.
>
> With that said, such licensing though is very common,
> so should be quite doable with VEE. Odds are you'll be using a DLL
> from the software vendor you choose.
>
> good luck with your venture!
>
> Stan
>
>
> --------------------------------------------------------------------------
> Stan Bischof  Agilent Technologies  707-577-3994  stan_bischof@agilent.com
> --------------------------------------------------------------------------
>
> ---
> You are currently subscribed to vrf as: robert@wscw.com
> To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
> To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
> To send messages to this mailing list,  email "vrf@agilent.com".
> If you need help with the mailing list send a message to
> "owner-vrf@it.lists.it.agilent.com".
> Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
>



---

To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list,  email "vrf@agilent.com". 
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".

Outcomes