04:09 <lvrp16> Hope you guys are doing OK with the hot weather in France. Time to hit the beach and get out of work early?

18:13 <repk> @narmstrong | afaerber: what’s the difference with https://github.com/repk/gxlimg tool ?? // I think the main difference is that it does support bl3enc and bootmk.

18:17 <repk> afaerber: I have pasted the link to gxlimg on this chan. Sorry if you missed that, maybe I should have contacted directly.

18:20 <vagrantc> one is licensed ambiguously, and the other licensed under a well-intentioned minimalist license that send lawyers into a rathole of possible infractions

18:21 <vagrantc> presuming you're comparing with meson-tools...

18:43 <repk> vagrantc: yes sorry, it is a shame but I do not really care about license as I should. One day I'll take my courage in my hands and compare about all the existing ones. In the meantime I do like beers.

18:45 <vagrantc> repk: yeah, don't particularly like them either, but also like to package software for distributions :)

18:46 <vagrantc> repk: yeah, encoding the appreciation for beer into a license is... tricky :)

18:58 <ukleinek> just an amendment of the GPL with an added paragraph "I like beer" sounds DFSG-free :-)

19:00 <repk> vagrantc: ok you win, I fixed that :).

19:09 <vagrantc> repk: yay!

19:11 <vagrantc> ukleinek: the problem with the beerware license is it includes clauses about actually buying the author a beer ... even though they're conditional, it introduces some ... challenges

19:11 <vagrantc> potential interpretations, etc.

19:11 <ukleinek> vagrantc: I'm aware of the problems, yeah.

19:17 <afaerber> repk, I got bl3enc working earlier today - took me a while to realize that somehow the first encrypted 0x200 bytes are moved to the end

19:18 <afaerber> so only bootmk and acs_tool remaining, hopefully

19:20 <repk> afaerber: yes this was a tricky thing to put the first 0x200 to the end

19:21 <afaerber> vagrantc, I thought I permitted you to use it with OpenSSL long ago - for SPDX I didn't find anything better than the OpenVPN exception

19:23 <afaerber> vagrantc, note that I am open to using any compatible library - surely this is not the only tool in Debian that uses crypto libraries, how do other tools handle it?

19:37 <vagrantc> afaerber: for GPLed projects, they either add an exception, or are removed

19:38 <vagrantc> afaerber: or, yeah, use gnutls or somethin

19:38 <vagrantc> but gnutls isn't a drop-in replacement

19:39 <vagrantc> afaerber: right, the OpenVPN exception is pretty much exactly right, except for the part about OpenVPN, Inc. being the grantee

19:40 <vagrantc> er, the ones making the assignment of additional rights above and beyond GPL

19:42 <vagrantc> afaerber: admittedly, i think there should be a generic one that basically does the same thing ... 389-exception was basically almost the same thing, although a little more verbose

19:44 <vagrantc> but both embedded the copyright holder's information, rather than "The authors and/or copyright holders additionally grant ..."