- Sort Score
- Num 10 results
- Language All
Results 1 - 5 of 5 for zeroing (0.21 seconds)
-
lib/fips140/v1.26.0.zip
"io" "sync" "sync/atomic" ) // memory is a scratch buffer that is accessed between samples by the entropy // source to expose it to memory access timings. // // We reuse it and share it between Seed calls to avoid the significant (~500µs) // cost of zeroing a new allocation every time. The entropy source accesses it // using atomics (and doesn't care about its contents). // // It should end up in the .noptrbss section, and become backed by physical pages // at first use. This ensures that programs that...
Created: Tue Apr 07 11:13:11 GMT 2026 - Last Modified: Thu Jan 08 17:58:32 GMT 2026 - 660.3K bytes - Click Count (0) -
RELEASE.md
* `Estimator.export_savedmodel()` now includes all valid serving signatures that can be constructed from the Serving Input Receiver and all available ExportOutputs. For instance, a classifier may provide regression- and prediction-flavored outputs, in addition to the classification-flavored one. Building signatures from these allows TF Serving to honor requests using the
Created: Tue Apr 07 12:39:13 GMT 2026 - Last Modified: Mon Mar 30 18:31:38 GMT 2026 - 746.5K bytes - Click Count (3) -
docs/en/docs/release-notes.md
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Apr 03 12:07:04 GMT 2026 - 631K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.19.md
- Kubeadm: add the deprecated flag --port=0 to kube-controller-manager and kube-scheduler manifests to disable insecure serving. Without this flag the components by default serve (e.g. /metrics) insecurely on the default node interface (controlled by --address). Users that wish to override this behavior and enable insecure serving can pass a custom --port=X via kubeadm's "extraArgs" mechanic for these components. ([#92720](https://github.com/kubernetes/kubernetes/pull/92720),...
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Wed Jan 05 05:42:32 GMT 2022 - 489.7K bytes - Click Count (0) -
lib/fips140/v1.0.0-c2097c7c.zip
0b0000_0001 } privateKey, err := NewPrivateKey(c, key) if err != nil { continue } // A "Pairwise Consistency Test" makes no sense if we just generated the // public key from an ephemeral private key. Moreover, there is no way to // check it aside from redoing the exact same computation again. SP 800-56A // Rev. 3, Section 5.6.2.1.4 acknowledges that, and doesn't require it. // However, ISO 19790:2012, Section 7.10.3.3 has a blanket requirement for a // PCT for all generated keys (AS10.35) and FIPS 140-3...
Created: Tue Apr 07 11:13:11 GMT 2026 - Last Modified: Thu Sep 25 19:53:19 GMT 2025 - 642.7K bytes - Click Count (0)