full-disclosure - SSL VPNs and security

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <9f08cff0606122213v1816479bm11f806d5edb4ead2@mail.gmail.com>
Date: Tue Jun 13 06:13:54 2006
From: qballus at gmail.com (Q-Ball)
Subject: SSL VPNs and security

SSL VPNs have their legitimate place as does IPSec. Personally, I'd rather
that travelling exec's who need to log on from a public Internet terminal,
dont have full IP connectivity into the network, but maybe that's just me.

Q-Ball

On 6/10/06, Tim <tim-security@...tinelchicken.org> wrote:
>
> > That depends on whether the solution tries to solve single-sign-on
> > problems as well.  If the vendor is trying to handle SSO in such an
> > environment, then they are probably using domain cookies.  The
> > problems are exactly the same as the ones Michal listed, plus some
> > additional ones specific to domain cookies.
>
> Right, that does make it difficult.  There's probably work arounds, but
> they may be browser-specific.  Wildcard cookies, cookies set to other
> origins, or somehow setting document.domain back to the base domain
> after the initial page load might help, but some would probably present
> the same problem.
>
> The web was never designed for complex application development.  At
> least, web standards aren't.  Use a real VPN.
>
> cheers,
> tim
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20060613/a6a811cc/attachment.html