radareorg/radare2

Support base64: on more commands

Open

#14,324 opened on Jun 16, 2019

View on GitHub
 (5 comments) (0 reactions) (1 assignee)C (23,826 stars) (3,229 forks)batch import
FEEDBACK WANTEDHacktoberfestgood first issuerefactorshell

Description

We should support base64 namings in flag commands too, not just in CC/CL, the realname must be kept as is, but the flag name must be filtered. And probably do something generic.

  • f base64:xxx
  • afn base64:xxx
  • CC base64:xxx (we have CCu only for now)
  • <base64: for raw binary input?

... cant think of a need for this on other commands. anyone?

Contributor guide

Tech stack
c
Domain
securitycli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of radare2 commandsC programmingBase64 encoding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the current base64 handling in CC/CL commands (e.g., in libr/core/cmd flag.c or similar). Understand how flag names are processed and filtered. Then implement base64 decoding for flag names in the f, afn, and CC commands, ensuring real names remain unchanged. Consider if a generic helper function can be created. Check the issue comments for any additional context or previously suggested approaches.