perl-security

Topics in the source

• Perl Security Patterns
• When to Activate
• How It Works
• Taint Mode
• Enabling Taint Mode
• Untainting Pattern
• Input Validation
• Allowlist Over Blocklist

Comprehensive security guidelines for Perl applications covering input validation, injection prevention, and secure coding practices. Handling user input in Perl applications Building Perl web applications (CGI, Mojolicious, Dancer2, Catalyst) Reviewing Perl code for security vulnerabilities Performing file operations with user-supplied paths Executing system commands from Perl Writing DBI database queries Start with taint-aware input boundaries, then move outward: validate and untaint inputs, keep filesystem and process execution constrained, and use parameterized DBI queries everywhere. The examples below show the safe defaults this skill expects you to apply before shipping Perl code that touches user input, the shell, or the network. Perl's taint mode (-T) tracks data from external sources and prevents it from being used in unsafe operations without explicit validation. Catastrophic backtracking occurs with nested quantifiers on overlapping patterns. Use File::Temp for temporary files (tempfile(UNLINK => 1)) and flock(LOCKEX) to prevent race conditions. Also use Capture::Tiny for capturing stdout/stderr from external commands safely. Use constant-time comparison when verifying

This is an excerpt. Refer to the complete source and its current requirements.