Description
I was using OpenSSL and ps. This produced unnecessary telemetry
script name: base.sh
Steps To Reproduce
Steps to reproduce the unexpected behavior:
Execute any shell script .
core_generate_job_id() {
# Use openssl to generate random hex string for job tracking
# Fallback to date-based ID if openssl not available
if command -v "$CMD_OPENSSL" > /dev/null 2>&1; then
$CMD_OPENSSL rand -hex 4 2>/dev/null || {
# Fallback: use timestamp and process ID
$CMD_PRINTF "%08x" "$(($(date +%s) % 4294967296))"
}
else
# Fallback: use timestamp and process ID
$CMD_PRINTF "%08x" "$(($(date +%s) % 4294967296))"
fi
}
Expected behavior
All tools used by base should be singed by Apple
Screenshots

Description
I was using OpenSSL and ps. This produced unnecessary telemetry
script name: base.sh
Steps To Reproduce
Steps to reproduce the unexpected behavior:
Execute any shell script .
core_generate_job_id() {
$CMD_PRINTF "%08x" "$ (($(date +%s) % 4294967296))"
$CMD_PRINTF "%08x" "$ (($(date +%s) % 4294967296))"
# Use openssl to generate random hex string for job tracking
# Fallback to date-based ID if openssl not available
if command -v "$CMD_OPENSSL" > /dev/null 2>&1; then
$CMD_OPENSSL rand -hex 4 2>/dev/null || {
# Fallback: use timestamp and process ID
}
else
# Fallback: use timestamp and process ID
fi
}
Expected behavior
All tools used by base should be singed by Apple
Screenshots
