ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
canvas-lms/gems/canvas_breach_mitigation
History
Landon Wilkins c5b5cc786d da licença part 53 
add consistent license headers to all source files

Change-Id: I405d2def01ad68c76533b9254983497485cd7073
Reviewed-on: https://gerrit.instructure.com/110160
Reviewed-by: Landon Wilkins <lwilkins@instructure.com>
Tested-by: Jenkins
Reviewed-by: Jon Jensen <jon@instructure.com>
Product-Review: Jon Jensen <jon@instructure.com>
QA-Review: Jon Jensen <jon@instructure.com>
 		2017-05-01 21:06:11 +00:00
..
lib da licença part 53 2017-05-01 21:06:11 +00:00
spec da licença part 53 2017-05-01 21:06:11 +00:00
.rspec convert breach migration plugin to proper gem and fix name 2014-01-30 22:55:31 +00:00
Gemfile bump simplecov, fixes SD-2056 2017-04-04 18:06:25 +00:00
LICENSE.txt da licença part 53 2017-05-01 21:06:11 +00:00
README.md convert breach migration plugin to proper gem and fix name 2014-01-30 22:55:31 +00:00
canvas_breach_mitigation.gemspec upgrade many canvas gems to rspec 3 syntax 2016-12-27 18:44:23 +00:00
test.sh simplify gem test harnesses 2016-01-19 17:52:58 +00:00

README.md

Canvas Breach Mitigation

This is a fork of the breach-mitigation-rails gem: http://rubygems.org/gems/breach-mitigation-rails

TODO: Ideally this should be replaced with the gem

Makes Rails applications less susceptible to the BREACH / CRIME attacks. See breachattack.com for details.

How it works

This implements one of the suggestion mitigation strategies from the paper:

Masking Secrets: The Rails CSRF token is 'masked' by encrypting it with a 32-byte one-time pad, and the pad and encrypted token are returned to the browser, instead of the "real" CSRF token. This only protects the CSRF token from an attacker; it does not protect other data on your pages (see the paper for details on this).

Warning!

BREACH and CRIME are complicated and wide-ranging attacks, and this gem offers only partial protection for Rails applications. If you're concerned about the security of your web app, you should review the BREACH paper and look for other, application-specific things you can do to prevent or mitigate this class of attacks.

Gotchas

  • If you have overridden the verified_request? method in your application (likely in ApplicationController) you may need to update it to be compatible with the secret masking code.