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

Support P2P Connections with Custom Signaling Between Steam and OSS Library Versions

Open
#392 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
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

Research direction

Start with CSteamNetworkConnectionBase::AllowRemoteUnsignedCert and the NetInterfaceGNS.cpp:188 warning path. Trace how networking configuration variables are defined and applied, focusing on the proposed k_ESteamNetworkingConfig_P2P_AllowWithoutAuth setting for non-SDR connections. Done means the setting controls whether these unsigned P2P connections are accepted between Steam and OSS library versions.

Written by the indexing model from the issue text.

Description

As a user, I would like to establish P2P connections using custom signaling between the Steam version of the library and the OSS (Open Source Software) version.

However, the Steam version currently disallows unauthenticated/unsigned P2P communication, which prevents this interoperability.

EUnsignedCert CSteamNetworkConnectionBase::AllowRemoteUnsignedCert()
{
	#ifdef STEAMNETWORKINGSOCKETS_OPENSOURCE
		// We don't have a cert authority.  We probably ought to make this customizable
		return k_EUnsignedCert_Allow;
	#else
		return k_EUnsignedCert_Disallow;
	#endif
}
[11:35:39.700] [warning] NetInterfaceGNS.cpp:188 - Failed to start accepting P2P connect request from str:393FD8571292475BB1128DCC7D73745 on vport 0; Unsigned certs are not allowed

Ideally it could be controlled with new config var for non-SDR connections.

k_ESteamNetworkingConfig_P2P_AllowWithoutAuth
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.