By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,165 Members | 1,409 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,165 IT Pros & Developers. It's quick & easy.

Privacy invasion (sorry for misposting)

P: n/a
Nak
Hi people,

I'm having a bit of a brain storm at the minute and wouldn't mind some
personal opinions on some things.

To license my applications I have decided to make a license manager
service that holds application license files (RSA encrypted). When the
application launches the license manager is consulted as to whether the
application is *allowed* to run or not. The license file for that
particular application is held by the license manager which decrypts it and
responds as necessary.

Now what I wanted to do was make the license file simply an XML file
that contains some information, but it's what information it *should*
contain is what my main concern is, for example...

Obligatory information,

* Name
* Company

"Is this a 'Privacy invasion" information?"

* Contact details
* System information (To prevent the application from being used on more
than 1 system).

Hmmm, any ideas on this?

BTW, this is something that I may want to release for free, so some of
you may be interested in this, I'm certainly interested in making my
applications more secure with as little code as possible are you?

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Nov 20 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Cor
Hi Nick,

I will think about it further

The first thoughts are I mis in my opinion 3 disclaimers.
On what systems it should not be used and that prevent you from users
with strange systems with claims.
The rights of the customer against you (and that are non of course)
The rights about you against the customer. (and that are a lot of
course)

Contact information is always something dificult.
It can make your program fast outdated. I would not do that untill you are
sure the adresses stays for a long time.
Cor
Nov 20 '05 #2

P: n/a
Nak
Hi Cor,
On what systems it should not be used and that prevent you from users
with strange systems with claims.
The rights of the customer against you (and that are non of course)
The rights about you against the customer. (and that are a lot of
course)
I'm thinking that the license manager itself should be able to be configured
for specific applications. For example when the application is first run,
it connects to the license manager and creates an account specific for that
application, the account manager could hold details of EULA's, trial length
(if necessary), number of users the license is valid for etc. Imagine the
license manager as being a simple engine that could be employed by .NET
applications.
Contact information is always something dificult.
It can make your program fast outdated. I would not do that untill you are
sure the adresses stays for a long time.
Not my contact information, the contact information of the person the
license is created for. My idea of the license file is to create something
personal to the user, something that they would not want to distribute to
others, it will unlock their software easier and hopefully be more secure
than using a simple username and serial number system.

Good points though Cor, this is something that *I* personally need quite
essentially as I seriously doubt the security of the standard license
provider available in .NET, it's just not secure and versatile enough.

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"Cor" <no*@non.com> wrote in message
news:3f**********************@reader20.wxs.nl... Hi Nick,

I will think about it further


Cor

Nov 20 '05 #3

P: n/a
Cor
Hi Nick,

I will think about it further

The first thoughts are I mis in my opinion 3 disclaimers.
On what systems it should not be used and that prevent you from users
with strange systems with claims.
The rights of the customer against you (and that are non of course)
The rights about you against the customer. (and that are a lot of
course)

Contact information is always something dificult.
It can make your program fast outdated. I would not do that untill you are
sure the adresses stays for a long time.
Cor
Nov 20 '05 #4

P: n/a
Nak
Hi Cor,
On what systems it should not be used and that prevent you from users
with strange systems with claims.
The rights of the customer against you (and that are non of course)
The rights about you against the customer. (and that are a lot of
course)
I'm thinking that the license manager itself should be able to be configured
for specific applications. For example when the application is first run,
it connects to the license manager and creates an account specific for that
application, the account manager could hold details of EULA's, trial length
(if necessary), number of users the license is valid for etc. Imagine the
license manager as being a simple engine that could be employed by .NET
applications.
Contact information is always something dificult.
It can make your program fast outdated. I would not do that untill you are
sure the adresses stays for a long time.
Not my contact information, the contact information of the person the
license is created for. My idea of the license file is to create something
personal to the user, something that they would not want to distribute to
others, it will unlock their software easier and hopefully be more secure
than using a simple username and serial number system.

Good points though Cor, this is something that *I* personally need quite
essentially as I seriously doubt the security of the standard license
provider available in .NET, it's just not secure and versatile enough.

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"Cor" <no*@non.com> wrote in message
news:3f**********************@reader20.wxs.nl... Hi Nick,

I will think about it further


Cor

Nov 20 '05 #5

P: n/a
Hi Nick,

Your serious enquiry seems to live on - hidden in that other thread. So
I'll post my OT here, lol.

There's a query from Kevin A. topic: splitting bitmaps which requires your
expertise. No one else has picked up on it but it's one that you'll be able to
answer with your eyes closed, I should think.

Regards,
Fergus
Nov 20 '05 #6

P: n/a
Nak
Hi Fergus,

WOW, something that *I* can help with? that makes a change, I'm off
there ;-)

Nick.

--
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
"No matter. Whatever the outcome, you are changed."

Fergus - September 5th 2003
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Nov 20 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.