Rich – techish.net

Cisco Configuration Professional Installation Notes

To install the Cisco Configuration Professional (CCP) software for the Catalyst 2960X/XR platform from a .tar file, you’ll need to extract and set it up on the switch’s flash memory. Here’s a step-by-step guide to install the .tar file on your Cisco 2960X switch:

What You’ll Need

The .tar file (e.g., ccp-c2960x.tar)
TFTP server (or FTP/USB depending on your method)
Console or SSH access to the switch

Step 1: Transfer the `.tar` File to the Switch

Use a TFTP server (like tftpd32 or SolarWinds TFTP) to upload the .tar file to the switch’s flash.

From the switch CLI:

copy tftp: flash:

You’ll be prompted:

Address or name of remote host []? 192.168.1.100  <-- your TFTP server
Source filename []? ccp-c2960x.tar
Destination filename [ccp-c2960x.tar]? <Enter>

Step 2: Extract the `.tar` File

Once the file is on the switch, extract it with:

archive extract flash:ccp-c2960x.tar flash:

This will unpack the files into a directory (e.g., ccp-web) inside flash.

Step 3: Enable the Web Interface

To use Configuration Professional, you need:

HTTP/HTTPS server enabled
A working VLAN interface with an IP address
Authentication (username/password)

Commands:

conf t
ip http server
ip http secure-server
username admin privilege 15 secret YourSecurePassword
interface vlan1
 ip address 192.168.1.1 255.255.255.0
 no shutdown
exit
ip default-gateway 192.168.1.254  ! Adjust as needed
end
write memory

🔗 Step 4: Access the Web Interface

Open a browser and go to:

http://192.168.1.1

https://192.168.1.1

You should see the Configuration Professional (CP Express) interface.

🧹 (Optional) Clean Up and Set as Default Web UI

If you want this web interface to load automatically on boot:

conf t
ip http path flash:ccp-web
end
write memory

And if you’re done, you can remove the .tar file to save space:

delete flash:ccp-c2960x.tar

Blocking AI Scrapers Using .htaccess

You can place the following into your .htaccess to have it return an HTTP 403 if the User Agent is matched.

Deleting Files from the Linux Kernel

The NSA has been directed by an executive order from the President to remove internal and external content with the following 27 words.

Anti-Racism
Racism
Allyship
Bias
DEI
Diversity
Diverse
Confirmation Bias
Equity
Equitableness
Feminism
Gender
Gender Identity
Inclusion
Inclusive
All-Inclusive
Inclusivity
Injustice
Intersectionality
Prejudice
Privilege
Racial Identity
Sexuality
Stereotypes
Pronouns
Transgender
Equality

This could pose an issue for content that may contain words or phrases relating to cyber-security, technology, etc.

I imagine this is how it is going down:

grep -rlFf wordlist.txt . | xargs rm -f

Could just get a list of unique files that contain one of the banned words and do something with it too.

grep -rFof wordlist.txt . >files_to_remove.txt

What about the Linux Kernel?

So, let’s see what the Linux Kernel would need to delete.

grep -rFi -of wordlist.txt linux-6.13.2/ >files_to_remove.txt

awk -F: '{print tolower($2)}' files_to_remove.txt | awk '{count[$1]++} END {for (word in count) print word, count[word]}' | sort -k2 -nr > word_frequencies.txt

Get unique files:


cut -d':' -f1 files_to_remove.txt | sort | uniq > uniq_files.txt

Count unique files to delete:

cut -d':' -f1 files_to_remove.txt | sort | uniq | wc -l

Results

Unique files to delete: 5923 of 87174 total files.

Top 10 Filetypes to be Deleted

Extension	Count	Percentage of Unique Files
.c	2764	46.7%
.h	1472	24.9%
.dts	423	7.1%
.dtsi	335	5.7%
.rst	301	5.1%
.yaml	240	4.0%
.S	75	1.3%
.txt	62	1.0%
.sh	55	0.9%
.json	36	0.6%
Other	160	2.7%

C-related files (.c, .h) dominate, making up about 71.6% of the unique files.
Device Tree Source (.dts, .dtsi) files make up 12.8%, suggesting embedded systems or Linux kernel development.
Configuration & documentation files (.rst, .yaml, .txt, .json) total ~11.6%, showing structured data and documentation usage.
Shell scripts (.sh) and Assembly (.S) make up a smaller portion (2.2%), likely for build or automation scripts.

Categorized Files

Code Files (.c, .h, .S, .sh): 4,366 files (73.7%)
Configuration (.yaml, .json, .dts, .dtsi): 1,034 files (17.5%)
Documentation (.rst, .txt): 363 files (6.1%)
Other/Miscellaneous: 160 files (2.7%)

Word frequencies across all files:

bias 33121
dei 9472
privilege 3899
diversity 837
inclusive 724
inclusion 232
equality 88
diverse 50
gender 31
prejudice 17
pronouns 2

FTC Mobile Health Apps Tool

Privacy and security are important considerations for any app—and especially apps that collect and share consumers’ health information. As you design, market, and distribute your mobile health app, think about which U.S. federal laws may apply. Check out this interactive tool to help you navigate laws and rules that may apply to you or your app.

https://www.ftc.gov/business-guidance/resources/mobile-health-apps-interactive-tool

InvoiceNinja – Mailer problem

I maintain an InvoiceNinja instance and an error was reported when sending mail.

Check the logs in storage/logs/laravel.log I see there is an error:

Mailer Problem: scheme is not supported; supported schemes for mailer "smtp" are: "smtp", "smtps"

First, I checked my .env and saw MAIL_MAILER=smtps, so I dug into config/mail.php to have a look.

There was no scheme in the mailers.smtp, so I added 'scheme' => 'smtps', to it:

    'mailers' => [
        'smtp' => [
            'scheme' => 'smtps',
            'transport' => 'smtps',

I cleared the config cache using php artisan clear:config.

Now invoices are sending.