Re: [WebDNA] Adding bcrypt as a encryption / hashing option

This WebDNA talk-list message is from

2017

It keeps the original formatting. numero = 113389
interpreted = N
texte = 982+1 on password hash.=20I have been getting away from WebDNA because of lack of support for =traditional databases... but I do like to see stuff like this.=20DonovanOn Jan 18, 2017, at 3:32 AM, Tom Duke wrote:> Chris,>=20> Hi - that's great.>=20> It might be worth considering adding a WebDNA context for password =hashing that implements current best practice. Something like the ="password_hash" PHP function:>=20> http://php.net/manual/en/function.password-hash.php>=20> Then as things change new algorithms / hash options could be added to =the context. Its would help with security audits to be able to show =that we are implementing standard hashing methods.>=20> - Tom>=20>=20>=20>=20>=20> On 18 January 2017 at 07:43, wrote:> Hello Tom! Yes, it is on our to-do list. It is based on blowfish, =which is already implemented in Webdna 8.x>=20> - chris=20>=20>=20>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us. Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Adding bcrypt as a encryption / hashing option (Donovan Brooke 2017)
Re: [WebDNA] Adding bcrypt as a encryption / hashing option (Tom Duke 2017)
Re: [WebDNA] Adding bcrypt as a encryption / hashing option (christophe.billiottet@webdna.us 2017)
[WebDNA] Adding bcrypt as a encryption / hashing option (Tom Duke 2017)

982+1 on password hash.=20I have been getting away from WebDNA because of lack of support for =traditional databases... but I do like to see stuff like this.=20DonovanOn Jan 18, 2017, at 3:32 AM, Tom Duke wrote:> Chris,>=20> Hi - that's great.>=20> It might be worth considering adding a WebDNA context for password =hashing that implements current best practice. Something like the ="password_hash" PHP function:>=20> http://php.net/manual/en/function.password-hash.php>=20> Then as things change new algorithms / hash options could be added to =the context. Its would help with security audits to be able to show =that we are implementing standard hashing methods.>=20> - Tom>=20>=20>=20>=20>=20> On 18 January 2017 at 07:43, wrote:> Hello Tom! Yes, it is on our to-do list. It is based on blowfish, =which is already implemented in Webdna 8.x>=20> - chris=20>=20>=20>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us. Donovan Brooke

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] Adding bcrypt as a encryption / hashing option

2017

Top Articles:

Related Readings: