Bradley Kemp

Currently anonymous structs have a blank name. It would be nice to just have a default name of "[]struct" or something.

The "address" of a map reflect.Value is actually the address of the struct field so although maps are reference types they get treated as if they have been copied if...

I ran the fuzz harness already in the codebase (https://github.com/gocql/gocql/blob/master/fuzz.go) and found two panics: These can be reproduced using: ```go package main import "github.com/gocql/gocql" var data = "" func main()...

`throttle` trigger modifier behaviour doesn't match the reference

2

https://htmx.org/attributes/hx-trigger/ says: > throttle: - a throttle will occur before an event triggers a request. If the event is seen again before the delay completes it is ignored, the element...

I'm hoping to create a custom "event" table (i.e. using https://osquery.readthedocs.io/en/stable/development/pubsub-framework rather than a traditional, on-demand generated table). It seems like `osquery-go` might only support the on-demand generate table style...

Quick replies not handled correctly as postbacks

6

When the user clicks on a quick reply button this triggers a bot.on('message', .....) handler whereas this should probably trigger a bot.on('postback', ....) instead?

There's loads of places to report phishing sites but phish.report aggregates them all in a single place so might be more useful than listing them all here. Disclaimer: I run...

Infinite loop if `ExponentialBackoff.Stop` is zero/unset

4

If `ExponentialBackoff.Stop` is zero (e.g. if you forget to initialise it) then the backoff function can run into an infinite loop on this line: https://github.com/cenkalti/backoff/blob/a04a6fe64ffb0e3fd0816460529d300be5f252df/retry.go#L98 Here `b.NextBackoff()` returns the `ExponentialBackoff.Stop`...

Gracefully handle rules containing invalid search conditions

1

Currently sigma-go panics when given a rule that looks like this: ```yaml detection: someCondition: foo: bar condition: nonExistentCondition ``` This panic happens here: https://github.com/bradleyjkemp/sigma-go/blob/fe36bd7f61b78a9aafb7c7e705b1ba2a196da313/evaluator/evaluate_search.go#L41 Instead this function should be extended...

While the `Result` type tells you which conditions matched in your rule, it doesn't help you know *why* they matched. So e.g. for phish.report/IOK rules, you can have a long...