On 16.04.20 19:54, Jeffrey Walton wrote:
> On Thu, Apr 16, 2020 at 12:50 PM Aapo Talvensaari
> wrote:
>>
>> On Thu, Apr 16, 2020 at 12:44 AM Jeffrey Walton wrote:
>>> ...
>> I agree with Tim. If project is of any importance, as I think Nettle is,
>> there is no
>> problem in finding a new
On 16.04.20 09:58, Jeffrey Walton wrote:
> On Thu, Apr 16, 2020 at 3:34 AM Niels Möller wrote:
>>
>> Jeffrey Walton writes:
>>
>>> Does Nettle have backup maintainers? If so, can you name them and
>>> provide their public keys in case something happens to Niels.
>>
>> I don't think the current
On 4/3/20 10:29 AM, Jeffrey Walton wrote:
On Tue, Mar 31, 2020 at 7:42 AM Jeffrey Walton wrote:
On Mon, Mar 30, 2020 at 7:23 AM Niels Möller wrote:
I committed a change to update nettle version numbers, which implies a
new symbol version for internal symbols.
That seems to break the
On 4/2/20 8:03 AM, Niels Möller wrote:
ni...@lysator.liu.se (Niels Möller) writes:
Nikos Mavrogiannopoulos writes:
We may want to install nettle somewhere separately and instruct gnutls
to use it from there rather than the default locations.
That seems to be the right solution to the
On 1/15/20 9:24 AM, Nikos Mavrogiannopoulos wrote:
> On Wed, Jan 15, 2020 at 7:18 AM Niels Möller wrote:
>
>>> If they are you should be able to see them in Settings -> CI/CD -> Runners.
>>
>> I've now had a look. There's a section for "Group runners", which is
>> empty. No mention of "shared
On 11/25/19 12:58 PM, Nikos Mavrogiannopoulos wrote:
> On Sun, Nov 24, 2019 at 4:43 PM Tim Rühsen wrote:
>>
>> Hi Niels,
>>
>> since a while (max a few weeks), I see sporadic failures when cloning
>> nettle.
>>
>> E.g. when building nettle on the OSS
Hi Niels,
since a while (max a few weeks), I see sporadic failures when cloning
nettle.
E.g. when building nettle on the OSS-Fuzz platform:
Step #1: [0m[91mfatal: unable to access
'https://git.lysator.liu.se/nettle/nettle.git/': Couldn't connect to server
Step #1: The command '/bin/sh -c git
On 10/24/19 11:47 AM, Wim Lewis wrote:
> On Wed, Oct 23, 2019 at 08:14:15PM +0200, Niels Möller wrote:
>> inside ..., which is supposed to override whatever the
>> actual http headers say. And that seems to work.
>
> That was my understanding as well but I had almost this problem a week
> or so
On 07.01.19 19:24, Simo Sorce wrote:
> They seem minor enough not to really need a new release IMO, people can
> get them from master as needed. Or maybe you can commit patches on the
> 3.4 branch so people can find them more easily if they really care.
>
> I have a question though, why C89
On 29.12.18 12:36, Nikos Mavrogiannopoulos wrote:
> For x86 builds the new image uses debian because it has a simpler and has a
> reproducible way to generate it. The x86 fedora image will remain though.
>
> With the current nettle master oss fuzz still fails to compile (does link
> statically)
Thank you, Niels !
On 26.12.18 15:28, Niels Möller wrote:
> Tim Rühsen writes:
>
>> Are you going to merge all of those into your master branch, so that
>> e.g. latest GnuTLS can be build it ?
>
> I've now done a merge from the release-3.4-fixes branch to master. The
On 12/3/18 9:09 AM, Nikos Mavrogiannopoulos wrote:
> On Sun, 2018-12-02 at 17:46 +0100, Tim Rühsen wrote:
>
>>>> Currently I see a several automated builds breaking. It's those
>>>> with
>>>> the latest GnuTLS (from git master) as dependency. They n
Hi Niels,
thank you (and all involved) for the fixes !
Are you going to merge all of those into your master branch, so that
e.g. latest GnuTLS can be build it ?
Reason:
Currently I see a several automated builds breaking. It's those with
the latest GnuTLS (from git master) as dependency. They
Hi,
are you going to upload a tarball to https://ftp.gnu.org/gnu/nettle/ ?
Regards, Tim
On 11/18/18 11:42 AM, Niels Möller wrote:
> It turns out there's a need for a bugfix-only release nettle-3.4.1, to
> be released in a few weeks.
>
> I've created a branch release-3.4-fixes, and backported a
On 08/13/2018 11:30 AM, Niels Möller wrote:
> Tim Rühsen writes:
>
>> #defines should not start with an underscore. C standards say this is
>> reserved (for system headers !?) and some static analyzers complain
>> about it.
>
> Note that Nettle has violated this
Hi Niels,
#defines should not start with an underscore. C standards say this is
reserved (for system headers !?) and some static analyzers complain
about it.
7.1.3 Reserved Identifiers
...
All identifiers that begin with an underscore and either an uppercase
letter or another underscore are
___
nettle-bugs mailing list
nettle-bugs@lists.lysator.liu.se
http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
On Mittwoch, 8. November 2017 21:29:57 CET Tim Rühsen wrote:
> On Mittwoch, 8. November 2017 12:44:28 CET Niels Möller wrote:
> > Tim Rühsen <tim.rueh...@gmx.de> writes:
> > > And of course you might be right and this is a bug in the sanitizer.
> > > I leave that d
On Mittwoch, 8. November 2017 12:44:28 CET Niels Möller wrote:
> Tim Rühsen <tim.rueh...@gmx.de> writes:
> > And of course you might be right and this is a bug in the sanitizer.
> > I leave that discussion to the experts and open a bug at oss-fuzz as soon
> > as I fin
On Sonntag, 5. November 2017 23:20:27 CET Niels Möller wrote:
> Tim Rühsen <tim.rueh...@gmx.de> writes:
> > Nothing with a real impact, just to silence sanitizers.
>
> Can you explain precisely what's undefined behavior in this code ?
>
> > diff --git a/sec
Nothing with a real impact, just to silence sanitizers.
From OSS-Fuzz:
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior
/src/libfuzzer/FuzzerSHA1.cpp:132:14 in
sec-tabselect.c:58:24: runtime error: negation of 1 cannot be
represented in type 'mp_limb_t' (aka 'unsigned long')
Hi,
commit 57e304262262b0f483d76f9981bb4b99b8ec2869 breaks certain builds
(likely those with --disable-shared). As a side effect, the oss-fuzz
build for Wget2 fails.
Example:
./.bootstrap
./configure --enable-mini-gmp --enable-static --disable-shared
--disable-documentation
make clean && make
Am Freitag, 7. September 2012 schrieb Niels Möller:
Tim Ruehsen tim.rueh...@gmx.de writes:
#define NONNULL(args) __attribute__ ((nonnull args))
Yes, functions with several non-null args than need several NONNULL(x)
occurrences.
I don't think so. NONNULL((1,3,5)) should work, with
23 matches
Mail list logo
