Project: Apache Hadoop (App Definition and Development / Database)
File: encryption.md

<! 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, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. See accompanying LICENSE file. --> <!-- MACRO{toc|fromDepth=0|toDepth=2} --> The S3A filesystem client supports Amazon S3's Server Side Encryption and Client Side Encryption for encrypting data at-rest. For up to date information on the encryption mechanisms, read: When configuring an encryption method in the `core-site.xml`, this will apply cluster wide. Any new file written will be encrypted with this encryption configuration. When the S3A client reads a file, S3 will attempt to decrypt it using the mechanism and keys with which the file was encrypted. It is NOT* advised to mix and match encryption types in a bucket. It is much simpler and safer to encrypt with just one type and key per bucket. You can use AWS bucket policies to mandate encryption rules for a bucket. You can use S3A per-bucket configuration to ensure that S3A clients use encryption policies consistent with the mandated rules. You can use S3 Default Encryption in AWS console to encrypt data without needing to set anything in the client. Changing the encryption options on the client does not change how existing files were encrypted, except when the files are renamed. For all mechanisms other than SSE-C and CSE-KMS, clients do not need any configuration options set in order to read encrypted data: it is all automatically handled in S3 itself. Encryption options and secrets are collected by and passed to workers during job submission. Encryption options and secrets MAY be stored in JCEKS files or any other Hadoop credential provider service. This allows for more secure storage than XML files, including password protection of the secrets. AWS S3 supports server-side encryption inside the storage system itself. When an S3 client uploading data requests data to be encrypted, then an encryption key is used to encrypt the data as it saved to S3. It remains encrypted on S3 until deleted: clients cannot change the encryption attributes of an object once uploaded. The Amazon AWS SDK also offers client-side encryption, in which all the encoding and decoding of data is performed on the client. The server-side "SSE" encryption is performed with symmetric AES256 encryption; S3 offers different mechanisms for actually defining the key to use. There are five key management mechanisms, which in order of simplicity of use, are: S3 Default Encryption SSE-S3: an AES256 key is generated in S3, and saved alongside the data. SSE-KMS: an AES256 key is generated in S3, and encrypted with a secret key provided by Amazon's Key Management Service, a key referenced by name in the uploading client. SSE-C : the client specifies an actual base64 encoded AES-256 key to be used to encrypt and decrypt the data. DSSE-KMS: Two independent layers of encryption at server side. An AES256 key is generated in S3, and encrypted with a secret key provided by Amazon's Key Management

Encryption options | type | encryption | config on write | config on read | |-||--|-| | `SSE-S3` | server side, AES256 | encryption algorithm | none | | `SSE-KMS` | server side, KMS key | key used to encrypt/decrypt | none | | `SSE-C` | server side, custom key | encryption algorithm and secret | encryption algorithm and secret | | `CSE-KMS` | client side, KMS key | encryption algorithm and key ID | encryption algorithm | | `DSSE-KMS` | server side, KMS key | key used to encrypt/decrypt | none | With server-side encryption, the data is uploaded to S3 unencrypted (but wrapped by the HTTPS encryption channel). The data is encrypted in the S3 store and decrypted when it's being retrieved. A server side algorithm can be enabled by default for a bucket, so that whenever data is uploaded unencrypted a default encryption algorithm is added. When data is encrypted with S3-SSE, SSE-KMS or DSSE-KMS it is transparent to all clients downloading the data. SSE-C is different in that every client must know the secret key needed to decypt the data. Working with SSE-C data is harder because every client must be configured to use the algorithm and supply the key. In particular, it is very hard to mix SSE-C encrypted objects in the same S3 bucket with objects encrypted with other algorithms or unencrypted; The S3A client (and other applications) get very confused. KMS-based key encryption is powerful as access to a key can be restricted to specific users/IAM roles. However, use of the key is billed and can be throttled. Furthermore as a client seeks around a file, the KMS key may be used multiple times. S3 Client side encryption (CSE-KMS) is an experimental feature added in July This encrypts the data on the client, before transmitting to S3, where it is stored encrypted. The data is unencrypted after downloading when it is being read back. In CSE-KMS, the ID of an AWS-KMS key is provided to the S3A client; the client communicates with AWS-KMS to request a new encryption key, which KMS returns along with the same key encrypted with the KMS key. The S3 client encrypts the payload and attaches the KMS-encrypted version of the key as a header to the object. When downloading data, this header is extracted, passed to AWS KMS, and, if the client has the appropriate permissions, the symmetric key is retrieved. This key is then used to decode the data. This feature allows the administrators of the AWS account to set the "default" encryption policy on a bucket -the encryption to use if the client does not explicitly declare an encryption algorithm. This supports SSE-S3, SSE-KMS and DSSE-KMS. There is no need to set anything up in the client: do it in the AWS console. In SSE-S3, all keys and secrets are managed inside S3. This is the simplest encryption mechanism. There is no extra cost for storing data with this option. To write S3-SSE encrypted files, the value of `fs.s3a.encryption.algorithm` must be set to that of the encryption mechanism used in `core-site`; currently only `AES256` is supported. ```xml <property> <name>fs.s3a.encryption.algorithm</name> <value>AES256</value> </property> ``` Once set, all new data will be stored encrypted. There is no need to set this property when downloading data the data will be automatically decrypted when read using the Amazon S3-managed

To learn more, refer to . Amazon offers a pay-per-use key management service, . This service can be used to encrypt data on S3 by defining "customer master keys", CMKs, which can be centrally managed and assigned to specific roles and IAM accounts. The AWS KMS . The AWS KMS service is not related to the Key Management Service built into Hadoop (Hadoop KMS). The Hadoop KMS primarily focuses on managing keys for HDFS Transparent Encryption. Similarly, HDFS encryption is unrelated to S3 data encryption. When uploading data encrypted with SSE-KMS, the sequence is as follows. The S3A client must declare a specific CMK in the property `fs.s3a.encryption.key`, or leave it blank to use the default configured for that region. The S3A client uploads all the data as normal, now including encryption information. The S3 service encrypts the data with a symmetric key unique to the new object. The S3 service retrieves the chosen CMK key from the KMS service, and, if the user has the right to use it, uses it to encrypt the object-specific key. When downloading SSE-KMS encrypted data, the sequence is as follows The S3A client issues an HTTP GET request to read the data. S3 sees that the data was encrypted with SSE-KMS, and looks up the specific key in the KMS service If and only if the requesting user has been granted permission to use the CMS key does the KMS service provide S3 with the key. As a result, S3 will only decode the data if the user has been granted access to the key. KMS keys can be managed by an organization's administrators in AWS, including having access permissions assigned and removed from specific users, groups, and IAM roles. Only those "principals" with granted rights to a key may access it, hence only they may encrypt data with the key, and decrypt data encrypted with it. This allows KMS to be used to provide a cryptographically secure access control mechanism for data stores on S3. Each KMS server is region specific, and accordingly, so is each CMK configured. A CMK defined in one region cannot be used with an S3 bucket in a different region. Notes Callers are charged for every use of a key, both for encrypting the data in uploads and for decrypting it when reading it back. Random-access IO on files may result in multiple GET requests of an object during a read sequence (especially for columnar data), so may require more than one key retrieval to process a single file, The KMS service is throttled: too many requests may cause requests to fail. As well as incurring charges, heavy I/O may* reach IO limits for a customer. If those limits are reached, they can be increased through the AWS console. To enable SSE-KMS, the property `fs.s3a.encryption.algorithm` must be set to `SSE-KMS` in `core-site`: ```xml <property> <name>fs.s3a.encryption.algorithm</name> <value>SSE-KMS</value> </property> ``` The ID of the specific key used to encrypt the data should also be set in the property `fs.s3a.encryption.key`: ```xml <property> <name>fs.s3a.encryption.key</name> <value>arn:aws:kms:us-west-2:360379543683:key/071a86ff-8881-4ba0-9230-95af6d01ca01</value> </property> ``` Organizations may define a default key in the Amazon KMS; if a default key is set, then it will be used whenever SSE-KMS encryption is chosen and the value of `fs.s3a.encryption.key` is empty. With SSE-KMS, the S3A client option

sets the key to be used when new files are created. When reading files, this key, and indeed the value of `fs.s3a.encryption.algorithm` is ignored: S3 will attempt to retrieve the key and decrypt the file based on the create-time settings. This means that There's no need to configure any client simply reading data. It is possible for a client to read data encrypted with one KMS key, and write it with another. In SSE-C, the client supplies the secret key needed to read and write data. Every client trying to read or write data must be configured with the same secret key. SSE-C integration with Hadoop is still stabilizing; issues related to it are still surfacing. It is already clear that SSE-C with a common key <b>must</b> be used exclusively within a bucket if it is to be used at all. This is the only way to ensure that path and directory listings do not fail with "Bad Request" errors. To use SSE-C, the configuration option `fs.s3a.encryption.algorithm` must be set to `SSE-C`, and a base-64 encoding of the key placed in `fs.s3a.encryption.key`. ```xml <property> <name>fs.s3a.encryption.algorithm</name> <value>SSE-C</value> </property> <property> <name>fs.s3a.encryption.key</name> <value>SGVscCwgSSdtIHRyYXBwZWQgaW5zaWRlIGEgYmFzZS02NC1jb2RlYyE=</value> </property> ``` All clients must share this same key. With SSE-C, the S3A client option `fs.s3a.encryption.key` sets the key to be used for both reading and writing data. When reading any file written with SSE-C, the same key must be set in the property `fs.s3a.encryption.key`. This is unlike SSE-S3 and SSE-KMS, where the information needed to decode data is kept in AWS infrastructure. You need to fully understand how SSE-C works in the S3 environment before using this encryption type. Please refer to the Server Side Encryption documentation available from AWS. SSE-C is only recommended for advanced users with advanced encryption use cases. Failure to properly manage encryption keys can cause data loss. Currently, the AWS S3 API(and thus S3A) only supports one encryption key and cannot support decrypting objects during moves under a previous key to a new destination. It is NOT advised to use multiple encryption keys in a bucket, and is recommended to use one key per bucket and to not change this key. This is due to when a request is made to S3, the actual encryption key must be provided to decrypt the object and access the metadata. Since only one encryption key can be provided at a time, S3A will not pass the correct encryption key to decrypt the data. By providing a dual-layer server-side encryption mechanism using AWS Key Management Service (AWS KMS) keys, known as DSSE-KMS, two layers of encryption are applied to objects upon their upload to Amazon S3. DSSE-KMS simplifies the process of meeting compliance requirements that mandate the implementation of multiple layers of encryption for data while maintaining complete control over the encryption keys. When uploading data encrypted with SSE-KMS, the sequence is as follows: The S3A client must declare a specific CMK in the property `fs.s3a.encryption.key`, or leave it blank to use the default configured for that region. The S3A client uploads all the data as normal, now including encryption information. The S3 service encrypts the data with a symmetric key unique to the new object. The S3 service retrieves the chosen CMK key from the KMS service, and, if the user has the right to use it, uses it to provide dual-layer encryption for the

When downloading DSSE-KMS encrypted data, the sequence is as follows The S3A client issues an HTTP GET request to read the data. S3 sees that the data was encrypted with DSSE-KMS, and looks up the specific key in the KMS service. If and only if the requesting user has been granted permission to use the CMS key does the KMS service provide S3 with the key. As a result, S3 will only decode the data if the user has been granted access to the key. Further reading on DSSE-KMS AWS Blog post To enable DSSE-KMS, the property `fs.s3a.encryption.algorithm` must be set to `DSSE-KMS` in `core-site`: ```xml <property> <name>fs.s3a.encryption.algorithm</name> <value>DSSE-KMS</value> </property> ``` The ID of the specific key used to encrypt the data should also be set in the property `fs.s3a.encryption.key`: ```xml <property> <name>fs.s3a.encryption.key</name> <value>arn:aws:kms:us-west-2:360379543683:key/071a86ff-8881-4ba0-9230-95af6d01ca01</value> </property> ``` Organizations may define a default key in the Amazon KMS; if a default key is set, then it will be used whenever SSE-KMS encryption is chosen and the value of `fs.s3a.encryption.key` is empty. With SSE-KMS, the S3A client option `fs.s3a.encryption.key` sets the key to be used when new files are created. When reading files, this key, and indeed the value of `fs.s3a.encryption.algorithm` is ignored: S3 will attempt to retrieve the key and decrypt the file based on the create-time settings. This means that There's no need to configure any client simply reading data. It is possible for a client to read data encrypted with one KMS key, and write it with another. Because it is up to the clients to enable encryption on new objects, all clients must be correctly configured in order to guarantee that data is encrypted. To mandate that all data uploaded to a bucket is encrypted, you can set a declaring that clients must provide encryption information with all data uploaded. Mandating an encryption mechanism on newly uploaded data does not encrypt existing data; existing data will retain whatever encryption (if any) applied at the time of creation Here is a policy to mandate `SSE-S3/AES265` encryption on all data uploaded to a bucket. This covers uploads as well as the copy operations which take place when file/directory rename operations are mimicked. ```json { "Version": "2012-10-17", "Id": "EncryptionPolicy", "Statement": [ { "Sid": "RequireEncryptionHeaderOnPut", "Effect": "Deny", "Principal": "*", "Action": [ "s3:PutObject" ], "Resource": "arn:aws:s3:::BUCKET/*", "Condition": { "Null": { "s3:x-amz-server-side-encryption": true } } }, { "Sid": "RequireAESEncryptionOnPut", "Effect": "Deny", "Principal": "*", "Action": [ "s3:PutObject" ], "Resource": "arn:aws:s3:::BUCKET/*", "Condition": { "StringNotEquals": { "s3:x-amz-server-side-encryption": "AES256" } } } ] } ``` To use SSE-KMS, a different restriction must be defined: ```json { "Version": "2012-10-17", "Id": "EncryptionPolicy", "Statement": [ { "Sid": "RequireEncryptionHeaderOnPut", "Effect": "Deny", "Principal": "*", "Action": [ "s3:PutObject" ], "Resource": "arn:aws:s3:::BUCKET/*", "Condition": { "Null": { "s3:x-amz-server-side-encryption": true } } }, { "Sid": "RequireKMSEncryptionOnPut", "Effect": "Deny", "Principal": "*", "Action": [ "s3:PutObject" ], "Resource": "arn:aws:s3:::BUCKET/*", "Condition": { "StringNotEquals": { "s3:x-amz-server-side-encryption": "SSE-KMS" } } } ] } ``` To use one of these policies: Replace `BUCKET` with the specific name of the bucket being secured. Locate the bucket in the AWS console . Select the "Permissions" tab. Select the "Bucket Policy" tab in the permissions section. Paste the edited policy into the form. Save the policy. In an organisation which has embraced S3 encryption, different buckets inevitably have different encryption policies, such as different keys for SSE-KMS

In particular, as different keys need to be named for different regions, unless you rely on the administrator-managed "default" key for each S3 region, you will need unique keys. S3A's per-bucket configuration enables this. Here, for example, are settings for a bucket in London, `london-stats`: ```xml <property> <name>fs.s3a.bucket.london-stats.server-side-encryption-algorithm</name> <value>AES256</value> </property> ``` This requests SSE-S; if matched with a bucket policy then all data will be encrypted as it is uploaded. A different bucket can use a different policy (here SSE-KMS) and, when necessary, declare a key. Here is an example bucket in S3 Ireland, which uses SSE-KMS and a KMS key hosted in the AWS-KMS service in the same region. ```xml <property> <name>fs.s3a.bucket.ireland-dev.server-side-encryption-algorithm</name> <value>SSE-KMS</value> </property> <property> <name>fs.s3a.bucket.ireland-dev.server-side-encryption.key</name> <value>arn:aws:kms:eu-west-1:98067faff834c:key/071a86ff-8881-4ba0-9230-95af6d01ca01</value> </property> ``` Again the appropriate bucket policy can be used to guarantee that all callers will use SSE-KMS; they can even mandate the name of the key used to encrypt the data, so guaranteeing that access to thee data can be read by everyone granted access to that key, and nobody without access to it. The S3A client retrieves all HTTP headers from an object and returns them in the "XAttr" list of attributed, prefixed with `header.`. This makes them retrievable in the `getXAttr()` API calls, which is available on the command line through the `hadoop fs -getfattr -d` command. This makes viewing the encryption headers of a file straightforward. Here is an example of the operation invoked on a file where the client is using CSE-KMS: ``` bin/hadoop fs -getfattr -d s3a://test-london/file2 2021-07-14 12:59:01,554 [main] WARN s3.AmazonS3EncryptionClientV2 (AmazonS3EncryptionClientV2.java:warnOnLegacyCryptoMode(409)) - The S3 Encryption Client is configured to read encrypted data with legacy encryption modes through the CryptoMode setting. If you don't have objects encrypted with these legacy modes, you should disable support for them to enhance security. See https://docs.aws.amazon.com/general/latest/gr/awssdkcryptography.html 2021-07-14 12:59:01,558 [main] WARN s3.AmazonS3EncryptionClientV2 (AmazonS3EncryptionClientV2.java:warnOnRangeGetsEnabled(401)) - The S3 Encryption Client is configured to support range get requests. Range gets do not provide authenticated encryption properties even when used with an authenticated mode (AES-GCM). See https://docs.aws.amazon.com/general/latest/gr/awssdkcryptography.html header.Content-Length="0" header.Content-Type="application/octet-stream" header.ETag="63b3f4bd6758712c98f1be86afad095a" header.Last-Modified="Wed Jul 14 12:56:06 BST 2021" header.x-amz-cek-alg="AES/GCM/NoPadding" header.x-amz-iv="ZfrgtxvcR41yNVkw" header.x-amz-key-v2="AQIDAHjZrfEIkNG24/xy/pqPPLcLJulg+O5pLgbag/745OH4VQFuiRnSS5sOfqXJyIa4FOvNAAAAfjB8BgkqhkiG9w0BBwagbzBtAgEAMGgGCSqGSIb3DQEHATAeBglghkgBZQMEAS4wEQQM7b5GZzD4eAGTC6gaAgEQgDte9Et/dhR7LAMU/NaPUZSgXWN5pRnM4hGHBiRNEVrDM+7+iotSTKxFco+VdBAzwFZfHjn0DOoSZEukNw==" header.x-amz-matdesc="{"aws:x-amz-cek-alg":"AES/GCM/NoPadding"}" header.x-amz-server-side-encryption="AES256" header.x-amz-tag-len="128" header.x-amz-unencrypted-content-length="0" header.x-amz-version-id="zXccFCB9eICszFgqv_paG1pzaUKY09Xa" header.x-amz-wrap-alg="kms+context" ``` Analysis The WARN commands are the AWS SDK warning that because the S3A client uses an encryption algorithm which seek() requires, the SDK considers it less secure than the most recent algorithm(s). Ignore. `header.x-amz-server-side-encryption="AES256"` : the file has been encrypted with S3-SSE. This is set up as the S3 default encryption, so even when CSE is enabled, the data is doubly encrypted. `header.x-amz-cek-alg="AES/GCM/NoPadding`: client-side encrypted with the `"AES/GCM/NoPadding` algorithm. `header.x-amz-iv="ZfrgtxvcR41yNVkw"`: `header.x-amz-key-v2="AQIDAHjZrfEIkNG24/xy/pqPPLcLJulg+O5pLgbag/745OH4VQFuiRnSS5sOfqXJyIa4FOvNAAAAfjB8BgkqhkiG9w0BBwagbzBtAgEAMGgGCSqGSIb3DQEHATAeBglghkgBZQMEAS4wEQQM7b5GZzD4eAGTC6gaAgEQgDte9Et/dhR7LAMU/NaPUZSgXWN5pRnM4hGHBiRNEVrDM+7+iotSTKxFco+VdBAzwFZfHjn0DOoSZEukNw=="`: `header.x-amz-unencrypted-content-length="0"`: this is the length of the unencrypted data. The S3A client DOES NOT* use this header; `header.x-amz-wrap-alg="kms+context"`: the algorithm used to encrypt the CSE key it always removes 16 bytes from non-empty files when declaring the length. `header.x-amz-version-id="zXccFCB9eICszFgqv_paG1pzaUKY09Xa"`: the bucket is versioned; this is the version ID. And a directory encrypted with S3-SSE only: ``` bin/hadoop fs -getfattr -d s3a://test-london/user/stevel/target/test/data/sOCOsNgEjv header.Content-Length="0" header.Content-Type="application/x-directory" header.ETag="d41d8cd98f00b204e9800998ecf8427e" header.Last-Modified="Tue Jul 13 20:12:07 BST 2021" header.x-amz-server-side-encryption="AES256" header.x-amz-version-id="KcDOVmznIagWx3gP1HlDqcZvm1mFWZ2a" ``` A file with no-encryption (on a bucket without versioning but with intelligent tiering): ``` bin/hadoop fs -getfattr -d s3a://noaa-cors-pds/raw/2024/001/akse/AKSE001x.24_.gz header.Content-Length="524671" header.Content-Type="binary/octet-stream" header.ETag=""3e39531220fbd3747d32cf93a79a7a0c"" header.Last-Modified="Tue Jan 02 00:15:13 GMT 2024" header.x-amz-server-side-encryption="AES256" ``` The encryption of an object is set when it is

If you want to encrypt an unencrypted file, or change the SEE-KMS key of a file, the only way to do so is by copying the object. How can you do that from Hadoop? With `rename()`. The S3A client mimics a real filesystem's' rename operation by copying all the source files to the destination paths, then deleting the old ones. Note: this does not work for SSE-C, because you cannot set a different key for reading as for writing, and you must supply that key for reading. There you need to copy one bucket to a different bucket, one with a different key. Use `distCp`for this, with per-bucket encryption policies. Amazon S3 Client Side Encryption(S3-CSE), is used to encrypt data on the client-side and then transmit it over to S3 storage. The same encrypted data is then transmitted over to client while reading and then decrypted on the client-side. S3-CSE, uses `AmazonS3EncryptionClientV2.java` as the AmazonS3 client. The encryption and decryption is done by AWS SDK. As of July 2021, Only CSE-KMS method is supported. A key reason this feature (HADOOP-13887) has been unavailable for a long time is that the AWS S3 client pads uploaded objects with a 16 byte footer. This meant that files were shorter when being read than when are listed them through any of the list API calls/getFileStatus(). Which broke many applications, including anything seeking near the end of a file to read a footer, as ORC and Parquet do. There is now a workaround: compensate for the footer in listings when CSE is enabled. When listing files and directories, 16 bytes are subtracted from the length of all non-empty objects( greater than or equal to 16 bytes). Directory markers MAY be longer than 0 bytes long. This "appears" to work; secondly it does in the testing as of July 2021. However , the length of files when listed through the S3A client is now going to be shorter than the length of files listed with other clients -including S3A clients where S3-CSE has not been enabled. Supports client side encryption with keys managed in AWS KMS. encryption settings propagated into jobs through any issued delegation tokens. encryption information stored as headers in the uploaded object. Performance will be reduced. All encrypt/decrypt is now being done on the client. Writing files may be slower, as only a single block can be encrypted and uploaded at a time. Multipart Uploader API disabled. Multipart uploads would be serial, and partSize must be a multiple of 16 bytes. maximum message size in bytes that can be encrypted under this mode is 2^36-32, or ~64G, due to the security limitation of AES/GCM as recommended by NIST. Generate an AWS KMS Key ID from AWS console for your bucket, with same region as the storage bucket. If already created, Set `fs.s3a.encryption.algorithm=CSE-KMS`. Set `fs.s3a.encryption.key=<KMSKEYID>`. KMSKEYID: Identifies the symmetric CMK that encrypts the data key. To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with "alias/". To specify a CMK in a different AWS account, you must use the key ARN or alias ARN. For example: Key ID: `1234abcd-12ab-34cd-56ef-1234567890ab` Key ARN: `arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab` Alias name: `alias/ExampleAlias` Alias ARN: `arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias` Note: If `fs.s3a.encryption.algorithm=CSE-KMS` is set, `fs.s3a.encryption.key=<KMSKEYID>` property must be set for S3-CSE to work. ```xml <property> <name>fs.s3a.encryption.algorithm</name> <value>CSE-KMS</value> </property> <property> <name>fs.s3a.encryption.key</name> <value>${KMSKEYID}</value> </property> ``` The document covers stack traces which may surface when working with encrypted data.