Full Disclosure mailing list archives

Re: Secure OWA


From: "Lohan Spies" <lohan.spies () gmail com>
Date: Thu, 31 Aug 2006 09:03:03 +0200

thanks for all the replies and solutions mentioned.

My actual need will be to allow users to login via OTP to exchange with a
SSO solution that will handle the domain username and password. (Or disable
the domain username and password authentication for exchange in some way, so
that they only use the OTP?)

The reason for this is because all users use smartcards to login on the
internal network and RAS etc.

But when they are away and need to use a public computer to access their
email via OWA, they would need some OTP because the public computer won't
have a smartcard reader for instance.

I thought about using OTP with an AAA server and SSO solution for auth? Any
suggestions of proven implemented products that could do the trick?


On 8/30/06, Fetch, Brandon <BFetch () texpac com> wrote:

Hijack:

So AOL doesn't play nice with IETF protocol standards?

*mock alarm*

NEVER!?

Sounds like a throwback to their old days of being the Internet's nanny
for the world.

"Let's 'cleanse' this data for you so as not to be offended based upon
your parental filters..."

I suppose we should be happy they're continuing their ways...

Brandon

-----Original Message-----
From: full-disclosure-bounces () lists grok org uk
[mailto:full-disclosure-bounces () lists grok org uk] On Behalf Of Brian
Eaton
Sent: Wednesday, August 30, 2006 4:15 PM
To: Mark Senior
Cc: full-disclosure () lists grok org uk
Subject: Re: [Full-disclosure] Secure OWA

On 8/30/06, Mark Senior <senatorfrog () gmail com> wrote:
> I think a possibly better approach, although it doesn't seem like you
> could implement it quite as simply as account lockouts, would be to
> lock out, not the account, but the originating IP address, for a
> duration.

Ever since I read this thread
(http://vegan.net/lb/archive/08-2004/0118.html) on one of the
load-balancer discussion lists I've been skeptical of using IP
addresses for much of anything.  My guess is that if you do things
like ban IPs automatically you run the risk of accidentally locking
out thousands of legit users as well as the one who is misbehaving.

A few of the more interesting comments in the thread:

"...myriad of enterprise networks that load-balance outbound client
connections across proxy servers which are connected to different
ISPs, with totally different source IP..."

"...The AOL client does a split tunnel type thing, where the HTTP gets
tunneled through the UDP conversation to AOL's network and back out
the proxies to the Internet, but the HTTPS (and other stuff) goes
directly from client to server..."

Regards,
Brian

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/


This message is intended only for the person(s) to which it is addressed
and may contain privileged, confidential and/or insider information.
If you have received this communication in error, please notify us
immediately by replying to the message and deleting it from your computer.
Any disclosure, copying, distribution, or the taking of any action
concerning
the contents of this message and any attachment(s) by anyone other
than the named recipient(s) is strictly prohibited.


_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/




--
Lohan Spies
083 258 2698
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Current thread: