Crowdly
Add to Chrome
Criptografia Aplicada
Looking for Criptografia Aplicada test answers and solutions? Browse our comprehensive collection of verified answers for Criptografia Aplicada at moodle24.iscte-iul.pt.
Get instant access to accurate answers and detailed explanations for your course questions. Our community-driven platform helps students succeed!
No estabelecimento de uma ligação SSH, o cliente envia a mensagem SSH_MSG_SERVICE_REQUEST para solicitar algum serviço ao servidor.
Que tipo de serviço pode ser esse?
Qual dos seguintes comandos produz o seguinte resultado do SSH?
OpenSSH_9.6p1, LibreSSL 3.3.6debug1: Reading configuration data /Users/cserrao/.ssh/configdebug1: Reading configuration data /etc/ssh/ssh_configdebug1: /etc/ssh/ssh_config line 21: include /etc/ssh/ssh_config.d/* matched no filesdebug1: /etc/ssh/ssh_config line 54: Applying options for *debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disablingdebug1: Connecting to 194.210.86.20 [194.210.86.20] port 22.debug1: Connection established.debug1: identity file /Users/cserrao/.ssh/id_rsa type 0debug1: identity file /Users/cserrao/.ssh/id_rsa-cert type -1debug1: identity file /Users/cserrao/.ssh/id_ecdsa type -1debug1: identity file /Users/cserrao/.ssh/id_ecdsa-cert type -1debug1: identity file /Users/cserrao/.ssh/id_ecdsa_sk type -1debug1: identity file /Users/cserrao/.ssh/id_ecdsa_sk-cert type -1debug1: identity file /Users/cserrao/.ssh/id_ed25519 type -1debug1: identity file /Users/cserrao/.ssh/id_ed25519-cert type -1debug1: identity file /Users/cserrao/.ssh/id_ed25519_sk type -1debug1: identity file /Users/cserrao/.ssh/id_ed25519_sk-cert type -1debug1: identity file /Users/cserrao/.ssh/id_xmss type -1debug1: identity file /Users/cserrao/.ssh/id_xmss-cert type -1debug1: identity file /Users/cserrao/.ssh/id_dsa type -1debug1: identity file /Users/cserrao/.ssh/id_dsa-cert type -1debug1: Local version string SSH-2.0-OpenSSH_9.6debug1: Remote protocol version 2.0, remote software version OpenSSH_8.4p1 Debian-5+deb11u3debug1: compat_banner: match: OpenSSH_8.4p1 Debian-5+deb11u3 pat OpenSSH* compat 0x04000000debug1: Authenticating to 194.210.86.20:22 as 'cserrao'debug1: load_hostkeys: fopen /Users/cserrao/.ssh/known_hosts2: No such file or directorydebug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directorydebug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directorydebug1: SSH2_MSG_KEXINIT sentdebug1: SSH2_MSG_KEXINIT receiveddebug1: kex: algorithm: curve25519-sha256debug1: kex: host key algorithm: ssh-ed25519debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: nonedebug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: nonedebug1: expecting SSH2_MSG_KEX_ECDH_REPLYdebug1: SSH2_MSG_KEX_ECDH_REPLY receiveddebug1: Server host key: ssh-ed25519 SHA256:mLb2oRGl9GWkaAP2WW4RZQURRytM9hicD0jYR9a8E5kdebug1: load_hostkeys: fopen /Users/cserrao/.ssh/known_hosts2: No such file or directorydebug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directorydebug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directorydebug1: Host '194.210.86.20' is known and matches the ED25519 host key.debug1: Found key in /Users/cserrao/.ssh/known_hosts:23debug1: ssh_packet_send2_wrapped: resetting send seqnr 3debug1: rekey out after 134217728 blocksdebug1: SSH2_MSG_NEWKEYS sentdebug1: expecting SSH2_MSG_NEWKEYSdebug1: ssh_packet_read_poll2: resetting read seqnr 3debug1: SSH2_MSG_NEWKEYS receiveddebug1: rekey in after 134217728 blocksdebug1: SSH2_MSG_EXT_INFO receiveddebug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,[email protected],ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected]>debug1: SSH2_MSG_SERVICE_ACCEPT receiveddebug1: Authentications that can continue: publickeydebug1: Next authentication method: publickeydebug1: get_agent_identities: bound agent to hostkeydebug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identitiesdebug1: Will attempt key: /Users/cserrao/.ssh/id_rsa RSA SHA256:6rjZpHA9b2eQqPTtHC0xVQtbqQGPq7Fq9Bq1f2yh5AMdebug1: Will attempt key: /Users/cserrao/.ssh/id_ecdsadebug1: Will attempt key: /Users/cserrao/.ssh/id_ecdsa_skdebug1: Will attempt key: /Users/cserrao/.ssh/id_ed25519debug1: Will attempt key: /Users/cserrao/.ssh/id_ed25519_skdebug1: Will attempt key: /Users/cserrao/.ssh/id_xmssdebug1: Will attempt key: /Users/cserrao/.ssh/id_dsadebug1: Offering public key: /Users/cserrao/.ssh/id_rsa RSA SHA256:6rjZpHA9b2eQqPTtHC0xVQtbqQGPq7Fq9Bq1f2yh5AMdebug1: Server accepts key: /Users/cserrao/.ssh/id_rsa RSA SHA256:6rjZpHA9b2eQqPTtHC0xVQtbqQGPq7Fq9Bq1f2yh5AMEnter passphrase for key '/Users/cserrao/.ssh/id_rsa':
Qual dos seguintes protocolos NÃO se situa acima do "Record Protocol" na pilha SSL/TLS, conforme ilustrado?
A que corresponde a seguinte informação? (escolha a opção mais correta)
MIME-Version: 1.0Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha-256"; boundary="----F46C4B7E272BA661D77AA4FF41655372"
This is an S/MIME signed message------F46C4B7E272BA661D77AA4FF41655372Este é o meu email secreto que eu pretendo assinar digitalmente!
------F46C4B7E272BA661D77AA4FF41655372Content-Type: application/x-pkcs7-signature; name="smime.p7s"Content-Transfer-Encoding: base64Content-Disposition: attachment; filename="smime.p7s"
MIIE6wYJKoZIhvcNAQcCoIIE3DCCBNgCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGgggK4MIICtDCCAh2gAwIBAgIBAjANBgkqhkiG9w0BAQsFADBhMQswCQYDVQQGEwJQVDEPMA0GA1UECAwGTGlzYm9hMQ8wDQYDVQQHDAZMaXNib2ExEjAQBgNVBAoMCUlTQ1RFLUlVTDENMAsGA1UECwwESVNUQTENMAsGA1UEAwwEU1JTSTAeFw0xNTExMDUwODQ0MDdaFw0xNjExMDQwODQ0MDdaMGIxCzAJBgNVBAYTAlBUMQ8wDQYDVQQIDAZMaXNib2ExDzANBgNVBAcMBkxpc2JvYTEhMB8GA1UECgwYSW50ZXJuZXQgV2lkZ2l0cyBQdHkgTHRkMQ4wDAYDVQQDDAVBbGljZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2RSZZp0l7ZeH1PDTLelHT9KBOxTri1re9dvMTpbsfMkqXZim/CXv2UGp9k4DxxIsSbqoARxajK8t81zvBh/ttbZjgT1MTi3K0ywpVNqfYKR2UKkaujfqlqF5tjErf09tzXNZcCr5hZtYYOiCLF/ThSGkOvTJDLH+TO64GkoIonECAwEAAaN7MHkwCQYDVR0TBAIwADAsBglghkgBhvhCAQ0EHxYdT3BlblNTTCBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFLqF8QmxcgwOPZNJNMAWg3I0js70MB8GA1UdIwQYMBaAFMypQ4gGj9SdNUCW2St2htc5ix1DMA0GCSqGSIb3DQEBCwUAA4GBAGunwN3AvSx3fRk7qLIoypaN/WD/AgJE5z6qA1h6fEjsrJQPBUqcjPWtpPOeNKBE5Q45zPchRW2dMXdWQwW4dCB0nWoAVCjxFHnUMWMUjWWmHG8p7n9xb85H+6lPBrPSLWAgQPAbrADnud79NpRK2f13QLFc3jP7JyewTQAWXTNYMYIB9zCCAfMCAQEwZjBhMQswCQYDVQQGEwJQVDEPMA0GA1UECAwGTGlzYm9hMQ8wDQYDVQQHDAZMaXNib2ExEjAQBgNVBAoMCUlTQ1RFLUlVTDENMAsGA1UECwwESVNUQTENMAsGA1UEAwwEU1JTSQIBAjANBglghkgBZQMEAgEFAKCB5DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTExMDUxMDEzMzhaMC8GCSqGSIb3DQEJBDEiBCCTTSIGPJF42yCzx4CWYZyjbuqxG61TBWA4hARuTLR/WTB5BgkqhkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASBgHfqoRy3pJi+BIIYNAhDou+BY9WmcXeP5z7t7UCIe3FH0HHrdveCNk7G2TYeYCPHEj+6uJORxGc4WCF/SsM9kbRFU1CPxJuwzHfkIaWB05yCk5H6eRv85ZRG10wgMaXk2wVoDunshjvW1vMjS1sYxN6vvAqIZU/Pj/A/LaN79Lsc
------F46C4B7E272BA661D77AA4FF41655372--Qual destes é um algoritmo de assinatura digital pós-quântica?
A RFC 2634 descreve "Enhanced Security Services for S/MIME". Um exemplo de tal serviço poderia ser:
De acordo com os algoritmos selecionados pelo NIST, qual dos seguintes é projetado especificamente para estabelecimento de chaves (Key Encapsulation Mechanism - KEM)?
Um advogado precisa de enviar documentos confidenciais a um cliente por correio eletrónico e quer garantir que apenas o cliente os consiga ler. Que serviço S/MIME deve utilizar?
Qual o papel da "informação de quem assina" anexada a uma mensagem assinada digitalmente no S/MIME, para além da própria assinatura?
Dado o seguinte trecho, o que representa o mesmo?
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-
signature"; micalg="sha-256"; boundary="----
585BF8182B32542477043593989FA8FF"
This is an S/MIME message
------585BF8182B32542477043593989FA8FF
This is my secret message!!!!
------585BF8182B32542477043593989FA8FF
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
MIIJzwYJKoZIhvcNAQcCoIIJwDCCCbwCAQExDTALBglghkgBZQMEAgEwCwYJKoZI
hvcNAQcBoIIGBjCCBgIwggPqoAMCAQICEQCyAUXgSTEnfJ0WluRzyDFfMA0GCSqG
SIb3DQEBBQUAMGoxCzAJBgNVBAYTAlBUMQ8wDQYDVQQIDAZMaXNib2ExDzANBgNV
BAcMBkxpc2JvYTESMBAGA1UECgwJSXNjdGUtSVVMMQ0wCwYDVQQLDARJU1RBMRYw
FAYDVQQDDA1DQSBJU1RBIElTQ1RFMB4XDTI0MDUxNDIzNDUwNFoXDTI1MDUxNDI