❓
물음표살인마 블로그
  • README
  • ALGORITHM
    • Sieve of Eratosthenes
    • Lcm, Gcd
    • Sorting Array
    • Round Up
    • Binary Search
    • Union Find
  • Books
    • CS Note for Interview
      • Ch1. Design Pattern & Programming paradigm
        • 1.1.1 Singleton Pattern
        • 1.1.2 Factory Pattern
        • 1.1.4 Observer Pattern
        • 1.1.5 Proxty Pattern & Proxy Server
        • 1.1.8 Model-View-Controller Pattern
        • 1.2.1 Declarative and Functional Programming
        • 1.2.2 Object Oriented Programming
      • Ch2. Network
        • 2.2.1 TCP/IP Four-Layer Model
        • 2.2.1-1 TCP 3, 4 way handshake
        • 2.3 Network Devices L4, L7
        • 2.4.1 ARP, RARP
        • 2.4.2 Hop By Hop Communication
        • 2.4.3 IP Addressing Scheme
      • Ch3. Operating System
        • 3.1.1 Roles and Structure of Operating Systems
        • 3.2.1 Memory Hierarchy
        • 3.2.2 Memory Management
        • 3.3.1 Processes and Compilation Process
        • 3.3.3 Memory Structure of a Process
        • 3.3.4 Process Control Block (PCB)
        • 3.3.5 Multiprocessing
        • 3.3.6 Threads and Multithreading
        • 3.3.7 Shared Resources and Critical Sections
        • 3.3.8 Deadlock
        • 3.4 CPU Scheduling Algorithm
      • Ch4. Database
        • 4.1 Database Basic
        • 4.2 Normalization
        • 4.3 Transaction and Integrity
        • 4.4 Types of Databases
        • 4.5 Indexes
        • 4.6 Types of Joins
        • 4.7 Principles of Joins
      • Ch5. Data Structure
    • Learning the Basics of Large-Scale System Design through Virtual Interview Cases
      • 1. Scalability based on user counts(1/2)
      • 1. Scalability based on user counts(2/2)
      • 2.Back-of-the-envelope estimation
      • 3. Strategies for System Design Interviews
      • 4. Rate Limiter
      • 5. Consistent Hashing
      • 6. Key-Value System Design
      • 7. Designing a Unique ID Generator for Distributed Systems
      • 8. Designing a URL Shortener
      • 9. Designing a Web Crawler
      • 10. Notification System Design
      • 11. Designing a News Feed System
      • 12. Chat System Design
      • 13. AutoComplete
      • 14. Design YouTube
      • 15. Design Google Drive
      • Loadbalancer Algorithms
      • Cache tier
      • CDN, Content Delivery Network
      • Stateless Web tier
    • Computer System A programmer's perspective
    • Effective Java
      • Item 1. Consider Static Factory Methods Instead of Constructors
      • Item 2. Consider a Builder When Faced with Many Constructor Parameters
      • Item 3. Ensure Singleton with Private Constructor or Enum Type
      • Item 4. Enforce Noninstantiability with a Private Constructor
      • Item 5. Prefer Dependency Injection to Hardwiring Resources
      • Item 6. Avoid Creating Unnecessary Objects
      • Item 7. Eliminate Obsolete Object References
      • Item 8. Avoid Finalizers and Cleaners
      • Item 9.Prefer try-with-resources to try-finally
      • Item10. Adhering to General Rules When Overriding equals
        • Handling Transitivity Issues
        • Ensuring Consistency
      • Item11. Override hashCode When You Override equals
      • Item12. Always Override toString
        • Always Override toString
      • Item13. Override Clone Judiciously
      • Item14. Consider Implementing Comparable
      • Item15. Minimize the Accessibility of Classes and Members
      • Item16. Accessor Methods Over Public Fields
      • Item17. Minimize Mutability
      • Item18. Composition over inherentance
      • Item19. Design and Document for Inheritance, or Else Prohibit It
      • Item20. Prefer Interfaces to Abstract Classes
      • Item21. Design Interfaces with Implementations in Mind
      • Item22. Use Interfaces Only to define Types
      • Item23. Prefer Class Hierarchies to Tagged Classes
      • Item24. Favor Static Member Classes Over Non-Static
      • Item28. Use Lists Instead of Arrays
      • Item29. Prefer Generic Types
      • Item30. Favor Generic Methods
    • Head First Design Patterns
      • Ch1. Strategy Pattern
      • Ch2. Observer Pattern
        • Ver1. Ch2. Observer Pattern
      • Ch3. Decorator Pattern
        • Ch3. Decorator Pattern
      • Ch4. Factory Pattern
      • Ch5. Singleton Pattern
      • Ch6. Command Pattern
      • Ch7. Adapter and Facade Pattern
      • Ch8. Template Method Pattern
    • Digging Deep into JVM
      • Chapter 2. Java Memory Area & Memory Overflow
      • Chapter 3. Garbage Collector & Memory Allocation Strategy (1/2)
      • Chapter 3. Garbage Collector & Memory Allocation Strategy (2/2)
      • Chapter 5. Optimization Practice
      • Chapter 6. Class file structure
  • Interview Practices
    • Restful API Practices
      • Url Shortener API
      • Event Ticket Reservation API
      • Course Management API
      • Search posts by tags API
      • Online Code platform API
      • Simple Task Management API
      • Event Participation API
      • Review System API
      • Car management API
      • Online Library
    • Naver Computer Science
      • Process & Thread
      • TCP & UDP
      • Spring & Servlet
      • Filter & Interceptor & AOP
      • Equals() & ==
      • Dependency Injection
  • F-Lab
    • Week1
      • Client & Server
      • HTTP
      • TCP/UDP
      • REST API
      • Questions
        • Object Oriented Programming
        • HTTP
        • Process & Thread
        • Data Structure
    • Week2
      • OSI 7 layer
      • Web vs WAS
    • Week3
      • RDB vs NoSQL
      • RDB Index
      • Cache
      • Redis
      • Messaging Queue
    • Week4
      • Project - Ecommerce
    • Week5
      • ERD - 1
    • Week6
      • Ecommerce - 2
      • Role
      • pw hashing && Salt
      • CreatedAt, ModifiedAt
      • JWT
      • Copy of ERD - 1
    • Week7
      • Vault (HashiCorp Vault)
    • Week 8
      • Api Endpoints
  • Week10
    • Product Create Workflow
  • TOY Project
    • CodeMentor
      • Implementation of Kafka
      • Implementation of K8s
      • Communication between servers in msa
  • JAVA
    • Java 101
      • JVM Structure
      • Java Compiles and Execution Method
      • Override, Overload
      • Interface vs Abstract Class
      • Primitive vs Object Type
      • Identity and equality
      • String, StringBuilder, StringBuffer
      • Checked Exceptions and Unchecked Exceptions
      • Java 8 methods
      • Try-with-reources
      • Strong Coupling and Loose Coupling
      • Serialization and Deserialization
      • Concurrency Programming in Java
      • Mutable vs Immutable
      • JDK vs JRE
    • Java Questions
      • Week 1(1/2) - Basic Java
      • Week 1(2/2) - OOP
      • Week 2(1/2) - String, Exception, Generic
      • Week2(2/2) Lambda, Stream, Annotation, Reflection
      • Week3(1/2) Collections
      • Week3(2/2) Threads
      • Week4 Java Concurrency Programming
      • Week5 JVM & GC
    • Batch delete instead of Cascade
    • Checked vs Unchecked Exception
    • Thread
    • Memory Visibility
    • Synchronized && ReentrantLock
    • Producer & Consumer
    • BlockingQueue
    • CAS (Compare and Set)
  • SPRING
    • Spring Questions
      • Spring Framework
      • Spring MVC & Web Request
      • AOP (Aspect-Oriented Programming)
      • Spring Boot
      • ORM & Data Access
      • Security
      • ETC
    • using profile name as variable
    • Template Method Pattern
    • Strategy Pattern
    • Proxy Pattern
    • @Transactional
    • Ioc container, di practice
  • Programming Paradigm
    • Declarative vs Imperative
  • JPA
    • Template Page
  • PYTHON
    • Icecream
  • FASTAPI
    • Template Page
  • COMPUTER SCIENCE
    • Computer Architecture 101
      • 3 components of a computer
      • RAM vs ROM
      • CPU vs GPU
      • SIMD
      • Two's complement
      • Harvard Architecture vs. von Neumann Architecture
      • The structure of a CPU.
      • Instruction cycle (CPU operation method)
      • Instruction pipelining
      • Bus
      • Memory area
      • Memory hierarchy structure
        • Reason for using memory hierarchy structure
      • Cache memory
      • L1, L2, L3 Cache
      • Locality of reference (cache)
      • Fixed-point vs Floating-point
        • epresentation of infinity and NaN (Not a Number) in floating-point
      • RISC vs CISC
      • Hamming code
      • Compiler
      • Linking
      • Compiler vs Interpreter
      • Mutex vs Semaphore
      • 32bit CPU and 64bit CPU
      • Local vs Static Variable
      • Page
  • OS
    • Operating System 101
      • Operating system
        • The role of the operating system
        • The composition of the operating system.
      • Process
        • In Linux, are all processes except the initial process child processes?
        • Zombie process, orphan process
        • (Linux) Daemon process
        • Process address space
        • Where are uninitialized variables stored?
        • Determination of the size of the Stack and Heap
        • Access speed of Stack vs Heap
        • Reason for memory space partitioning
        • Process of compiling a process
        • sudo kill -9 $CURRENT_PID
      • Thread
        • Composition of a thread's address space
      • Process vs Thread
        • Creation of processes and threads in Linux
      • Multiprocessing
        • Web Browser
        • Implementation of multiprocessing
        • Application areas of multiprocessing
      • Multithreading
        • Application areas of multithreading
      • Interrupt
        • HW / SW Interrupt
        • Method of handling interrupts
        • Occurrence of two or more interrupts simultaneously
      • Polling
      • Dual Mode
        • Reason for distinguishing between user mode and kernel mode
      • System call
        • Differentiation between system calls
        • Types of system calls
        • Execution process of a system call
      • Process Control Block (PCB)
        • PCB의 구조
        • 쓰레드는 PCB를 갖고 있을까?
        • 프로세스 메모리 구조
      • Context switching
        • Timing of context switching
        • Registers saved during context switching
        • Context switching in processes
        • Context switching in threads
        • Difference between context switching in processes and threads
        • Information of the current process during context switching
      • Interprocess Communication (IPC)
        • Cases where IPC is used
        • Process address space in IPC Shared Memory technique
        • Types of IPC
    • Operating System Questions
      • Week1 OS & How Computer Systems Work
      • Week2(1/2) Process
      • Week2(2/2) Thread
      • Week3 CPU Scheduling
      • Week4 Process Synchronize
      • Week5 Virtual Memory
  • LINUX
    • Template Page
  • SERVER
    • Template Page
  • NETWORK
    • Network 101
      • https://www.google.com
      • TCP vs UDP
      • Http vs Https
      • TLS Handshake 1.2
      • HTTP Method
      • CORS & SOP
      • Web Server Software
    • Network Questions
      • Week1 Computer Network Basic
      • Week2(1/3) Application Layer Protocol - HTTP
      • Week2(2/3) Application Layer Protocol - HTTPS
      • Week2(3/3) Application Layer Protocol - DNS
      • Week3 Application Layer
      • Week4 Transport Layer - UDP, TCP
      • Week5 Network Layer - IP Protocol
    • Blocking, NonBlocking and Sync, Async
    • HTTP 0.9-3.0
  • DATABASE
    • Database Questions
      • Week1 DBMS, RDBMS basics
      • Week2 SQL
      • Week3 Index
      • Week4 Anomaly, Functional Dependency, Normalization
      • Week5 DB Transaction, Recovery
    • Normalization
      • 1st Normal Form
      • 2nd Normal Form
      • 3rd Normal Form
    • Ensuring Data Consistency, Atomicity and UX Optimization (feat.Firebase)
    • Redis: Remote Dictionary Server
    • Enhancing Query Performance - User list
  • DATA STRUCTURE
    • Array vs Linked List
    • Counting Sort
  • GIT, Github
    • git clone, invalid path error
  • INFRA
    • Template Page
  • AWS
    • Server Log Archive Pipeline
    • Image Processing using Lambda
  • DOCKER
    • Docker commands
    • Python Executable Environment
    • Docker and VM
  • docker-compose
    • Kafka, Multi Broker
  • KUBERNATES
    • !Encountered Errors
      • my-sql restarts
      • kafka producer: disconnected
    • Kubernetes Components
    • Helm
      • Helm commands
    • Pod network
    • Service network
      • deployment.yaml
      • services.yaml
    • Service type
      • Cluster IP
      • NodePort
    • service-name-headless?
    • kube-proxy
    • Template Page
  • GraphQL
    • Template Page
  • WEB
    • Template Page
  • Reviews
    • Graphic Intern Review
    • Kakao Brain Pathfinder Review
    • JSCODE 자바 1기 Review
  • 😁Dev Jokes
    • Image
      • Plot twist
      • Priorities
      • SQL join guide
      • Google is generous
      • Genie dislikes cloud
      • buggy bugs
      • last day of unpaid internship
      • what if clients know how to inspect
      • its just game
      • how i wrote my achievement on resume
      • self explanatory
      • chr(sum(range(ord(min(str(not))))))
Powered by GitBook
On this page
  • TLS 핸드쉐이크 1.2 기준
  • 1. ClientHello
  • 2. ServerHello
  • 3. Server Certificate
  • 4. ServerHelloDone
  • 5. ClientKeyExchange
  • 6. Master Secret 생성
  • 7. Session Key 생성
  • TLS 핸드쉐이크 완료 후의 통신
  • 질의
  • 질문: TLS 핸드셰이킹의 주요 목적은 무엇인가요?
  • 질문: TLS 핸드셰이킹 과정에서 인증서(Certificate)는 어떤 역할을 하나요?
  • 질문: Pre-Master Secret은 어떻게 사용되나요?
  1. NETWORK
  2. Network 101

TLS Handshake 1.2

TLS핸드쉐이크

PreviousHttp vs HttpsNextHTTP Method

Last updated 8 months ago

TLS 핸드쉐이크 1.2 기준

1. ClientHello

클라이언트가 서버와의 연결을 시작하기 위해 'ClientHello' 메시지를 보냅니다. Client Random(무작위 값)이 포함됩니다.

2. ServerHello

서버는 'ClientHello' 메시지를 수신한 후, 다음 단계로 'ServerHello' 메시지를 클라이언트에게 보냅니다. 이 메시지에는 서버가 선택한 암호화 방식과 무작위 바이트 문자열(Server Random)이 포함됩니다.

3. Server Certificate

서버는 'ServerHello' 메시지 이후에 'Certificate' 메시지를 전송합니다. 이 메시지에는 서버의 인증서가 포함되어 있습니다.

  • 서버 인증서: 공개 키, 서버 정보, 인증 기관(CA)의 서명

4. ServerHelloDone

서버는 'ServerHelloDone' 메시지를 전송하여 초기 핸드셰이크 메시지를 마무리합니다.

5. ClientKeyExchange

클라이언트는 Pre-Master-Secret 값을 생성하고, 서버에서 받은 공개 키로 암호화하여 'ClientKeyExchange' 메시지로 서버에 전송합니다.

  • Pre-Master-Secret: 클라이언트와 서버가 공유하는 비밀 값으로, 이를 통해 최종 암호화 키(Master Secret)를 생성합니다.

6. Master Secret 생성

클라이언트와 서버는 'Client Random', 'Server Random', 'Pre-Master-Secret' 값을 사용하여 'Master Secret'을 생성합니다. 이 값은 이후의 통신을 암호화하는 데 사용되는 세션 키를 생성하는 데 사용됩니다.

7. Session Key 생성

클라이언트와 서버는 'Master Secret' 값을 기반으로 세션 키를 생성합니다. 이 세션 키는 대칭 암호화 알고리즘을 사용하여 데이터를 암호화하고 복호화하는 데 사용됩니다.

TLS 핸드쉐이크 완료 후의 통신

핸드쉐이크가 완료된 후 클라이언트와 서버 간의 통신은 다음과 같은 방식으로 진행됩니다:

  • 암호화된 데이터 전송: 클라이언트와 서버는 세션 키를 사용하여 데이터를 암호화하고 전송합니다. 이로 인해 데이터가 도청되거나 변조되는 것을 방지할 수 있습니다.

  • 데이터 무결성 확인: 전송된 데이터는 메시지 인증 코드(MAC)를 사용하여 무결성을 확인할 수 있습니다. 이를 통해 데이터가 전송 중에 변경되지 않았음을 보장할 수 있습니다.

클라이언트와 서버가 세션 키를 사용하여 안전하게 통신하는 예를 간단히 설명하면 다음과 같습니다:

  1. 클라이언트가 서버에 데이터를 전송할 때:

    • 데이터를 세션 키로 암호화합니다.

    • 암호화된 데이터를 서버로 전송합니다.

  2. 서버가 클라이언트로부터 데이터를 수신할 때:

    • 수신된 데이터를 세션 키로 복호화합니다.

    • 복호화된 데이터를 처리합니다.

이 과정을 통해 클라이언트와 서버는 안전하게 데이터를 주고받을 수 있습니다.

질의

질문: TLS 핸드셰이킹의 주요 목적은 무엇인가요?

TLS 핸드셰이킹의 주요 목적은 클라이언트와 서버 간의 보안 통신을 설정하는 것입니다.

  • 암호화: 데이터가 전송 중에 도청되지 않도록 보호합니다.

  • 인증: 서버(및 경우에 따라 클라이언트)의 신원을 확인하여 신뢰할 수 있는 통신을 보장합니다.

  • 무결성: 데이터가 전송 중에 변경되지 않았음을 보장합니다.

질문: TLS 핸드셰이킹 과정에서 인증서(Certificate)는 어떤 역할을 하나요?

인증서는 서버(및 경우에 따라 클라이언트)의 신원을 확인하는 데 사용됩니다.

  • 공개 키(Public Key): 서버의 공개 키.

  • 서버 정보: 서버의 도메인 이름, 조직 정보 등.

  • 인증 기관(CA)의 서명: 신뢰할 수 있는 CA가 서버 인증서를 검증한 서명. 클라이언트는 이 인증서를 사용하여 서버의 신원을 검증하고, 서버의 공개 키를 얻어 이후 통신을 암호화하는 데 사용합니다.

질문: Pre-Master Secret은 어떻게 사용되나요?

Pre-Master Secret은 클라이언트가 생성하여 서버에 전송하는 비밀 값입니다. 클라이언트는 서버의 공개 키로 Pre-Master Secret을 암호화하여 서버에 보냅니다. 서버는 자신의 비밀 키로 이를 복호화합니다. 클라이언트와 서버는 Pre-Master Secret을 사용하여 'Client Random'과 'Server Random' 값을 결합하여 'Master Secret'을 생성합니다. 이 Master Secret을 기반으로 암호화된 세션에서 사용될 세션 키(Session Key)를 생성합니다.