From: brian avery <avery.brian@gmail.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Call csrf function in all pages to ensure cookie is sent
Date: Tue, 18 Aug 2015 15:32:42 -0700 [thread overview]
Message-ID: <cover.1439937065.git.avery.brian@gmail.com> (raw)
Simple addition of cross site request forgery protection to base page so it is inherited everywhere.
The following changes since commit c348fa50186fb0796bc7b793c4b8d710419f2a0d:
bitbake: toaster: move code from setup_lv_tests to setUp (2015-08-17 14:41:45 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib bavery/submit/michaelw/20150817_csrf_added_base
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/submit/michaelw/20150817_csrf_added_base
Michael Wood (1):
toastergui: Call csrf function in all pages to ensure cookie is sent
lib/toaster/toastergui/templates/base.html | 1 +
1 file changed, 1 insertion(+)
--
1.9.1
next reply other threads:[~2015-08-18 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 22:32 brian avery [this message]
2015-08-18 22:32 ` [PATCH 1/1] toastergui: Call csrf function in all pages to ensure cookie is sent brian avery
-- strict thread matches above, loose matches on Subject: below --
2015-08-18 22:10 [PATCH 0/1] " brian avery
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1439937065.git.avery.brian@gmail.com \
--to=avery.brian@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox