--- Log opened Wed Apr 15 00:00:52 2020
00:29 -!- jonatack_ [~jon@37.173.103.51] has joined #secp256k1
00:32 -!- jonatack [~jon@37.170.227.51] has quit [Ping timeout: 240 seconds]
03:15 -!- jonatack__ [~jon@37.172.252.66] has joined #secp256k1
03:18 -!- jonatack_ [~jon@37.173.103.51] has quit [Ping timeout: 260 seconds]
04:00 -!- jonatack__ [~jon@37.172.252.66] has quit [Read error: Connection reset by peer]
04:01 -!- jonatack__ [~jon@37.172.252.66] has joined #secp256k1
04:27 -!- Apocalyptic [~Apocalypt@unaffiliated/apocalyptic] has quit [Quit: Quit]
04:27 -!- Apocalyptic [~Apocalypt@unaffiliated/apocalyptic] has joined #secp256k1
05:33 -!- jonatack__ [~jon@37.172.252.66] has quit [Quit: jonatack__]
05:34 -!- jonatack [~jon@37.172.252.66] has joined #secp256k1
07:10 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
07:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
07:51 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
07:56 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 265 seconds]
08:08 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
09:23 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit []
13:16 < elichai2> ariard: ha. they do say 90 days disclosure or 30 days after fix, maybe we can talk with them to make an exception?
13:18 < sipa> i think we'd need to have meaningful fuzzers for libsecp256k1 before we can discuss participating in oss-fuzz i think
13:21 < elichai2> sipa: for libsodium they fuzz the public API https://github.com/google/oss-fuzz/blob/master/projects/libsodium/secret_key_auth_fuzzer.cc
13:22 < sipa> sure, that makes sense
13:22 < sipa> but someone would still need to write that fuzzer for libsecp256k1
13:22 < sipa> and my point is that that is an interesting thing to do, whether or not we're interested in oss-fuzz
13:23 < sipa> and until someone does, the question is moot
13:23 < elichai2> so something like that I can probably write in an hour or two I think. (just copy their libsodium thing and replace it with libsecp functions)
13:24 < elichai2> although I don't have much experience with fuzzers, but looking at how it's implemented there for other projects it looks very simple
13:25 < sipa> maybe play around with the bitcoin core ones a bit first?
13:25 < sipa> it's useful to get a feel for what kind of approaches work well
13:25 < elichai2> integrating a fuzzing option into our autotools might take more time though.
13:25 < elichai2> sure, so I guess you're right, it's better to start with "in house" fuzzing which we can then copy to oss-fuzz
13:25 < sipa> there is nothing to copy
13:26 < sipa> libfuzzer == oss-fuzz
13:26 < sipa> oss-fuzz is just google machinery running it for you
13:26 < elichai2> right. It just looks like the fuzzing code needs to be hosted in the `oss-fuzz` repo for them to run it
13:27 < sipa> oh, ok - that's possible
13:27 < elichai2> and they have a whole docker and stuff
13:27 < sipa> but it'd be identical i mean; same API etc
13:27 < sipa> anyway, bitcoin core is getting more and more decent fuzzers recently
13:27 < sipa> integrated in autotools etc
13:28 < sipa> see doc/fuzzing.md
13:28 < sipa> it's fun to play around with
14:04 -!- jonatack [~jon@37.172.252.66] has quit [Ping timeout: 260 seconds]
14:06 -!- jonatack [~jon@37.171.222.247] has joined #secp256k1
14:37 < elichai2> nickler: I see everyone became interested in anonymous credentials suddenly :P https://github.com/isislovecruft/aeonflux
14:55 -!- jonatack [~jon@37.171.222.247] has quit [Ping timeout: 265 seconds]
14:56 -!- jonatack [~jon@213.152.162.69] has joined #secp256k1
15:44 < TD-Linux> gmaxwell, https://lab.whitequark.org/notes/2020-04-06/synthesizing-optimal-8051-code/
16:01 < midnight> TD-Linux: that approach is something that I was saying a few months ago would be *really cool* to know if it would work for power because of how hard it is for humans to fully keep in mind the entire billion instructions on that isa.
16:01 < midnight> <3 whitequark's awesome projects
20:36 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Quit: Quit]
20:36 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #secp256k1
20:37 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Client Quit]
20:37 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #secp256k1
--- Log closed Thu Apr 16 00:00:53 2020