Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Self signed certificates

Open
#384 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

Start with isteamnetworkingsockets.h and the certtool output described in the issue, then trace SetCertificate() and STEAMNETWORKINGSOCKETS_HARDCODED_ROOT_CA_KEY. Clarify how self-signed certificates, private keys, and binary certificate data are configured, and provide a basic setup example or documentation that resolves these questions.

Written by the indexing model from the issue text.

Description

I'm trying to figure out how to use self signed certificates to prevent MITM. I managed to create a cert via the certtool (the output includes other metadata and shows the cert in base64 - why doesn't it just export to a binary file as that's what SetCertificate() expects anyway? Or am I wrong here?) and then hardcoding the key with STEAMNETWORKINGSOCKETS_HARDCODED_ROOT_CA_KEY (this is required because it's self signed right?). But now it's complaining about it missing a private key. I can't really find how to set this to be honest. It seems like the private key could either be part of the cert (I can't find how to embed this) or setting it manually, but I can't find the API for this.

Any guidance is much appreciated. Perhaps some documentation on the subject wouldn't be a bad idea either. The documentation in isteamnetworkingsockets.h is pretty good in general, but there's very little about setting up encryption using self signed keys, which is pretty necessary for any serious game. Unless I'm just looking in the wrong place.

A basic example on how to set this up would be absolutely fantastic.

Dominant language
C++
Stars
10k
Forks
747
Avg merge
5d 19h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ValveSoftware/GameNetworkingSockets

All issues in ValveSoftware/GameNetworkingSockets

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.