Hi Jon,
OK, so for now I moved "-lcrypt" flag to a Makefile variable LCRYPT, and
assigned "-lcrypto" for Darwin and the BSD family.
Though it doesn't give strong encryption at the moment, at least it
compiles and is better than nothing ;-)
♪♫ Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de
Hi Alex,
> Hi Jon,
>
>> $ ./pil lib/adm.l +
>> : (de *Salt 16 . "$6$@1$")
>> -> *Salt
>> : (passwd "somestring")
>> -> "$6bsuufIMFxJE"
>>
>> So it seems that the 'passwd' function is working in 32-bit PicoLisp on
>> Mac, right?
>
> Hmm, yes and no ...
>
> It works, but obviously only with the (wor
Hi Jon,
> $ ./pil lib/adm.l +
> : (de *Salt 16 . "$6$@1$")
> -> *Salt
> : (passwd "somestring")
> -> "$6bsuufIMFxJE"
>
> So it seems that the 'passwd' function is working in 32-bit PicoLisp on
> Mac, right?
Hmm, yes and no ...
It works, but obviously only with the (worthless) DES algorithm, bec
Hi Alex,
> Hi Jon,
>
>> >The big question is: Did it only help to *build* it, or does it also
>> >*work* (i.e. does the 'passwd' function function return an encrypted
>> >password if '*Salt' is set, see my previous mail)?
>> >
>> >?? Alex
>>
>> Can I test this 'passwd' function in 32-bit PicoLisp?
On Mon, May 27, 2013 at 11:06:43AM +0200, Alexander Burger wrote:
> On failure (for example, if it is the wrong crypt library), you should
> get an error message about undefined 'ext:Crypt'.
Both versions (i.e. 'ext:Crypt' in pil32 or the native call to crypt()
in pil64) call the same library func
Hi Jon,
> >The big question is: Did it only help to *build* it, or does it also
> >*work* (i.e. does the 'passwd' function function return an encrypted
> >password if '*Salt' is set, see my previous mail)?
> >
> >♪♫ Alex
>
> Can I test this 'passwd' function in 32-bit PicoLisp? (I may not
> find
Hi Alex,
On 27-05-13 07:42 , Alexander Burger wrote:
Hi Jon,
current scr/Makefile. Adding the "o" to make it "-lcrypto" helped me
build 32-bit PicoLisp, v. 3.1.2.9 C (on Mac OS X 10.8.3).
The big question is: Did it only help to *build* it, or does it also
*work* (i.e. does the 'passwd' funct
Hi Jon,
> current scr/Makefile. Adding the "o" to make it "-lcrypto" helped me
> build 32-bit PicoLisp, v. 3.1.2.9 C (on Mac OS X 10.8.3).
The big question is: Did it only help to *build* it, or does it also
*work* (i.e. does the 'passwd' function function return an encrypted
password if '*Salt'
On Fri, May 24, 2013 at 04:11:54PM +0200, Alexander Burger wrote:
> Hi Jon,
>
> > I believe there is a missing "o" at the end of line 104 in the
> > current scr/Makefile. Adding the "o" to make it "-lcrypto" helped me
> > build 32-bit PicoLisp, v. 3.1.2.9 C (on Mac OS X 10.8.3).
>
> Under Linux i
On May 24, 2013, at 4:11 PM, Alexander Burger wrote:
> Hi Jon,
>
>> I believe there is a missing "o" at the end of line 104 in the
>> current scr/Makefile. Adding the "o" to make it "-lcrypto" helped me
>> build 32-bit PicoLisp, v. 3.1.2.9 C (on Mac OS X 10.8.3).
>
> Under Linux it is "-lcrypt
On Fri, May 24, 2013 at 10:11 PM, Alexander Burger wrote:
> Does anybody know the difference between libcrypt.so and libcrypto.so?
i don't know whats the difference, but what's common is that neither
of them are written in picolisp... ;)
--
tom
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de
Hi Jon,
> I believe there is a missing "o" at the end of line 104 in the
> current scr/Makefile. Adding the "o" to make it "-lcrypto" helped me
> build 32-bit PicoLisp, v. 3.1.2.9 C (on Mac OS X 10.8.3).
Under Linux it is "-lcrypt" (according to the man page of crypt(3)).
Seems we must make src/M
Hi,
I believe there is a missing "o" at the end of line 104 in the current
scr/Makefile. Adding the "o" to make it "-lcrypto" helped me build
32-bit PicoLisp, v. 3.1.2.9 C (on Mac OS X 10.8.3).
/Jon
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
13 matches
Mail list logo
