Re: bcrypt

2016-09-20 Thread Mike Pechkin
> Can you make the rounds (cost factor) available as a parameter (perhaps as
> a global) ?
>
That would be quite important to use the library correctly.
>


Default rounds:
o) golang - 10
o) pybcrypt - 12
o) openbsd root - 9
o) openbsd user - 8

Implementation was already "broken":
o) no base64
o) no rounds
o) no compatibility with others implementations
o) lists only

Its so simple to change (increase?) hard-coded value and go forward.
User dont want *store* and pass rounds to function.
The only correct way to *use* library is to implement all himself.

Mike


Re: bcrypt

2016-09-19 Thread Joe Bogner
perfect, thanks!

On Mon, Sep 19, 2016 at 9:03 AM, Mike Pechkin <mike.pech...@gmail.com>
wrote:

>
> all under CC0.
> you are free to do you want.
>
> On Mon, Sep 19, 2016 at 3:12 PM, Joe Bogner <joebog...@gmail.com> wrote:
>
>> Mike, this looks great. What license covers this work - I see CC0 in the
>> root LICENSE[1] but didn't want to assume? Can I redistribute the source
>> with my example app?
>>
>> [1] - https://bitbucket.org/mihailp/tankfeeder/src/f9ad69ad2a6ec35
>> 941f50c4ec1160e7a53ea3e67/LICENSE?at=default=file-view-default
>>
>> On Sun, Sep 18, 2016 at 9:00 AM, Alexander Burger <a...@software-lab.de>
>> wrote:
>>
>>> Hi Mike,
>>>
>>> > bcrypt is ready
>>>
>>> Cool! Thank you!
>>> ♪♫ Alex
>>> --
>>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>>
>>
>>
>


Re: bcrypt

2016-09-19 Thread Mike Pechkin
all under CC0.
you are free to do you want.

On Mon, Sep 19, 2016 at 3:12 PM, Joe Bogner <joebog...@gmail.com> wrote:

> Mike, this looks great. What license covers this work - I see CC0 in the
> root LICENSE[1] but didn't want to assume? Can I redistribute the source
> with my example app?
>
> [1] - https://bitbucket.org/mihailp/tankfeeder/src/
> f9ad69ad2a6ec35941f50c4ec1160e7a53ea3e67/LICENSE?at=default&
> fileviewer=file-view-default
>
> On Sun, Sep 18, 2016 at 9:00 AM, Alexander Burger <a...@software-lab.de>
> wrote:
>
>> Hi Mike,
>>
>> > bcrypt is ready
>>
>> Cool! Thank you!
>> ♪♫ Alex
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>


Re: bcrypt

2016-09-19 Thread Joe Bogner
Mike, this looks great. What license covers this work - I see CC0 in the
root LICENSE[1] but didn't want to assume? Can I redistribute the source
with my example app?

[1] -
https://bitbucket.org/mihailp/tankfeeder/src/f9ad69ad2a6ec35941f50c4ec1160e7a53ea3e67/LICENSE?at=default=file-view-default

On Sun, Sep 18, 2016 at 9:00 AM, Alexander Burger <a...@software-lab.de>
wrote:

> Hi Mike,
>
> > bcrypt is ready
>
> Cool! Thank you!
> ♪♫ Alex
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>


Re: bcrypt

2016-09-18 Thread Alexander Burger
Hi Mike,

> bcrypt is ready

Cool! Thank you!
♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe


bcrypt

2016-09-18 Thread Mike Pechkin
hi,

bcrypt is ready
https://bitbucket.org/mihailp/tankfeeder/src/f9ad69ad2a6ec35941f50c4ec1160e7a53ea3e67/crypto/?at=default

1. new blowfish implementation, on "Vars". Pass original test vectors
2. implementation itself comparable to golang's bcrypt results
3. without base64 support, input-output lists only
4. hardcoded 8 rounds
5. to generate password and store it do:
(bcrypt (mapcar char (chop "qwerty123")))
it returns lists form: ((HASH) (SALT))
6. to check password entered do:
(=
   HASH
   (bcrypt (mapcar char (chop FROMUSER)) SALT) )
6. in general i trust all above

Mike


A bcrypt library for PicoLisp

2015-03-17 Thread Alexander Williams
Hi all,

I've cooked up yet another library for everyone to enjoy. This time it's
for bcrypt hashing:

  https://github.com/aw/picolisp-bcrypt

I haven't written an EXPLAIN.MD though, because the code is so brief and
doesn't really introduce anything new.

This was written as per someone's request on IRC (beneroth?), and it turns
out I needed it as well.

As usual, let me know your comments/suggestions.

Thanks!


Re: A bcrypt library for PicoLisp

2015-03-17 Thread Alexander Williams
Hi Jon,

I'm using Mac OS X, but for PicoLisp dev it's just SSH to an AWS instance
running 64-bit Debian 7.

Sometimes I'll use a virtualbox VM locally if I don't have internet access,
but it's too slow for regular use.


On Tue, Mar 17, 2015 at 9:25 AM, Jon Kleiser jon.klei...@fsat.no wrote:

 Hi Alexander W.,

 I’m just curious about what kind of development system you’re using. From
 the screen dump in the picolisp-bcrypt/README.md it seems that you are
 using some kind of Mac OSX, but at the same time the README.md says that
 “PicoLisp 64-bit v3.1.9+” is required. Are you using Docker?

 /Jon

 On 17. Mar, 2015, at 09:52, Alexander Williams a...@unscramble.co.jp
 wrote:

  Hi all,
 
  I've cooked up yet another library for everyone to enjoy. This time it's
 for bcrypt hashing:
 
https://github.com/aw/picolisp-bcrypt
 
  I haven't written an EXPLAIN.MD though, because the code is so brief
 and doesn't really introduce anything new.
 
  This was written as per someone's request on IRC (beneroth?), and it
 turns out I needed it as well.
 
  As usual, let me know your comments/suggestions.
 
  Thanks!

 --
 UNSUBSCRIBE: mailto:picolisp@software-lab.de?subjectUnsubscribe



Re: A bcrypt library for PicoLisp

2015-03-17 Thread Jon Kleiser
Hi Alexander W.,

I’m just curious about what kind of development system you’re using. From the 
screen dump in the picolisp-bcrypt/README.md it seems that you are using some 
kind of Mac OSX, but at the same time the README.md says that “PicoLisp 64-bit 
v3.1.9+” is required. Are you using Docker?

/Jon

On 17. Mar, 2015, at 09:52, Alexander Williams a...@unscramble.co.jp wrote:

 Hi all,
 
 I've cooked up yet another library for everyone to enjoy. This time it's for 
 bcrypt hashing:
 
   https://github.com/aw/picolisp-bcrypt
 
 I haven't written an EXPLAIN.MD though, because the code is so brief and 
 doesn't really introduce anything new.
 
 This was written as per someone's request on IRC (beneroth?), and it turns 
 out I needed it as well.
 
 As usual, let me know your comments/suggestions.
 
 Thanks!

--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe