bugtraq - Re: At long last -- Extra Outlooks!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 11 Jan 2008 16:23:13 -0500
From: Francois Labreque <flabreq@...ibm.com>
To: bugtraq@...urityfocus.com
Subject: Re: At long last -- Extra Outlooks!

Alexander Bochmann <ab@...ts.gxis.de> a écrit sur 2008-01-11 12:42:00 :

> ...on Thu, Jan 10, 2008 at 10:28:34PM -0800, Thor (Hammer of God) wrote:
> 
>  > it turns out, Outlook is doing nothing close to what I feared.
>  > Basically, the second instance sees that another Outlook window is
>  > running in the same interactive logon space, and when it starts, it 
just
>  > calls another popup in the previous Outlook space and then terminates
>  > itself (that's close enough, anyway). The good news is that there is 
no
>  > "user hopping" or "boundary crossing" here. 
> 
> Sounds comparable to what the Windows Explorer does when 
> it is not expicitly set to run as a separate process (or 
> started with the /separate switch).
> 
> Is there some design principle behind this kind of behaviour?
> 
> Alex.
> 

At least since Windows 3.0, whenever an application starts, it gets a 
reference to the previous (if any) instance of the app running on the 
system.  There are many applications that will simply exit with a message 
saying "Fropboz.exe is already running".

It doesn't answer your question as to WHY the functionality is there, or 
why the Outlook programmers thought about using it that way, but it's 
hardly something new.