<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If it helps, we decided to give those spokes (only those initiated
FROM the OP) the choice of how we frame their site in a browser child, post SSO.
They can chose to have it with without location bar, among other frame setup variables
provided by IE/msft. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The nature of websso is of course such that the spoke/consumer site
can use that new frame (which could now be address bar-less) to ping the IDP/OP
again - using SAML/openidauth – whose UI would appear now in that frame.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We failed to make sense of IE7+ tabs (using only javascript),
which seemed like a promising compromise - but which didn’t work out. Perhaps
others made tabs work, viably(without exploiting custom activeX downloads,
controlling tabbing)?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> general-bounces@openid.net
[mailto:general-bounces@openid.net] <b>On Behalf Of </b>Andrew Arnott<br>
<b>Sent:</b> Wednesday, October 22, 2008 8:47 AM<br>
<b>To:</b> Praveen Alavilli<br>
<b>Cc:</b> OpenID List<br>
<b>Subject:</b> Re: [OpenID] Security related Use Cases?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>A real hacker wouldn't. But the
fact that legitimate sites <i>can</i> do it means that some will likely do
it. If legitimate sites embed the Yahoo sign-in page in an iframe, thus
hiding the <a href="http://yahoo.com">yahoo.com</a> from the location bar,
users will become desensitized from not seeing <a href="http://yahoo.com">yahoo.com</a>
when they enter their credentials. This will make the phishers job that
much easier.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Wed, Oct 22, 2008 at 8:33 AM, Praveen Alavilli <<a
href="mailto:AlavilliPraveen@aol.com">AlavilliPraveen@aol.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>But why would a hacker open the real yahoo sign in page in
an iframe<br>
(security enabled or not) - there is nothing to gain from it (whether it<br>
shows the signin seal or not). Instead they are better of showing their<br>
own phishing page to steal the credentials.<br>
<span style='color:#888888'><br>
- Praveen</span><o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
Breno de Medeiros wrote:<br>
> On Tue, Oct 21, 2008 at 6:03 PM, Allen Tom <<a
href="mailto:atom@yahoo-inc.com">atom@yahoo-inc.com</a>> wrote:<br>
><br>
>> Hi Breno,<br>
>><br>
>> Do you have a demo of this?<br>
>><br>
><br>
> I could put one together, the directions are here:<br>
><br>
> <a href="http://msdn.microsoft.com/en-us/library/ms534622%28VS.85%29.aspx"
target="_blank">http://msdn.microsoft.com/en-us/library/ms534622(VS.85).aspx</a><br>
><br>
><br>
>> Thanks<br>
>> Allen<br>
>><br>
>><br>
>> Breno de Medeiros wrote:<br>
>><br>
>>> IE allows you to create an iframe and disable JS inside the
iframe.<br>
>>> 70-85% of users will be vulnerable to this attack.<br>
>>><br>
>>><br>
>>><br>
>><br>
><br>
><br>
><br>
><o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>