cybersecurity · beginner · ~15 min · safe pentest lab

Why you don't scan public targets

Internalise the ethical and legal boundary before touching tools.

Challenge

Write a main that prints the pentest-scope policy to stdout. The first control against accidentally illegal scanning is internal: state the rules out loud.

Task

From main, print exactly these three lines to stdout, each ended with a newline:

I will only test systems I am explicitly authorised to test.
Unauthorised scanning is illegal under laws like the UK Computer Misuse Act and US CFAA.
All exercises here target 127.0.0.1 or static text fixtures only.

Input

None — the program takes no input.

Output

The three lines above, in order, each followed by \n. No extra leading or trailing output.

Example

(no input)   ->   the three policy lines, each ending with a newline

Edge cases

  • The output is matched exactly: no extra blank lines, no missing trailing newline on the last line.

Input format

None — the program takes no input.

Output format

Three exact policy lines on stdout, each terminated by a newline.

Constraints

Output must match exactly — no extra or missing newlines.

Starter code

#include <stdio.h>

int main(void) {
    /* TODO: print the three policy lines */
    return 0;
}

Solve this exercise in the browser editor — compile and run against the test harness, no setup required.