[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2022-08-28T05:13:33Z 2022-08-28T05:13:33Z taca taca@pkgsrc.org 2022-08-28T05:13:33Z urn:sha1:cc3b045302fe83f8a42f2a2ca8a8c019d148ee76 3.1.17 (2022-05-14) * Unlock GVL when calculating hashes and salts [GH #260] * Fix compilation warnings in `ext/mri/bcrypt_ext.c` [GH #261] 3.1.18 (2022-05-16) * Fix regex in validators to use \A and \z instead of ^ and $ [GH #121] * Truncate secrets greater than 72 bytes in hash_secret [GH #255] * Assorted test and doc improvements 2020-09-14T14:02:14Z taca taca@pkgsrc.org 2020-09-14T14:02:14Z urn:sha1:ea2d2a13dfbbe5506b6c4feaf286f125f96a5412 Update ruby-bcrypt package to 3.1.16. 3.1.16 Sep 3 2020 - Fix compilation on FreeBSD. [GH #234] 3.1.15 July 21 2020 - Remove GVL optimization. Apparently it breaks things [GH #230] 3.1.14 July 21 2020 - Start calibration from the minimum cost supported by the algorithm [GH #206 by @sergey-alekseev] 2020-03-24T15:48:52Z taca taca@pkgsrc.org 2020-03-24T15:48:52Z urn:sha1:9b419594701875e8633c4416b7bc5540eee08470 Update ruby-bcrypt to 3.1.13. pkgsrc change: correct HOMEPAGE. 3.1.13 May 31 2019 - No longer include compiled binaries for Windows. See GH #173. - Update C and Java implementations to latest versions [GH #182 by @fonica] - Bump default cost to 12 [GH #181 by @bdewater] - Remove explicit support for Rubies 1.8 and 1.9 - Define SKIP_GNU token when building extension (Fixes FreeBSD >= 12) [GH #189 by @adam12] 2018-09-23T16:05:28Z taca taca@pkgsrc.org 2018-09-23T16:05:28Z urn:sha1:cefeee485357e1ddc67c42e38e76357abe9863f7 3.1.12 May 16 2018 - Add support for Ruby 2.3, 2.4, and 2.5 in compiled Windows binaries - Fix compatibility with libxcrypt [GH #164 by @besser82] 2015-03-08T15:17:17Z taca taca@pkgsrc.org 2015-03-08T15:17:17Z urn:sha1:7dfc8b21a2896248435e1a88ae6fc61d0cf72c92 2014-03-14T17:53:12Z taca taca@pkgsrc.org 2014-03-14T17:53:12Z urn:sha1:2587575b3be6a3f0032f15615fafe64ab7c4e09c 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-15T14:56:11Z taca taca@pkgsrc.org 2013-09-15T14:56:11Z urn:sha1:df107c98157978adf5ab9a9d718e4f26fd5b3c6b 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-25T15:31:01Z taca taca@pkgsrc.org 2011-08-25T15:31:01Z urn:sha1:6a6a581385d5c1965bd50178a83138e237b35257 3.0.0 Aug 24, 2011 - Bcrypt C implementation replaced with a public domain implementation. - License changed to MIT 2011-06-19T03:17:32Z taca taca@pkgsrc.org 2011-06-19T03:17:32Z urn:sha1:a0f7696ce6a8687d6e565295941164097cdc85d5 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.