Creating an Installer for the Dnet Client

[striker64]

The other day, I was thinking how much of a pain in the ass it is to get family and friends to install the client and configure all the settings, so I had a great idea to make an installer with all the settings pre-set.

So, in about 10 minutes I whipped up a 1.3MB installer using InstallShield Pro 6.2 and it works beautifully, it even has the TA banner as a splash screen when it's uncompressing the files. All I did was configure the client with all the settings I want (email address, RC5 only, teamanandtech.com proxy, etc.), then I copied those files to a directory and added those files to the installer. Then I made the installer create a shortcut in the startup menu with the the -quiet switch and voila, all that is required for people to install it is virtually one click!

I was wondering if anyone knows if there are any legal ramifications with this, i.e. does dnet not permit it or something like that? I can't really see the harm if it's for friends and family, esp since there is no profit involved.

Anyway, something like this would be great for you big ass laminators as well! I'm sure it would make denil's new 80 Celeron benefactor's life a lot easier

 

[Adul]

Dunno if it is legal or not. We are not selling it for a profit. I did the same thing myself for the naked crackers. I even gave the options to install has a service or not.

 

[phule]

http://www.distributed.net/legal/policy.html

Those are all the official policies for dnet client usage.

I don't think the installer would be a problem provided:
ALL (and that means every single last one of them) is a legal install. You do not install on machines that you don't own or don't have permission from the highest persons at your location. This INCLUDES not violating ANY proper usage policy. It does not matter if your sys admin tells you it's ok if the corp or edu policy says you can't.

As for the "sale" of such an installer, I believe that would be a violation as well, but the dnet policy page doesn't go into detail over it.

On the other hand, if you could tailor that installer so that you can prompt a user to enter in their own info, (email address especially), perhaps dnet would be interested in using the software for the win32 installer distribution of the client from the dnet pages.

just some thoughts.

 

[Ken g6]

It's the note on the client download page that worries me more:

important note
This is the official listing of distributed.net clients. They have been tested to be functioning correctly. The binaries listed here are the ONLY ones you should be using. Trojan horses and other perverted versions have been known to have been circulated. Please do not make attempts to mirror or redistribute the client binaries, either via your own web/ftp server or other means. If you wish to provide a convenient method for your visitors to download clients, please provide a link to it on our FTP site or (preferably) to this page.

 

[Xede]

I don't think using an installer so family and friends can more easily crack for you really falls under what is intended by "mirroring or redistributing" the client.

 

[phule]

I agree with Xede. Using a home-made installer for your own needs (computers at work or family members) is one thing, but to distribute this online to anyone and everyone is another completely.

 

[Adul]

I use mine for our team member to more easily assimilate computers.

 

[ViRGE]

Moose has said something before, though we hven't heard much from him lately. Would something like this be OK man, or is it still on Dnet's no-nos?

 

[ZapZilla]

Non-DNet installers would be ripe for infection and foul play:

the more widespread the installer, the greater the risk of infection.

Is there a way to 100% guarantee the wholesomeness of a public non-DNet installer?

I think not, thus, DNet's wise policy.

 

[ElFenix]

i wouldn't consider the sort of uses striker has in mind as "public"

 

[JonB]

Striker64, I've been through many discussions about installers. As long as you are not releasing your new "install.exe" for distribution, you will be allright. The TeamAnandtech Borg mini-team (TA Cube) has something similar and haven't had problems. Keep some controls on the release and you'll be just fine (plus, you'll be putting together a smokin' herd).