Re: [tor-talk] which 3.0a4 package is for Windows

2013-10-09 Thread Moritz Bartl
On 10/09/2013 06:24 AM, Joe Btfsplk wrote:
 Except in this case, the file / package isn't an executable - it's a
 compressed archive.  The exe may be used here to indicate a Windows
 build, but it's just a zipped (.7z) file. 

It may contain a .7z archive and you may be able to open it using 7zip,
but it is still an executable, containing both the compressed archive as
well as an self-contained unpacker. (the jargon term is SFX,
self-extracting archive)

In the case of 3.0, it should even be a proper installer made with NSIS.
Did you actually try to run it?

 Technically, shouldn't the Windows packages have a compressed archive
 extension, like the other platforms?

You can't make it right for everyone. Most Windows users don't know how
to deal with archives, but do expect a wizard to guide them when they
double-click a file.

 Besides, emailing a Windows TBB package w/ .exe extension can create
 problems.  Why not call it what it is?

It is a proper Windows executable, not simply an archive.

Moritz
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk


Re: [tor-talk] which 3.0a4 package is for Windows

2013-10-09 Thread Sebastian G. bastik.tor
09.10.2013 06:24, Joe Btfsplk:
 On 10/8/2013 6:13 PM, Moritz Bartl wrote:
 Is there a reason even stable Win versions never reference the OS in
 file names?
 .exe is a Windows(-only) extension. I agree that the OS could be added
 to the file name to avoid confusion.

 Thanks, but a question / comment.
 Except in this case, the file / package isn't an executable - it's a
 compressed archive.

It's kind of both. You can install the bundle. The .exe can be
executed and asks for where to extract to and can optionally start the
bundle after extracting it.

It's also possible to extract the installer using 7zip (or another
extractor) and access it that way. (This applies to the relay bundle and
bridge bundle, too. They are installers and can be extracted using 7zip
or something else.)

 The exe may be used here to indicate a Windows
 build, but it's just a zipped (.7z) file.  I'm sure lots of new users
 are confused by the .exe, in spite of instructions.

Apparently users are confused all the time. They were confused about
simple archives one had to extract. They extracted it and did not know
what to do. Now it is an executable that unpacks the bundle and can
launch it.

This should be a lot easier to handle for most people.

 Technically, shouldn't the Windows packages have a compressed archive
 extension, like the other platforms?

They had, but users seemed confused.

 Besides, emailing a Windows TBB package w/ .exe extension can create
 problems.  Why not call it what it is?

Indeed, some security mechanism filer attachments based on extension.

I would get confused if something that can't be executed would have the
extension .exe and if that would be the case with TBB releases I would
also prefer to have a .zip file as it doesn't require third-party
software on modern windows, which as far as I can tell still does not
know how to handle .7z

I also would include the OS name in the bundle name if there would be
just archives or version for 64bit Windows, maybe one can do that anyway
to avoid confusion.

Regards,
Sebastian G.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk


Re: [tor-talk] which 3.0a4 package is for Windows

2013-10-09 Thread krishna e bera
On 13-10-09 04:00 AM, Sebastian G. bastik.tor wrote:
 09.10.2013 06:24, Joe Btfsplk:
 On 10/8/2013 6:13 PM, Moritz Bartl wrote:
 Is there a reason even stable Win versions never reference the OS in
 file names?
 .exe is a Windows(-only) extension. I agree that the OS could be added
 to the file name to avoid confusion.

 Thanks, but a question / comment.
 Except in this case, the file / package isn't an executable - it's a
 compressed archive.
 
 It's kind of both. You can install the bundle. The .exe can be
 executed and asks for where to extract to and can optionally start the
 bundle after extracting it.
 
 It's also possible to extract the installer using 7zip (or another
 extractor) and access it that way. (This applies to the relay bundle and
 bridge bundle, too. They are installers and can be extracted using 7zip
 or something else.)
 
 The exe may be used here to indicate a Windows
 build, but it's just a zipped (.7z) file.  I'm sure lots of new users
 are confused by the .exe, in spite of instructions.
 
 Apparently users are confused all the time. They were confused about
 simple archives one had to extract. They extracted it and did not know
 what to do. Now it is an executable that unpacks the bundle and can
 launch it.

If you want to prevent confusing Windows users, the installer should be
a .msi file which by default has the action Install associated with it
when they click.  It should also be signed in Microsoft's anointed way
so that there are no popup warnings about untrusted software.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk


[tor-talk] which 3.0a4 package is for Windows

2013-10-08 Thread Joe Btfsplk

Is the only set of installers that doesn't list an OS, the one for Windows?
https://archive.torproject.org/tor-package-archive/torbrowser/3.0a4/

Is there a reason even stable Win versions never reference the OS in 
file names?


Thanks.
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk


Re: [tor-talk] which 3.0a4 package is for Windows

2013-10-08 Thread Moritz Bartl
On 10/09/2013 01:07 AM, Joe Btfsplk wrote:
 Is the only set of installers that doesn't list an OS, the one for Windows?
 https://archive.torproject.org/tor-package-archive/torbrowser/3.0a4/

Yes.

 Is there a reason even stable Win versions never reference the OS in
 file names?

.exe is a Windows(-only) extension. I agree that the OS could be added
to the file name to avoid confusion.

-- Moritz
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk


Re: [tor-talk] which 3.0a4 package is for Windows

2013-10-08 Thread Joe Btfsplk

On 10/8/2013 6:13 PM, Moritz Bartl wrote:

Is there a reason even stable Win versions never reference the OS in
file names?

.exe is a Windows(-only) extension. I agree that the OS could be added
to the file name to avoid confusion.


Thanks, but a question / comment.
Except in this case, the file / package isn't an executable - it's a 
compressed archive.  The exe may be used here to indicate a Windows 
build, but it's just a zipped (.7z) file.  I'm sure lots of new users 
are confused by the .exe, in spite of instructions.


Technically, shouldn't the Windows packages have a compressed archive 
extension, like the other platforms?
Besides, emailing a Windows TBB package w/ .exe extension can create 
problems.  Why not call it what it is?

--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk