How Do I License & Protect My Software?

Discussion in 'C Programming' started by itamtodd@isu.edu, Jun 8, 2006.

  1. Guest

    I am in the process of developing a small program that I will be trying
    to sell to different institutions. The program is written in VB and
    uses an Access database.

    Now how do I go about selling people a license for my software? And
    also how do I protect my software from just being ripped off, i.e.
    Encrypt it?


    Thanks
    -Todd
    , Jun 8, 2006
    #1
    1. Advertising

  2. Eric Sosman Guest

    wrote On 06/08/06 15:35,:
    > I am in the process of developing a small program that I will be trying
    > to sell to different institutions. The program is written in VB and
    > uses an Access database.
    >
    > Now how do I go about selling people a license for my software? And
    > also how do I protect my software from just being ripped off, i.e.
    > Encrypt it?


    Your best plan is to ask questions about licensing,
    about Visual Basic, and about Access in a newsgroup that
    has nothing to do with any of those topics. That will
    make people will think you are a fool, and since they
    won't believe a fool can write a worthwhile program they
    will have no incentive to steal it.

    Congratulations! You should be all set now.

    --
    Eric Sosman, Jun 8, 2006
    #2
    1. Advertising

  3. Default User Guest

    Eric Sosman wrote:

    >
    >
    > wrote On 06/08/06 15:35,:
    > > I am in the process of developing a small program that I will be
    > > trying to sell to different institutions. The program is written
    > > in VB and uses an Access database.
    > >
    > > Now how do I go about selling people a license for my software? And
    > > also how do I protect my software from just being ripped off, i.e.
    > > Encrypt it?

    >
    > Your best plan is to ask questions about licensing,
    > about Visual Basic, and about Access in a newsgroup that
    > has nothing to do with any of those topics. That will
    > make people will think you are a fool, and since they
    > won't believe a fool can write a worthwhile program they
    > will have no incentive to steal it.
    >
    > Congratulations! You should be all set now.


    In spades. He posted this, individually, to several groups.



    Brian
    Default User, Jun 8, 2006
    #3
  4. In article <>,
    <> wrote:
    >I am in the process of developing a small program that I will be trying
    >to sell to different institutions. The program is written in VB and
    >uses an Access database.


    >Now how do I go about selling people a license for my software? And
    >also how do I protect my software from just being ripped off, i.e.
    >Encrypt it?



    VB and Access suggests that your program is written for Microsoft Windows.
    If so, then the known ways to prevent your software from being ripped off
    are:

    - don't write the program; or
    - thoroughly destroy *all* of the equipment used immediately after
    you finish writing the program and before even a single copy is made; or
    - set the licensing conditions such that it is freely redistributable
    (something can only be "ripped off" if you aren't already giving
    it away); or
    - use a hardware assist device that uses quantum entanglement
    ("action at a distance") to run the program on equipment under your
    control [and I'd have to think more to determine whether this
    method is completely secure.]

    Techniques such as encryption will NOT prevent your software
    from being ripped off: such techniques merely -delay- the software
    from being ripped off. A much less expensive and much more effective
    way to -delay- your software from being ripped off is to simply
    write the software so badly that no-one would want to bother copying it.
    --
    "It is important to remember that when it comes to law, computers
    never make copies, only human beings make copies. Computers are given
    commands, not permission. Only people can be given permission."
    -- Brad Templeton
    Walter Roberson, Jun 8, 2006
    #4
  5. >Now how do I go about selling people a license for my software? And
    >also how do I protect my software from just being ripped off, i.e.
    >Encrypt it?


    License the program under the GPL. That way copying it won't
    be "ripping you off".

    Gordon L. Burditt
    Gordon Burditt, Jun 8, 2006
    #5
  6. CBFalconer Guest

    wrote:
    >
    > I am in the process of developing a small program that I will be
    > trying to sell to different institutions. The program is written
    > in VB and uses an Access database.
    >
    > Now how do I go about selling people a license for my software? And
    > also how do I protect my software from just being ripped off, i.e.
    > Encrypt it?


    Insufficient information. We will have to see the source to give
    any decent advice. Just paste it into a reply here and encrypt it
    with ROT13. Then wait for sparkling advice. Just be sure that
    your source compiles under standard C, which may require some
    rewriting. Keep line lengths under 65 for usenet posting.

    --
    "Our enemies are innovative and resourceful, and so are we.
    They never stop thinking about new ways to harm our country
    and our people, and neither do we." -- G. W. Bush.
    "The people can always be brought to the bidding of the
    leaders. All you have to do is tell them they are being
    attacked and denounce the pacifists for lack of patriotism
    and exposing the country to danger. It works the same way
    in any country." --Hermann Goering.
    CBFalconer, Jun 8, 2006
    #6
  7. In article <>,
    Gordon Burditt <> wrote:
    >>Now how do I go about selling people a license for my software? And
    >>also how do I protect my software from just being ripped off, i.e.
    >>Encrypt it?


    >License the program under the GPL. That way copying it won't
    >be "ripping you off".


    But under the GPL, if someone were to redistribute the binary without
    the source, then the OP -would- be ripped off. To avoid being ripped
    off, it is better to license under one of the other licenses
    (one of the BSD ones maybe?)
    --
    I was very young in those days, but I was also rather dim.
    -- Christopher Priest
    Walter Roberson, Jun 9, 2006
    #7
  8. Lew Pitcher Guest

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    Walter Roberson wrote:
    > In article <>,
    > Gordon Burditt <> wrote:
    >>> Now how do I go about selling people a license for my software? And
    >>> also how do I protect my software from just being ripped off, i.e.
    >>> Encrypt it?

    >
    >> License the program under the GPL. That way copying it won't
    >> be "ripping you off".

    >
    > But under the GPL, if someone were to redistribute the binary without
    > the source, then the OP -would- be ripped off.


    I don't see how. Under the GPL, you do not have a licence to distribute
    the binary without the source. Since someone who distributes GPLed
    software without the source has violated the distribution licence, the
    software author can take the distributor to court for copyright
    violation. Such a violation wouldn't go uncompensated.

    > To avoid being ripped
    > off, it is better to license under one of the other licenses
    > (one of the BSD ones maybe?)


    - From the "being ripped off" POV, the BSD licences are no help. As I
    understand it, they give explicit permission for distributors to
    repackage and distribute without accompanying source, and without
    compensation to the original author. So, the original author doesn't
    even have copyright law to fall back on to enforce compensation.

    - --

    Lew Pitcher, IT Specialist, Corporate Technology Solutions,
    Enterprise Technology Solutions, TD Bank Financial Group

    (Opinions expressed here are my own, not my employer's)
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.3 (MingW32)
    Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

    iD8DBQFEibGuagVFX4UWr64RAiFnAJ9YMOI0pBapVQkhCwPqoISDRegwbwCg83KE
    44npY/IC+NdlorLZZBJZwgc=
    =PC7K
    -----END PGP SIGNATURE-----
    Lew Pitcher, Jun 9, 2006
    #8
  9. >But under the GPL, if someone were to redistribute the binary without
    >the source, then the OP -would- be ripped off.


    I disagree. *WHO* is ripped off if the binary is distributed without
    the source? I'd say it's the *recipient*, not the author.

    You do have a point, though.

    >To avoid being ripped
    >off, it is better to license under one of the other licenses
    >(one of the BSD ones maybe?)


    Gordon L. Burditt
    Gordon Burditt, Jun 9, 2006
    #9
  10. Gordon Burditt said:

    >>But under the GPL, if someone were to redistribute the binary without
    >>the source, then the OP -would- be ripped off.

    >
    > I disagree. *WHO* is ripped off if the binary is distributed without
    > the source? I'd say it's the *recipient*, not the author.
    >
    > You do have a point, though.


    Who does?

    Please retain attributions.

    Thank you.

    --
    Richard Heathfield
    "Usenet is a strange place" - dmr 29/7/1999
    http://www.cpax.org.uk
    email: rjh at above domain (but drop the www, obviously)
    Richard Heathfield, Jun 9, 2006
    #10
  11. On Thu, 08 Jun 2006 17:53:06 -0400, in comp.lang.c , CBFalconer
    <> wrote:

    > wrote:
    >>
    >> I am in the process of developing a small program that I will be
    >> trying to sell to different institutions. The program is written
    >> in VB and uses an Access database.
    >>
    >> Now how do I go about selling people a license for my software? And
    >> also how do I protect my software from just being ripped off, i.e.
    >> Encrypt it?

    >
    >Insufficient information.


    Not really - he told us its written in VB and Access, that pretty much
    secures it from use :)

    To the OP: this isn't a question for comp.lang.c, you might want to
    STFW instead.

    --
    Mark McIntyre

    "Debugging is twice as hard as writing the code in the first place.
    Therefore, if you write the code as cleverly as possible, you are,
    by definition, not smart enough to debug it."
    --Brian Kernighan
    Mark McIntyre, Jun 9, 2006
    #11
  12. In article <Skiig.1192$>,
    Lew Pitcher <> wrote:

    >> To avoid being ripped
    >> off, it is better to license under one of the other licenses
    >> (one of the BSD ones maybe?)


    >- From the "being ripped off" POV, the BSD licences are no help. As I
    >understand it, they give explicit permission for distributors to
    >repackage and distribute without accompanying source


    I think you missed the joke. If you distribute under the Berkeley
    licence, you are effectively agreeing that you won't consider any use
    of it to constitute "ripping off".

    -- Richard
    Richard Tobin, Jun 9, 2006
    #12
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Volker Grabsch
    Replies:
    2
    Views:
    730
    Michael Hudson
    Jul 25, 2005
  2. Replies:
    21
    Views:
    1,077
    protectlicense
    Jul 11, 2007
  3. Replies:
    2
    Views:
    351
    Victor Bazarov
    Jun 8, 2006
  4. Replies:
    4
    Views:
    596
    Ian Collins
    Jun 8, 2006
  5. John
    Replies:
    0
    Views:
    1,009
Loading...

Share This Page