网络安全导论 课件 第十章 安全通信2_第1页
网络安全导论 课件 第十章 安全通信2_第2页
网络安全导论 课件 第十章 安全通信2_第3页
网络安全导论 课件 第十章 安全通信2_第4页
网络安全导论 课件 第十章 安全通信2_第5页
已阅读5页,还剩47页未读, 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

第十章安全通信(2)SMUCSE5349/49上一次课的内容密钥如何分配

对称加密用的密钥

——三种办法非对称加密中的公钥

——证书一种办法SMUCSE5349/49上一次课的内容Deffie-Hellman协议

SMUCSE5349/49上一次课的内容数字证书SMUCSE5349/49本讲的主要内容“支付宝”是如何保障安全的?“支付宝”使用的安全协议SSL(TLS)。比SSL更安全协议“支付宝”为什么不用?今天课程用到的知识对称加密公钥加密与签名MAC=H(k,M)加密密钥与认证密钥要分开课后要完成的作业Page198:3,4Page215:5,6SMUCSE5349/491支付宝是如何保障安全的?SMUCSE5349/49出现登录界面后,浏览器与服务器之间已经完成的工作如下:

服务器已经提交了数字证书并被浏览器验证完毕.一套密码套件已经协商完毕,48字节的预主密钥已经传送.服务器用443端口通信,SSL握手协议已经完成,包括一个会话已经建立,一个连接中的加密密钥与MAC密钥已经算出。SMUCSE5349/49:

之后的通信内容全是加密的SMUCSE5349/492“支付宝”使用的安全协议SSL/TLSSMUCSE5349/7349LayersofSecuritySMUCSE5349/7349SSLHistoryEvolvedthroughUnreleasedv1(Netscape)Flawed-but-usefulv2Version3fromscratchStandardTLS1.0,TLS1.2SSL3.0withminortweaks,henceVersionfieldis3.1DefinedinRFC2246,/rfc/rfc2246.txtOpen-sourceimplementationat/SMUCSE5349/7349OverviewEstablishasessionAgreeonalgorithmsSharesecretsPerformauthenticationTransferapplicationdataEnsureprivacyandintegritySMUCSE5349/7349ArchitectureRecordProtocoltotransferapplicationandTLSinformationAsessionisestablishedusingaHandshakeProtocolTLSRecordProtocolHandshakeProtocolAlertProtocolChangeCipherSpecSMUCSE5349/7349Architecure(cont’d)HANDLESCOMMUNICATIONWITHTHEAPPLICATIONProtocolsINITIALIZESCOMMUNCATIONBETWEENCLIENT&SERVERINITIALIZESSECURECOMMUNICATIONHANDLESDATACOMPRESSIONERRORHANDLINGSMUCSE5349/7349HandshakeNegotiateCipher-SuiteAlgorithmsSymmetricciphertouseKeyexchangemethodMessagedigestfunctionEstablishandsharemastersecretOptionallyauthenticateserverand/orclientSMUCSE5349/7349HandshakePhasesHellomessagesCertificateandKeyExchangemessagesChangeCipherSpecandFinishedmessagesSMUCSE5349/7349SSLMessagesOFFERCIPHERSUITEMENUTOSERVERSELECTACIPHERSUITESENDCERTIFICATEANDCHAINTOCAROOTCLIENTSIDESERVERSIDESENDPUBLICKEYTOENCRYPTSYMMKEYSERVERNEGOTIATIONFINISHEDSENDENCRYPTEDSYMMETRICKEYSOURCE:THOMAS,SSLANDTLSESSENTIALSACTIVATEENCRYPTIONCLIENTPORTIONDONE(SERVERCHECKSOPTIONS)ACTIVATESERVERENCRYPTIONSERVERPORTIONDONE(CLIENTCHECKSOPTIONS)NOWTHEPARTIESCANUSESYMMETRICENCRYPTIONSMUCSE5349/7349ClientHelloProtocolversionSSLv3(major=3,minor=0)TLS(major=3,minor=1)RandomNumber32bytesFirst4bytes,timeofthedayinseconds,other28bytesrandomPreventsreplayattackSessionID32bytes–indicatestheuseofpreviouscryptographicmaterialCompressionalgorithmSMUCSE5349/7349ClientHello-CipherSuitesINITIAL(NULL)CIPHERSUITEPUBLIC-KEYALGORITHMSYMMETRICALGORITHMHASHALGORITHMCIPHERSUITECODESUSEDINSSLMESSAGESSSL_NULL_WITH_NULL_NULL={0,0}SSL_RSA_WITH_NULL_MD5={0,1}SSL_RSA_WITH_NULL_SHA={0,2}SSL_RSA_EXPORT_WITH_RC4_40_MD5={0,3}SSL_RSA_WITH_RC4_128_MD5={0,4}SSL_RSA_WITH_RC4_128_SHA={0,5}SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5={0,6}SSL_RSA_WITH_IDEA_CBC_SHA={0,7}SSL_RSA_EXPORT_WITH_DES40_CBC_SHA={0,8}SSL_RSA_WITH_DES_CBC_SHA={0,9}SSL_RSA_WITH_3DES_EDE_CBC_SHA={0,10}

SMUCSE5349/7349ServerHelloVersionRandomNumberProtectsagainsthandshakereplaySessionIDProvidedtotheclientforlaterresumptionofthesessionCiphersuiteUsuallypicksclient’sbestpreference–NoobligationCompressionmethodSMUCSE5349/7349CertificatesSequenceofX.509certificatesServer’s,CA’s,…X.509CertificateassociatespublickeywithidentityCertificationAuthority(CA)createscertificateAdherestopoliciesandverifiesidentitySignscertificateUserofCertificatemustensureitisvalidSMUCSE5349/7349ValidatingaCertificateMustrecognizeacceptedCAincertificatechainOneCAmayissuecertificateforanotherCAMustverifythatcertificatehasnotbeenrevokedCApublishesCertificateRevocationList(CRL)SMUCSE5349/7349ClientKeyExchangePremastersecretCreatedbyclient;usedto“seed”calculationofencryptionparameters2bytesofSSLversion+46randombytesSentencryptedtoserverusingserver’spublickeyThisiswheretheattackhappenedinSSLv2SMUCSE5349/7349ChangeCipherSpec&

FinishedMessagesChangeCipherSpecSwitchtonewlynegotiatedalgorithmsandkeymaterialFinishedFirstmessageencryptedwithnewcryptoparametersDigestofnegotiatedmastersecret,theensembleofhandshakemessages,senderconstantHMACapproachofnestedhashingSMUCSE5349/7349SSLEncryptionMastersecretGeneratedbybothpartiesfrompremastersecretandrandomvaluesgeneratedbybothclientandserverKeymaterialGeneratedfromthemastersecretandsharedrandomvaluesEncryptionkeysExtractedfromthekeymaterialSMUCSE5349/7349GeneratingtheMasterSecret

SOURCE:THOMAS,SSLANDTLSESSENTIALSSERVER’SPUBLICKEYISSENTBYSERVERINServerKeyExchangeCLIENTGENERATESTHEPREMASTERSECRETENCRYPTSWITHPUBLICKEYOFSERVERCLIENTSENDSPREMASTERSECRETINClientKeyExchangeSENTBYCLIENTINClientHelloSENTBYSERVERINServerHelloMASTERSECRETIS3MD5HASHESCONCATENATEDTOGETHER=384BITSSMUCSE5349/7349GenerationofKeyMaterialSOURCE:THOMAS,SSLANDTLSESSENTIALSJUSTLIKEFORMING

THEMASTERSECRETEXCEPTTHEMASTERSECRETISUSEDHEREINSTEADOFTHEPREMASTERSECRET...SMUCSE5349/7349ObtainingKeysfromtheKeyMaterial

SOURCE:THOMAS,SSLANDTLSESSENTIALSSECRETVALUESINCLUDEDINMESSAGEAUTHENTICATIONCODESINITIALIZATIONVECTORSFORDESCBCENCRYPTIONSYMMETRICKEYSSMUCSE5349/7349SSLRecordProtocolSMUCSE5349/7349RecordHeaderThreepiecesofinformationContenttypeApplicationdataAlertHandshakeChange_cipher_specContentlengthSuggestswhentostartprocessingSSLversionRedundantcheckforversionagreementSMUCSE5349/7349Protocol(cont’d)Max.recordlength214–1MACDataHeadersSequencenumberTopreventreplayandreorderingattackNotincludedintherecordSMUCSE5349/7349AlertsandClosureAlerttheothersideofexceptionsDifferentlevelsTerminateandsessioncannotberesumedClosurenotifyTopreventtruncationattack(sendingaTCPFINbeforethesenderisfinished)SMUCSE5349/7349SSLSessionsSessionsvs.ConnectionsMultipleconnectionswithinasessionsOnenegotiation/sessionSessionResumptionThroughsessionIDsClientsuseserverIPaddressornameasindexServersusethesessionIDsprovidebytheclientsUseofrandomnumbersinresumedsessionkeycalculationensuresdifferentkeysSessionRe-handshakeClientcaninitiateanewhandshakewithinasessionUseofServerGatedCryptography(SGC)foraddedsecuritySMUCSE5349/7349SSLOverhead2-10timesslowerthanaTCPsessionWheredowelosetimeHandshakephaseClientdoespublic-keyencryptionServerdoesprivate-keyencryption(stillpublic-keycryptography)UsuallyclientshavetowaitonserverstofinishDataTransferphaseSymmetrickeyencryptionSMUCSE5349/7349SSLApplicationsHTTP–originalapplicationSecuremailServertoclientconnectionSMTP/SSL?Telnet,ftp..Resources:/related/apps.htmlSMUCSE5349/493“支付宝”为什么不用更安全的协议?SMUCSE5349/49WTLSSMUCSE5349/7349WAPGatewayArchitectureWTLSHTTP/SSLHTTP/SSLWirelessGatewayApplicationServersSMUCSE5349/7349WAPStackConfigurationSMUCSE5349/7349WirelessTransportLayerSecurity(WTLS)Providessecurityservicesbetweenthemobiledevice(client)andtheWAPgatewayDataintegrityPrivacy(throughencryption)Authentication(throughcertificates)Denial-of-serviceprotection(detectsandrejectsmessagesthatarereplayed)SMUCSE5349/7349WTLSProtocolStackSMUCSE5349/7349WTLSRecordProtocolTakesinfofromthenexthigherlevelandencapsulatesthemintoaPDUPayloadiscompressedAMACiscomputedCompressedmessageplusMACcodeareencryptedusingsymmetricencryptionRecordprotocoladdsaheadertothebeginningtoencryptedpayloadSMUCSE5349/734

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

评论

0/150

提交评论