Decryption
If you decrypt this u get 1 credit
gV5wfl0bXZLFgUn+Zr9DbSTp2XaqK9nRLKN7LJWfGuKksuOCDhm22GSy1Dhk3agjTXoWQsvu8MVyNoExH4/pMPR82C6++M8r2v/Q+WQYBPUtEGKsVr7Bd4aZ/n4d0R/FlFwet6ETjLnpU5p1P5hah86OLthS/twXb+onQmE5r208cDxITSdWZ6lPxcSDiSR3vMjpTiEcp3Bjv7OGm4+dkA==
if i dont reply it means you are incorrect
EDIT: just post the code here instead of /msg me.
The answer I got was- “p”.
Is this correct?
p
@steveplayz6 what decryption method did you guys use (it is still incorrect)
I used the frequency distributions method
^p~]]ŁIfCm$v+,{,⤲d8dݨ#MzBr61 0|.+d-bVw~ Ŕ\ Su?ZΎ.Ro'Ba9m<p<HM'VgOă$wN! pc
Ill try a different method.
The code answer I got is- 23,55,70,4,17,3,66,6,40,59,63,53,16,58,28,79,42,19,74,55,21,60,38,20,66,57,18,2,60,86,28,54,60,42,61,68,59,37,37,2,55,20,56,24,4,26,61,39,52,9,30,65,69,40,33,29,65,37,27,24,68,14,21,14,36,57,28,36,38,28,4,17,72,44,37,10,57,0,55,28,56,85,92,3,58,63,32,92,66,34,69,88,92,34,74,22,66,23,92,34,92,56,35,61,50,49,38,7,50,40,57,23,38,19,68,49,19,91,19,62,95,15,71,23,71,61,93,34,28,39,4,22,3,89,55,48,26,45,29,3,34,90,2,85,32,84,27,18,31,87,68,43,60,21,27,32,88,27,5,60,18,74,28,29,38,2,55,81,2,83,67,75,20,43,10,45,36,50,23,36,45,89,30,52,8,2,32,55,30,60,32,87,6,44,25,3,35,6,55,7,0,82,49,25,1,88,61,35,29,85,88,23,28,46,79,89,122,107
�^p~]�]�Å�Iþf¿Cm$éÙvª+ÙÑ,£{,���⤲ã���¶Ød²Ô8dݨ#Mz�BËîðÅr6�1��é0ô|Ø.¾øÏ+ÚÿÐùd��õ-�b¬V¾Áw��þ~�Ñ�Å�\�·¡��¹éS�u?�Z�Î�.ØRþÜ�oê'Ba9¯m<p<HM'Vg©OÅÄ��$w¼ÈéN!�§pc¿³�����
gV5wfl0bXZLF…A==
Z1Y1d2ZsMGJYWkxGZ1VuK1pyOURiU1RwMlhhcUs5blJMS043TEpXZkd1S2tzdU9DRGhtMjJHU3kxRGhrM2FnalRYb1dRc3Z1OE1WeU5vRXhINC9wTVBSODJDNisrTThyMnYvUStXUVlCUFV0RUdLc1ZyN0JkNGFaL240ZDBSL0ZsRndldDZFVGpMbnBVNXAxUDVoYWg4Nk9MdGhTL3R3WGIrb25RbUU1cjIwOGNEeElUU2RXWjZsUHhjU0RpU1Izdk1qcFRpRWNwM0JqdjdPR200K2RrQT09
is it any of those?
yeah that is not gonna work lol
Diabetic ketoacidosis is a serious complication of diabetes.
The condition develops when the body can't produce enough insulin. Insulin plays a key role in helping sugar — a major source of energy for muscles and other tissues — enter cells in the body.
Without enough insulin, the body begins to break down fat as fuel. This causes a buildup of acids in the bloodstream called ketones. If it's left untreated, the buildup can lead to diabetic ketoacidosis.
If you have diabetes or you're at risk of diabetes, learn the warning signs of diabetic ketoacidosis and when to seek emergency care.
is it this?
is it a text, sentence,numbers?!?!
is it A????????????
Diabetic ketoacidosis
yep it is
I searched it up
that mean im right?
i just got this one
The average is
46.4446.44
46.44
, the median is
3838
38
, and the modes are
2,28,38,55,60,922 comma 28 comma 38 comma 55 comma 60 comma 92
2,28,38,55,60,92
.
idk
You can use this operation to decrypt ciphertext that was encrypted under a symmetric encryption KMS key or an asymmetric encryption KMS key. When the KMS key is asymmetric, you must specify the KMS key and the encryption algorithm that was used to encrypt the ciphertext. For information about asymmetric KMS keys, see Asymmetric KMS keys in the AWS Key Management Service Developer Guide.
The Decrypt operation also decrypts ciphertext that was encrypted outside of AWS KMS by the public key in an AWS KMS asymmetric KMS key. However, it cannot decrypt symmetric ciphertext produced by other libraries, such as the AWS Encryption SDK or Amazon S3 client-side encryption. These libraries return a ciphertext format that is incompatible with AWS KMS.
If the ciphertext was encrypted under a symmetric encryption KMS key, the KeyId parameter is optional. AWS KMS can get this information from metadata that it adds to the symmetric ciphertext blob. This feature adds durability to your implementation by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even if they've lost track of the key ID. However, specifying the KMS key is always recommended as a best practice. When you use the KeyId parameter to specify a KMS key, AWS KMS only uses the KMS key you specify. If the ciphertext was encrypted under a different KMS key, the Decrypt operation fails. This practice ensures that you use the KMS key that you intend.
Whenever possible, use key policies to give users permission to call the Decrypt operation on a particular KMS key, instead of using IAM policies. Otherwise, you might create an IAM policy that gives the user Decrypt permission on all KMS keys. This user could decrypt ciphertext that was encrypted by KMS keys in other accounts if the key policy for the cross-account KMS key permits it. If you must use an IAM policy for Decrypt permissions, limit the user to particular KMS keys or particular trusted accounts. For details, see Best practices for IAM policies in the AWS Key Management Service Developer Guide.
Decrypt also supports AWS Nitro Enclaves, which provide an isolated compute environment in Amazon EC2. To call Decrypt for a Nitro enclave, use the AWS Nitro Enclaves SDK or any AWS SDK. Use the Recipient parameter to provide the attestation document for the enclave. Instead of the plaintext data, the response includes the plaintext data encrypted with the public key from the attestation document (CiphertextForRecipient). For information about the interaction between AWS KMS and AWS Nitro Enclaves, see How AWS Nitro Enclaves uses AWS KMS in the AWS Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of AWS KMS keys in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. If you use the KeyId parameter to identify a KMS key in a different AWS account, specify the key ARN or the alias ARN of the KMS key.
Required permissions: kms:Decrypt (key policy)
Related operations:
Eventual consistency: The AWS KMS API follows an eventual consistency model. For more information, see AWS KMS eventual consistency.
death yt stop spamming