- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 124 for fuzzers (0.19 sec)
-
pkg/fuzz/README.md
```shell go test ./path/to/pkg -v -run=^$ -fuzz=Fuzz ``` ## CI testing Go fuzzers are run as part of standard unit tests against known test cases (from `f.Add` (which `fuzz.BaseCases` calls), or `testdata`). For continuous fuzzing, [`OSS-Fuzz`](https://github.com/google/oss-fuzz) continually builds and runs the fuzzers and reports any failures.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Oct 05 21:25:25 UTC 2023 - 1.9K bytes - Viewed (0) -
tests/fuzz/README.md
# Istio fuzzing Istio has a series of fuzzers that run continuously through OSS-fuzz. ## Native fuzzers While many jobs are still using the old [go-fuzz](https://github.com/dvyukov/go-fuzz) style fuzzers, using [Go 1.18 native fuzzing](https://go.dev/doc/fuzz/) is preferred. These should be written alongside standard test packages. Currently, these cannot be in `<pkg>_test` packages; instead move them to a file under `<pkg>`.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Aug 23 16:45:44 UTC 2022 - 994 bytes - Viewed (0) -
tests/fuzz/regression_test.go
} for _, tt := range cases { if testedFuzzers.InsertContains(tt.name) { t.Fatalf("dupliate fuzzer test %v", tt.name) } t.Run(tt.name, func(t *testing.T) { runRegressionTest(t, tt.name, tt.fuzzer) }) } t.Run("completeness", func(t *testing.T) { match := regexp.MustCompile(`func Fuzz.+\(`) fuzzers, err := walkMatch(filepath.Join(env.IstioSrc, "tests/fuzz"), match) if err != nil { t.Fatal(err)
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Fri Feb 10 16:43:09 UTC 2023 - 5.9K bytes - Viewed (0) -
tensorflow/cc/framework/fuzzing/op_fuzzing.bzl
"""Functions for automatically generating fuzzers.""" load( "//tensorflow:tensorflow.bzl", "if_not_windows", "lrt_if_needed", "tf_cc_binary", "tf_copts", ) load( "//tensorflow/core/platform:rules_cc.bzl", "cc_test", ) def tf_gen_op_wrappers_fuzz( name, op_def_src, api_def_srcs = [], kernel_deps = []): """ Generates fuzzers for several groups of ops.
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Mon Nov 07 19:14:57 UTC 2022 - 4.3K bytes - Viewed (0) -
tests/integration/security/fuzz/fuzz_test.go
return false } func runFuzzer(t framework.TestContext, fuzzer, ns, server string) { pods, err := t.Clusters().Default().PodsForSelector(context.TODO(), ns, "app="+fuzzer) if err != nil { t.Fatalf("failed to get %s pod: %v", fuzzer, err) } t.Logf("running %s test against the %s (should normally complete in 60 seconds)...", fuzzer, server) switch fuzzer { case dotdotpwn:
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Apr 08 22:02:59 UTC 2024 - 12.9K bytes - Viewed (0) -
tests/integration/security/fuzz/README.md
## Overview ![](overview.jpg) The fuzz test uses specialized web vulnerability fuzzers ([jwt_tool](https://github.com/ticarpi/jwt_tool), [dotdotpwn](https://github.com/wireghoul/dotdotpwn)) and [wfuzz](https://github.com/xmendez/wfuzz) to generate a large number of fuzzed requests. The mutation is based on a predefined path (`/private/secret.html`) that should be
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Fri Jul 09 02:34:11 UTC 2021 - 2.3K bytes - Viewed (0) -
tests/fuzz/oss_fuzz_build.sh
# and Go would therefore remove it from go.mod once we run "go mod tidy && go mod vendor". printf "package main\nimport _ \"github.com/AdamKorcz/go-118-fuzz-build/testing\"\n" > register.go go mod tidy # Find all native fuzzers and compile them # shellcheck disable=SC2016 grep --line-buffered --include '*_test.go' -Pr 'func Fuzz.*\(.* \*testing\.F' | sed -E 's/(func Fuzz(.*)\(.*)/\2/' | xargs -I{} sh -c ' fname="$(dirname $(echo "{}" | cut -d: -f1))"
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Jun 03 15:50:05 UTC 2024 - 6.5K bytes - Viewed (0) -
tests/fuzz/misc_fuzzers.go
// See the License for the specific language governing permissions and // limitations under the License. // This file has a series of fuzzers that target different // parts of Istio. They are placed here because it does not // make sense to place them in different files yet. // The fuzzers can be moved to other files without anything // breaking on the OSS-fuzz side. package fuzz import (
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Jun 23 02:26:59 UTC 2022 - 5.1K bytes - Viewed (0) -
tensorflow/cc/framework/fuzzing/cc_op_fuzz_gen_main.cc
// Main executable to generate op fuzzers /* Copyright 2016 The TensorFlow Authors. All Rights Reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS,
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Tue Jun 11 10:53:49 UTC 2024 - 3.2K bytes - Viewed (0) -
tensorflow/cc/framework/fuzzing/cc_op_fuzz_gen.cc
std::cout << "NOT fuzzing: " << op_info.graph_op_def.name() << " is deprecated.\n"; return false; } // TODO(unda, b/249347507): should we hide fuzzers for hidden ops? if (op_info.api_def.visibility() == ApiDef::HIDDEN) { std::cout << "NOT fuzzing: " << op_info.graph_op_def.name() << " is hidden.\n"; return false; }
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Sat Jan 27 16:26:51 UTC 2024 - 13K bytes - Viewed (0)