openssl / openssl/openssl

Not possible to get the SAFI from IPAddressFamily

Open
#18,529 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue help wanted triaged: feature
Dominant language
C
Stars
30.8k
Forks
11.5k
Avg merge
10m
Merged PRs (30d)
1

Description

Reported by @botovq:

The public API exposes the AFI using X509v3_addr_get_afi(), but doesn't
expose the SAFI. The SAFI can only be fed into the API but not be read
from it. Another unfortunate thing about X509v3_addr_get_afi() is that it
uses the reserved AFI 0 as an in-band error. It does not care about the
reserved AFI 65535.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the public X509v3_addr_get_afi() API and the IPAddressFamily interfaces that accept SAFI values. Trace how AFI and SAFI are stored and retrieved, then add a way to read SAFI without using a reserved value as an error; update the relevant tests to cover ordinary and reserved AFI values.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
api, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.