[Mono-devel-list] FormsAuthentication [was: session_end Event (global.asax)]

[Bernhard Herzog]

Miguel, thank you very much for your answer. I have filed a few bug reports. 
The online problem I cannot reproduce right now is when aspx files get 
locked after editing on the fly on Windows... I will file it when it happens 
again. I am happy to support Mono any way I can.

I have another problem or question along these lines:
After login I call
FormsAuthentication.RedirectFromLoginPage(name.Value, 
PersistCookie.Checked);

So the user does not have to login again when checking "autologin". But 
isn't that a security problem? Because the password of the user isn't stored 
in the cookie so everybody could fake the username in a mono application? I 
have taken a look into the FormsAuthentication.cs and the ticket is not 
encrypted right now. Is there any plan to implement this?

//if (protection == FormsProtectionEnum.None)
   return GetHexString (allTicket.ToString ());
//TODO: encrypt and validate

BTW: Is there an easy way to compile System.Web.dll - i.e. is it all managed 
code?

Thanks again
Bernhard

----- Original Message ----- 
From: "Miguel de Icaza" <miguel at ximian.com>
To: "Bernhard Herzog" <schwimmlehrer at gmail.com>
Cc: <mono-devel-list at lists.ximian.com>
Sent: Friday, July 22, 2005 10:14 PM
Subject: Re: [Mono-devel-list] session_end Event (global.asax)


> Hello,
>
>> Is it generally a good idea to use Mono on Windows? I am seeing a lot of
>> problems, e.g.:
>> 1. "Some sort of w32 error occurred: 10053" when a socket client closes a
>> connection
>
> Do you have a way of reproducing this problem?
>
> The error in question is:
>
> An established connection was aborted by the software in your
> host machine.
>
>> 2. I cannot copy a dll into the bin-directory while XSP is running (i.e. 
>> hot
>> deployment does not work). Even on Linux I get a assertion failure in
>> loader.c
>
> Yes, this is because we currently do not implement a mechanism in which
> we copy the contents of the Bin directory elsewhere and use those, so
> those contents are "live".
>
> This is a difference in implementations, we should look into fixing this
> at some point.  Could you file a bug report please?
>
>> 3. When changing an aspx file sometimes the file gets locked and I cannot
>> edit it without restarting the XSP server
>
> Do you have more details about this problem?  How can we reproduce this?
>
>> Should I file these as Bugs or is the Windows implementation generally 
>> well
>> behind the Linux implementation?
>
> Filing bugs is the best way of getting these things fixed, and we will
> be happy to fix them.
>