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
| ||
|
Date: Fri Jun 9 15:23:42 2006 From: tim-security at sentinelchicken.org (Tim) Subject: SSL VPNs and security > 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
Powered by blists - more mailing lists