Infralution Support Forum Index Infralution Support
Support groups for Infralution products
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

source code to AuthenticationServer.dll

 
Post new topic   Reply to topic    Infralution Support Forum Index -> Licensing Support
View previous topic :: View next topic  
Author Message
frankcrowder



Joined: 04 Dec 2008
Posts: 7

PostPosted: Thu Dec 04, 2008 10:42 pm    Post subject: source code to AuthenticationServer.dll Reply with quote

I have been looking for the code for this dll and it is not in my purchase.

What I want to do is add a way for my customers to transfer (unistall and re-install) the software from one computer to another.

the process would be something like this.

un-install connects to the server and sets the installs allowed to 0 and deletes the lic file and adding a flag somewhere to let me know it had been un-installed from this computer to prevent them from just keeping a copy of the lic file. they as me for a new license key that I send them after I see that the allowed installs is 0 and another field has been set or changed.
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Fri Dec 05, 2008 9:47 pm    Post subject: Reply with quote

The source code for the authentication server is a separate purchase (see www.infralution.com/licensingpurchase.html). The problem with this approach is that is is always possible for someone to circumvent it by simply taking an image of their computer, uninstalling and transfering the license to another computer and then restoring the image on their original computer. The only way to avoid this is to authenticate the license key every time you program runs - but this is too intrusive for most software applications.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
frankcrowder



Joined: 04 Dec 2008
Posts: 7

PostPosted: Sun Dec 07, 2008 7:47 pm    Post subject: source code for authentication Reply with quote

OK, I will buy it but thought I was getting all the source code to what I ordered. anyway, I ordered ILS Single and IPN so I would not have to connect to or use someone elses servers. I have added the code to my program and it connects to "http://Infralution .com/webservices" to do most of its online stuff, IF I order the code for the Autientication Web Site, can I change the code to use MY server for webservices or am I going to have to leave that pointing to YOU? or do I need to BUY something else? and if so WHAT.

from your own website:
Code:
Source Code Integration - Full source code is supplied for the licensing classes you call from your application. This allows the licensing code to be fully integrated into your own applications or components, which means there are no third party DLLs to distribute and the licensing code can be fully obfuscated using your normal obfuscator.

and
Code:
Full C# source code for the IPN.NET Server is included, allowing you to fully customize the solution to your requirements

the above lead me to believe that I would have all I needed to use this system without connecting to other servers and would have all the needed source code so that I would not have to use other DLLs.

I have just ordered the Authentication source code for $80 and the License Tracker application Source code for $140.

I ordered the ILS Single License for $140 and the IPN for $90 the other day.

This brings my total to $450

am I going to need anything else?

Infralution wrote:
The problem with this approach is that is is always possible for someone to circumvent it by simply taking an image of their computer, uninstalling and transfering the license to another computer and then restoring the image on their original computer.


What is stopping them from doing that now? if the user is that smart, then they will know just to change the computer name!

I am using the Hard Drive serial number and or the CPU to lock the program to the computer. cloning the hard drive un-installing the software, installing it on a second computer and restoring the clone just to get a second copy of the software is more work then most people that know how to do this will do when they could just buy a second copy. the idea is to make it not cost effective or easy for them to do and to prevent KEYGEN type programs from working.

I went with your system because it has the source code. this allows me to make some changes that will prevent a "generic" crack of your system from working on my system. anyone can buy the source code and find the location for the 'eval' information in the registry and create a program that will extend or remove the 'eval' information. but, if I make that and other parts of the code work in a different way, the "Generic" crack would not work.


Last edited by frankcrowder on Sun Dec 07, 2008 8:49 pm; edited 1 time in total
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Sun Dec 07, 2008 10:32 pm    Post subject: Reply with quote

You don't need to purchase the Authentication Server source code to host it on your own server. If you follow the instructions in the help you can deploy the Authentication Server assemblies supplied, to any server of your choosing. You then change the License Parameters included in your Application code to contact that server. Your application code will not contact our servers at all. We don't actually even support authenticating licenses using our servers - you must use your own. The sample applications distributed with ILS contact an Authentication Server running locally on your own development machine. You only need the source code for the Authentication Server and License Tracker if you wish to substantially modify the way they work (as would be the case for implementing a license transfer mechanism).

The statements about source code with the product are correct and as clear as we could make them. ILS does include source code for the classes your application calls and IPN.NET does come with full source code. The same web page has the following paragraph:

Quote:
Full Source Code Option - full source code for the License Tracker application and Authentication Web Service can be purchased separately for those companies that wish to use License Tracker as a springboard for developing their own in-house software.


We will however see if we can word the statements any better. If you purchase License Tracker and Authentication Server then you have the full source code for the Licensing System. The License Tracker application does use some other UI controls for displaying data - however we include special license keys for these (found in the Licenses.txt file under the Components directory of the source code).
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
frankcrowder



Joined: 04 Dec 2008
Posts: 7

PostPosted: Mon Dec 08, 2008 12:00 am    Post subject: webservices Reply with quote

Code:
"http://Infralution .com/webservices"

if I change the above in the code, the code stops working! I have the AuthenticationServer installed on a 'not local' server and the programs seem to work as long as I do not change the above.
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Mon Dec 08, 2008 7:51 pm    Post subject: Reply with quote

You mean this attribute on the Authentication Web Service:
Code:

[System.Web.Services.WebServiceBindingAttribute(Name = "AuthenticationServiceSoap", Namespace = "http://infralution.com/webservices")]


This merely defines a unique namespace for the webservice (the same as defining a namespace in normal code) - it is not a "real" address and if you try to visit it you will get a "Page Not Found" error. It is never actually contacted by the code.

The reason your code won't work if you change this is that the AuthenticationServer is compiled against the same definition. So if you change the webservice namespace, it is like changing namespace of an assembly used by another assembly. When your application contacts the webservice it checks that the web namespace the server gives matches what it is expecting. If you have the Authentication Server source code you can change this - but there is no real reason to.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
frankcrowder



Joined: 04 Dec 2008
Posts: 7

PostPosted: Mon Dec 08, 2008 9:30 pm    Post subject: thank you! Reply with quote

great support and qiuck answers. I am glade I found your site.

frank
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Infralution Support Forum Index -> Licensing Support All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group