Commit graph

12 commits

Author SHA1 Message Date
wiz
5d86518619 Switch github HOMEPAGEs to https. 2017-07-30 22:32:10 +00:00
taca
c7d7bc9648 Update ruby-bcrypt to 3.1.11.
3.1.11 Mar 06 2016
  - Add support for Ruby 2.2 in compiled Windows binaries
2016-03-15 15:07:02 +00:00
agc
5293710fb4 Add SHA512 digests for distfiles for security category
Problems found locating distfiles:
	Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
	Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
	Package libidea: missing distfile libidea-0.8.2b.tar.gz
	Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
	Package uvscan: missing distfile vlp4510e.tar.Z

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
2015-11-04 01:17:40 +00:00
taca
17a1a339eb Add ${GEM_EXTSDIR}/gem.build_complete for new rubygems and updated ruby. 2015-03-08 15:17:17 +00:00
taca
6f9a0726ec Update ruby-bcrypt to 3.1.10.
3.1.8  Oct 23 2014
  - Add support for Ruby 2.1 in compiled Windows binaries [GH #102]

3.1.9  Oct 23 2014
  - Rebuild corrupt binaries

3.1.10 Jan 28 2015
  - Fix issue with dumping a BCrypt::Password instance to YAML in Ruby 2.2 [GH #107 by @mattwildig]
2015-02-04 16:07:29 +00:00
taca
e6a83edd99 Update ruby-bcrypt to 3.1.7.
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
2014-03-14 17:53:12 +00:00
jperkin
9e7a1ba4b9 Set USE_GCC_RUNTIME=yes for packages which build shared libraries but do
not use libtool to do so.  This is required to correctly depend upon a
gcc runtime package (e.g. gcc47-libs) when using USE_PKGSRC_GCC_RUNTIME.
2014-03-13 11:08:49 +00:00
taca
5ab07c82b1 Update ruby-bcrypt to 3.1.2.
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
2013-09-15 14:56:11 +00:00
rodent
6b46c62d2e Edited DESCR in the case of:
File too long (should be no more than 24 lines).
 Line too long (should be no more than 80 characters).
 Trailing empty lines.
 Trailing white-space.
Trucated the long files as best as possible while preserving the most info
contained in them.
2013-04-07 20:49:31 +00:00
taca
c5a66ec5ef Update ruby-bcrypt package to 3.0.1.
3.0.1
  - create raises an exception if the cost is higher than 31. GH #27
2011-09-13 14:47:25 +00:00
taca
5af5a59075 Update ruby-bcrypt to 3.0.0.
3.0.0 Aug 24, 2011
  - Bcrypt C implementation replaced with a public domain implementation.
  - License changed to MIT
2011-08-25 15:31:01 +00:00
taca
a01d055a6d Importing ruby-bcrypt version 2.1.4 package.
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.
2011-06-19 03:17:32 +00:00