I am the current de-facto mantainer of the distribution, and I don't
see this changing anytime soon. I'll document it for the next release
so it's treated as an exposed method.
As for the salting mechanism, I'll consider it since it doesn't seem
to do much harm apart from minor namespace pollution... comments
anyone??
On 2/14/07, atsushi kobayashi <[EMAIL PROTECTED]> wrote:
Hi.
Thank you for the reply.
In the beginning
As for the name space pollution of digest method, it is.
->_get_digest_string is seemed the method of internal,
Therefore, digest method was prepared.
Should I use ->_get_digest_string directly on the application side?
How if the method name is changed if it is recommended to use it directly?
In the second place
key thing..
Isn't it secure or more to use the character string given by the
system together?
Though it is thought it is of course case by case.
Am I different though I want to use this module to encrypt the
password as a fundamental idea?
Regards.
2007/2/15, Guillermo Roditi <[EMAIL PROTECTED]>:
> ->digest seems a bit like namespace pollution, additionally, you can
> already do this via ->_get_digest_string so I am going to vote for nix
> on this one since you basically just wrapped one method with another
> one that has a shorter name. As for the key thing.. nix on that as
> well because I don't understand where you are going with it. Is this
> supposed to be some sort of salting mechanism?
>
>
> On 2/13/07, atsushi kobayashi <[EMAIL PROTECTED]> wrote:
> > Hi.ALL.
> >
> > I wrote DBIC::DigestColumns patch.
> >
> > This patch provide digest method and the character string can be
> > separately specified.
> > To want occasionally to use the character string specified on the
> > system side when the user's inputting it in Digest, this patch was
> > written.
> > For instance, password.
> > The purpose is to be able to check the password when logging it in
> > when whether digest method
> > was separately made is said.
> >
> > for example:
> >
> > my $member = $schema->resultset('Member')->search({login_id =>
> > $login_id})->first;
> > if ($member->password eq $member->digest($password)) {
> > # some process.
> > }
> >
> > Please deliberation it.
> >
> > Thanks.
> >
> > --
> > Atsushi Kobayashi (nekokak)
> >
> > _______________________________________________
> > List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
> > Wiki: http://dbix-class.shadowcatsystems.co.uk/
> > IRC: irc.perl.org#dbix-class
> > SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
> > Searchable Archive:
http://www.mail-archive.com/[email protected]/
> >
> >
>
> _______________________________________________
> List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
> Wiki: http://dbix-class.shadowcatsystems.co.uk/
> IRC: irc.perl.org#dbix-class
> SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
> Searchable Archive: http://www.mail-archive.com/[email protected]/
>
--
Atsushi Kobayashi
_______________________________________________
List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
Wiki: http://dbix-class.shadowcatsystems.co.uk/
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
Searchable Archive: http://www.mail-archive.com/[email protected]/
_______________________________________________
List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
Wiki: http://dbix-class.shadowcatsystems.co.uk/
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
Searchable Archive: http://www.mail-archive.com/[email protected]/
