pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2015-03-08	Add ${GEM_EXTSDIR}/gem.build_complete for new rubygems and updated ruby.	taca	1	-1/+2

2014-03-14	Update ruby-bcrypt to 3.1.7.	taca	1	-2/+3
	3.1.3 Feb 21 2014 - Add support for Ruby 2.1 in compiled Windows binaries - Rename gem from "bcrypt-ruby" to just "bcrypt". [GH #86 by @sferik] 3.1.6 Feb 21 2014 - Dummy version of "bcrypt-ruby" needed a couple version bumps to fix some bugs. It felt wrong to have that at a higher version than the real gem, so the real gem is getting bumped to 3.1.6. 3.1.7 Feb 24 2014 - Rebuild corrupt Java binary version of gem [GH #90] - The 2.1 support for Windows binaries alleged in 3.1.3 was a lie -- documentation removed
2013-09-15	Update ruby-bcrypt to 3.1.2.	taca	1	-2/+6
	3.1.0 May 07 2013 - Add BCrypt::Password.valid_hash?(str) to check if a string is a valid bcrypt password hash - BCrypt::Password cost should be set to DEFAULT_COST if nil - Add BCrypt::Engine.cost attribute for getting/setting a default cost externally 3.1.1 Jul 10 2013 - Remove support for Ruby 1.8 in compiled win32 binaries 3.1.2 Aug 26 2013 - Add support for Ruby 1.8 and 2.0 (in addition to 1.9) in compiled Windows binaries - Add support for 64-bit Windows
2011-08-25	Update ruby-bcrypt to 3.0.0.	taca	1	-6/+10
	3.0.0 Aug 24, 2011 - Bcrypt C implementation replaced with a public domain implementation. - License changed to MIT
2011-06-19	Importing ruby-bcrypt version 2.1.4 package.	taca	1	-0/+24
	bcrypt() is a sophisticated and secure hash algorithm designed by The OpenBSD project for hashing passwords. bcrypt-ruby provides a simple, humane wrapper for safely handling passwords. = bcrypt-ruby An easy way to keep your users' passwords secure. * http://bcrypt-ruby.rubyforge.org/ * http://github.com/codahale/bcrypt-ruby/tree/master == Why you should use bcrypt If you store user passwords in the clear, then an attacker who steals a copy of your database has a giant list of emails and passwords. Some of your users will only have one password -- for their email account, for their banking account, for your application. A simple hack could escalate into massive identity theft. It's your responsibility as a web developer to make your web application secure -- blaming your users for not being security experts is not a professional response to risk. bcrypt allows you to easily harden your application against these kinds of attacks.