- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 242 for derive (0.03 seconds)
-
internal/crypto/sse.go
"github.com/minio/sio" ) const ( // SealAlgorithm is the encryption/sealing algorithm used to derive & seal // the key-encryption-key and to en/decrypt the object data. SealAlgorithm = "DAREv2-HMAC-SHA256" // InsecureSealAlgorithm is the legacy encryption/sealing algorithm used // to derive & seal the key-encryption-key and to en/decrypt the object data.
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 4.3K bytes - Click Count (0) -
impl/maven-core/src/main/java/org/apache/maven/plugin/prefix/DefaultPluginPrefixRequest.java
* used as well. * * @param prefix The plugin prefix to resolve, must not be {@code null}. * @param session The build session from which to derive further settings, must not be {@code null}. */ public DefaultPluginPrefixRequest(String prefix, MavenSession session) { setPrefix(prefix); setRepositorySession(session.getRepositorySession());Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Fri Jun 06 14:28:57 GMT 2025 - 4K bytes - Click Count (0) -
impl/maven-cli/src/main/java/org/apache/maven/cling/invoker/mvn/resident/ResidentMavenInvoker.java
// TODO: in a moment Maven stop pushing user properties to system properties (and maybe something more) // and allow multiple instances per JVM, this may become a pool? derive key based in invokerRequest? MavenContext result = residentContext.computeIfAbsent( "resident", k -> new MavenContext(invokerRequest, false, (MavenOptions)
Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Thu Sep 11 17:20:46 GMT 2025 - 4.1K bytes - Click Count (0) -
impl/maven-core/src/main/java/org/apache/maven/execution/ExecutionListener.java
/** * Defines events that Maven fires during a build. <strong>Warning:</strong> This interface might be extended in future * Maven versions to support further events. Hence it is strongly recommended to derive custom listeners from * {@link AbstractExecutionListener} in order to avoid interoperability problems. * */ public interface ExecutionListener { void projectDiscoveryStarted(ExecutionEvent event);
Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Fri Oct 25 12:31:46 GMT 2024 - 2K bytes - Click Count (0) -
internal/crypto/doc.go
// // SSE-S3 can use either a master key or a KMS as root-of-trust. // The en/decryption slightly depens upon which root-of-trust is used. // // ### SSE-S3 and single master key // // The master key is used to derive unique object- and key-encryption-keys. // SSE-S3 with a single master key works as SSE-C where the master key is // used as the client-provided key. // // 1. Encrypt:
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Aug 26 19:52:29 GMT 2022 - 5K bytes - Click Count (0) -
build-logic-commons/basics/src/main/kotlin/gradlebuild/basics/transforms/Minify.kt
} } private fun extractArtifactName(fileName: String): String { return jarArtifactRegex.matchEntire(fileName) ?.groupValues ?.get(1) ?: error("Cannot derive artifact name from: $fileName") } private fun minify(artifact: File, keepClasses: Set<String>, jarFile: File): File { val tempDirectory = java.nio.file.Files.createTempDirectory(jarFile.name).toFile()Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Thu Dec 18 11:46:45 GMT 2025 - 4.9K bytes - Click Count (0) -
internal/crypto/metadata.go
// MetaIV is the random initialization vector (IV) used for // the MinIO-internal key derivation. MetaIV = "X-Minio-Internal-Server-Side-Encryption-Iv" // MetaAlgorithm is the algorithm used to derive internal keys // and encrypt the objects. MetaAlgorithm = "X-Minio-Internal-Server-Side-Encryption-Seal-Algorithm" // MetaSealedKeySSEC is the sealed object encryption key in case of SSE-C.
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Mon Jun 10 17:40:33 GMT 2024 - 6.4K bytes - Click Count (0) -
internal/config/drive/drive.go
// You should have received a copy of the GNU Affero General Public License // along with this program. If not, see <http://www.gnu.org/licenses/>. package drive import ( "sync" "time" "github.com/minio/minio/internal/config" "github.com/minio/pkg/v3/env" ) // Drive specific timeout environment variables const ( EnvMaxDriveTimeout = "MINIO_DRIVE_MAX_TIMEOUT" EnvMaxDriveTimeoutLegacy = "_MINIO_DRIVE_MAX_TIMEOUT"
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Mon Nov 11 14:51:43 GMT 2024 - 3K bytes - Click Count (0) -
cmd/metrics-v3-system-drive.go
} func (m *MetricValues) setDriveBasicMetrics(drive madmin.Disk, labels []string) { m.Set(driveUsedBytes, float64(drive.UsedSpace), labels...) m.Set(driveFreeBytes, float64(drive.AvailableSpace), labels...) m.Set(driveTotalBytes, float64(drive.TotalSpace), labels...) m.Set(driveUsedInodes, float64(drive.UsedInodes), labels...) m.Set(driveFreeInodes, float64(drive.FreeInodes), labels...)
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Mar 30 00:56:02 GMT 2025 - 7.8K bytes - Click Count (0) -
docs/erasure/README.md
drives. Therefore, the number of drives you present must be a multiple of one of these numbers. Each object is written to a single erasure-coding set. Minio uses the largest possible EC set size which divides into the number of drives given. For example, *18 drives* are configured as *2 sets of 9 drives*, and *24 drives* are configured as *2 sets of 12 drives*. This is true for scenarios when running MinIO as a standalone erasure coded deployment. In [distributed setup however node (affinity)...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Aug 12 18:20:36 GMT 2025 - 4.2K bytes - Click Count (0)