[Full-disclosure] Cookies marked as secure

["Josh L. Perrymon" <joshuaperrymon@xxxxxxxxx>]

Ok,

I'm having a discussion with a buddy about secure cookies. I'm looking
at a Java application that used several cookies after logging in;

 SessionID
 CookieIDtype
 FailMSGID

so on...

Obviously the application is using some code that performs additional
sessions on top of the standard sessionID.

What I'm seeing is that once I login to the app is that the SET
Cookie: Statement has /Secure marked.  However, all the client/server
traffic afterwards is NOT marked with /Secure.

I read the RFC and it says something like " HTTP Is stateless,
therefore all sensitive cookies sent over HTTPS should be marked as
/SECURE, so they are not passed over HTTP.

So my questions finally:
When needed a Cookie to be secure.. should it be marked as /SECURE in
client requests to the server OR can it be marked secure within the
physical cookie itself.. on the HD?

Confrused,

JP

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