Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sun, 8 Jul 2012 10:29:05 -0400
From: Rich Rumble <>
Subject: Re: install types (was: John the Ripper 1.7.9-jumbo-6)

On Fri, Jul 6, 2012 at 11:16 PM, Solar Designer <> wrote:
> We don't currently have a native package for Windows.  All we have is a
> .zip archive.  As long as this is how we distribute John for Windows, I
> think it should use the current approach with doc and run directories.
A very simple "installer" is all that is needed.
> When we have a package with some kind of installer, I guess what we do
> may depend on the installer's capabilities.  Personally, I see little
> need to install JtR on Windows system-wide - on the contrary, I think
> installs local to the current account should be preferable - and in that
> case I see no benefit from separating the program and data.
I also see no reason for a system-wide install, and there is no reason
to even get very fancy with an installer, a SFX archive is probably
the best and easiest choice. 7zip has very good support for creating
SFX, and there are other FOSS installers we could use as well.
> Another issue is that on Windows Vista and newer, UAC may be getting in
> the way, unnecessarily making the installer run with administrator
> privileges.  I am not familiar with Windows at all, but from what I read
> a while ago this is triggered by typical installer filenames.  So we'd
> have to either avoid those or bite the bullet and maybe actually do
> system-wide installs.  What's the point in using administrator
> privileges along with making a user-local install?  Maybe there's some
> weird Windows reason for that combination?
As long as an installed program doesn't attempt to write to the
registry, or certain paths, nothing special needs done. If I create an
installer and make the default location for JtR non-system wide (don't
write to the "all users" profile/path) and instead use "my documents"
or some other "looser" permissioned path, no flags will be raised by
the OS/UAC. FireFox is a good example, even if you don't install
firefox with admin rights, you can install it, just not to c:\program
files... but just about anywhere else you choose, like ones desktop or
documents folder. This also prevents FF from being ones default
browser because the installer can't write to the registry, and FF
doesn't show up in "add remove programs", but I digress. I think a
simple SFX is all that is required, it can allow the user to install
where they see fit if a certain (yet to be determined) default
location doesn't suit their preference or perhaps their permission.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.