- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 166 for easing (0.04 sec)
-
doc/godebug.md
field by default. Go 1.24 enabled the post-quantum key exchange mechanism X25519MLKEM768 by default. The default can be reverted using the [`tlsmlkem` setting](/pkg/crypto/tls/#Config.CurvePreferences). This can be useful when dealing with buggy TLS servers that do not handle large records correctly, causing a timeout during the handshake (see [TLS post-quantum TL;DR fail](https://tldr.fail/)).
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Tue Jul 08 18:30:38 UTC 2025 - 22.9K bytes - Viewed (0) -
src/main/java/jcifs/internal/smb2/Smb2Constants.java
*/ public static final int SMB2_DIALECT_ANY = 0x02FF; /** * Server supports DFS */ public static final int SMB2_GLOBAL_CAP_DFS = 0x1; /** * Server supports leasing */ public static final int SMB2_GLOBAL_CAP_LEASING = 0x2; /** * Server supports multi-credit operations */ public static final int SMB2_GLOBAL_CAP_LARGE_MTU = 0x4; /**
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 23 05:11:12 UTC 2025 - 4.5K bytes - Viewed (0) -
.github/SUPPORT.md
Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions. We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://go.dev/s/proposal-process). For asking questions, see: * [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts) * [The Go Forum](https://forum.golangbridge.org/), a web-based forum
Registered: Tue Sep 09 11:13:09 UTC 2025 - Last Modified: Wed Mar 29 22:00:27 UTC 2023 - 692 bytes - Viewed (0) -
cmd/erasure-healing-common.go
// inspection to understand the root cause. E.g, this could be due to // backend filesystem corruption. // listOnlineDisks - returns // - a slice of disks where disk having 'older' xl.meta (or nothing) // are set to nil. // - latest (in time) of the maximally occurring modTime(s), which has at least quorum occurrences.
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Sun Mar 30 00:56:02 UTC 2025 - 12K bytes - Viewed (0) -
.github/workflows/missing_playground.yml
stale-issue-label: "status:stale" days-before-stale: 0
Registered: Sun Sep 07 09:35:13 UTC 2025 - Last Modified: Tue Apr 11 02:27:05 UTC 2023 - 1.3K bytes - Viewed (0) -
docs/SMB3_IMPLEMENTATION_PLAN.md
- Update `SmbSession` for multi-channel awareness - Enhance `SmbTransport` for channel management --- ### Phase 4: Directory Leasing **Priority: MEDIUM** | **Estimated Effort: 2-3 weeks** Directory leasing extends the lease concept to directories for improved metadata caching. #### 4.1 Core Directory Lease Infrastructure ``` Package: jcifs.internal.smb2.lease
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 02:53:50 UTC 2025 - 10.7K bytes - Viewed (0) -
src/test/java/jcifs/pac/ASN1UtilTest.java
void testAs_Object_Success() throws PACDecodingException { // Test successful casting String expected = "test string"; Object obj = expected; String result = ASN1Util.as(String.class, obj); assertSame(expected, result); } @Test void testAs_Object_Failure() { // Test failed casting Object obj = 123; // Integer assertThrows(PACDecodingException.class, () -> {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 9.4K bytes - Viewed (0) -
cmd/erasure-healing-common_test.go
Klaus Post <******@****.***> 1756435188 +0200
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 22.4K bytes - Viewed (0) -
src/main/java/jcifs/internal/smb2/lease/DirectoryCacheScope.java
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */ package jcifs.internal.smb2.lease; /** * Defines the scope of directory caching for SMB3 directory leasing */ public enum DirectoryCacheScope { /** * Cache only direct children of the directory */ IMMEDIATE_CHILDREN, /** * Cache entire subtree recursively (if supported by server)
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 23 01:47:47 UTC 2025 - 1.3K bytes - Viewed (0) -
docs/security/README.md
- Delete one/some master keys. From a security standpoint, this is equal to erasing all SSE-S3 encrypted objects protected by these master keys. All these objects are lost forever as they cannot be decrypted. Especially deleting all master keys at the KMS is equivalent to secure erasing all SSE-S3 encrypted objects. ## Acronyms - **AEAD**: Authenticated Encryption with Associated Data
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Feb 26 09:25:50 UTC 2025 - 13.8K bytes - Viewed (0)