Hi all,
I'm having a heck of a time with what should be a simple bug.
http://trac.macosforge.org/projects/macports/ticket/13156
Several people have reported the same problem, but I cannot replicate
it on my MacBook Pro running Mac OS X 10.4.11. I have tested both
with and without the
On Dec 31, 2007, at 3:26 PM, Landon Fuller wrote:
But HTTP digest doesn't solve any of the problems that SSL solves:
- It is still vulnerable to a MITM attack. Your password is hashed,
but the hash is password-equivalent -- an attacker can simply
forward it on.
Not really... the server
Perhaps the port revision should also be incremented so that anyone
who had beta 3 installed will be informed of the availability of this
new beta 4?
On Jan 2, 2008, at 03:32, [EMAIL PROTECTED] wrote:
Revision: 32446
http://trac.macosforge.org/projects/macports/changeset/32446
On Jan 2, 2008, at 10:40, Kevin Van Vechten wrote:
On Dec 31, 2007, at 3:26 PM, Landon Fuller wrote:
But HTTP digest doesn't solve any of the problems that SSL solves:
- It is still vulnerable to a MITM attack. Your password is
hashed, but the hash is password-equivalent -- an attacker
On 1 Jan 2008, at 17:00, James Berry wrote:
Hi Ryan,
On Jan 1, 2008, at 12:56 PM, Ryan Schmidt wrote:
On Jan 1, 2008, at 11:09, [EMAIL PROTECTED] wrote:
Revision: 32441
http://trac.macosforge.org/projects/macports/changeset/
32441
Author: [EMAIL PROTECTED]
Date:
On Jan 2, 2008, at 12:37 PM, Landon Fuller wrote:
- Digest authentication is indistinguishable from Basic
authentication -- your browser will display the same dialog
regardless of the authentication type.
Safari distinguishes them; Basic authentication dialogs say the
password will be
I tried to compile the latest Deluge (a BitTorrent client) and XPN
(an experimental Python newsreader) after applying a workaround to
py25-gobject, py25-cairo, py25-gtk and dbus-python25, all of which
were reporting missing symbols under Leopard: the patches simply
exclude the option
Ryan Schmidt wrote:
Perhaps the port revision should also be incremented so that anyone
who had beta 3 installed will be informed of the availability of this
new beta 4?
Perhaps, but these -devel ports usally build from tip of trunk so they
all had revision 0...
--anders
On Jan 2, 2008, at 17:25, Anders F Björklund wrote:
Ryan Schmidt wrote:
Perhaps the port revision should also be incremented so that
anyone who had beta 3 installed will be informed of the
availability of this new beta 4?
Perhaps, but these -devel ports usally build from tip of trunk so
