[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Minios-devel] [UNIKRAFT PATCH 0/3] Introduce posix-crypt internal library


  • To: Simon Kuenzer <simon.kuenzer@xxxxxxxxx>, minios-devel@xxxxxxxxxxxxx
  • From: Costin Lupu <costin.lupu@xxxxxxxxx>
  • Date: Wed, 27 Nov 2019 11:16:48 +0200
  • Delivery-date: Wed, 27 Nov 2019 09:17:17 +0000
  • Ironport-sdr: UENzGbpeXVa3ohdRpvN2jk8poAqBfjB58D1xtEHD+F7tA8EQu3GvfK0hg/EkDoYEhagpQAdRic FZ1NU/JPTjuw==
  • List-id: Mini-os development list <minios-devel.lists.xenproject.org>

On 11/27/19 10:43 AM, Simon Kuenzer wrote:
> Hey Costin,
> 
> thanks a lot for your work. Could you also add a message why providing
> `crypt` and `crypt_r` with the Unikraft base repo is needed? E.g., are
> there any common and shared modifications needed for supporting libc
> implementations or is there an internal direct dependency? If not, I
> prefer to avoid introducing us maintainance effort for copies of code
> that is usually provided with a libc. In the latter case I suggest to
> introduce posix-crypt as external library.

Hi Simon,

We need crypt/crypt_r with newlib which doesn't implement them. The
alternative would have been to put the code into newlib's glue code. But
then, what happens with other libc implementation which doesn't provide
crypt? We would have to copy it there as well, right?

With this approach I think the maintenance effort is reduced when adding
it into Unikraft. And I think it's even less effort compared with making
it external, which would have to be cloned separately. Btw, would crypt
have original code?

Cheers,
Costin

_______________________________________________
Minios-devel mailing list
Minios-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/minios-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.