full-disclosure - Cookies marked as secure

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

Message-ID: <7d85153f0607111950w185e9bdbr99a1a016d173f6fa@mail.gmail.com>
Date: Wed Jul 12 03:50:27 2006
From: joshuaperrymon at gmail.com (Josh L. Perrymon)
Subject: Cookies marked as secure

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