- Sort Score
- Result 10 results
- Languages All
Results 1 - 2 of 2 for myself (2.22 sec)
-
internal/crypto/doc.go
// for implementing Server-Side-Encryption (SSE-S3) and Server-Side-Encryption // with customer provided keys (SSE-C). // // All objects are encrypted with an unique and randomly generated 'ObjectKey'. // The ObjectKey itself is never stored in plaintext. Instead it is only stored // in a sealed from. The sealed 'ObjectKey' is created by encrypting the 'ObjectKey' // with an unique key-encryption-key. Given the correct key-encryption-key the
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Aug 26 19:52:29 GMT 2022 - 5K bytes - Viewed (0) -
src/cmd/cgo/doc.go
executable itself. Keeping cmd/link simple means we cannot possibly implement the full semantics of the host linker, so the kinds of objects that can be linked directly into the binary is limited (other code can only be used as a dynamic library). On the other hand, when using internal linking, cmd/link can generate Go binaries by itself.
Go - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Sun Mar 31 09:02:45 GMT 2024 - 42.1K bytes - Viewed (0)