[PATCH v2 6/7] coreutils: Import from packages feed

[edgar.soldin at web.de]

On 08.01.2023 00:02, Thibaut wrote:
>
>
>> Le 7 janv. 2023 à 22:41, Robert Marko <robimarko at gmail.com> a écrit :
>>
>> On Sat, 7 Jan 2023 at 16:26, Thibaut VARÈNE <varenet at zigoo.net> wrote:
>>>
>>>
>>>
>>>> Le 7 janv. 2023 à 15:06, Christian Marangi <ansuelsmth at gmail.com> a écrit :
>>>>
>>>> On Fri, Jan 06, 2023 at 11:49:44PM -0800, Brian Norris wrote:
>>>>> I need to express a per-target dependency on the 'base64' utility, and
>>>>> that's seemingly impossible to do for busybox. Pull in coreutils to make
>>>>> that easier.
>>>>>
>>>>> Signed-off-by: Brian Norris <computersforpeace at gmail.com>
>>>>
>>>> We still need to think of a correct solution for this... coreutils is an
>>>> option but wonder if a better one is openssl... Actually we have a small
>>>> tool to handle specific decryption of some stuff... Wonder if that can
>>>> be expanded for this task and just use wolfssl or openssl api to decode
>>>> base64 stuff?
>>>
>>> Using one or the other would impose (i.e. (en)force) that SSL library on this particular target. Do we want this, especially considering the ongoing conversation about mbedTLS?
>>>
>>> Also pulling an entire SSL implementation just to decode base64 seems a tad overkill too.
>>
>> I agree on this one, forcing usage of OpenSSL isn't ideal, coreutils
>> is a better option for sure.
>
> There might be an even easier/lighter way (short of enabling base64 in busybox), AWK to the rescue:
> https://github.com/shane-kerr/AWK-base64decode
>
> The code is clean and judging by the comment line 97, works with busybox awk.

how is luci doing base64 en/decoding? that should be available in default images. if it's using lua, that should be available in every image even without web-interface or?

..ede