WordPress: Prevent Copyright Violation

If you are a Hobby Blogger like me, you should ALWAYS take Snapshots for your Blog with your OWN Camera!

For „non professional“ use you can take the cheapest Camera or reuse old Smartphones of the Family.
Resolution at VGA Mode (640×480/800×600 less 250kb) is more enough than you need.
Faster you can’t save or earn Money, a Camera Snapshot needs less a second..

Don’t DO Rules:

  • Don’t download and share Images from public sites
  • Don’t take Snapshots on public Sites with a Snapshot Tool like gnome-screenshot
  • Don’t take Parts of Images from public sites
  • Don’t trust free Image Pools!! Most of them dont have rights of the Creators
  • Don’t visit public Photo Shares, cause most of them RECORD your IP for ABUSE!
  • Check your owned public Blogs and Wiki for uploaded Images by other users or friends monthly
  • Try to forbid the display of Images outside your Blog inside your Content by Admin Settings at your Blog!
  • Insert your Domain Name and Photo Creator Infos into your used Photos!
  • Use less Photos than you really need, cause the Search Engines can only filter Text by their bots and fast load is higher rated.

.. these rules saves your money for your Family.. happy Blogging

Major Webserver Setup Rules: The „must“ do!

If you want to setup a fresh secure Webserver then use this list

  • dont ever upload data, files, images on the Webserver who are classified as „secret“
  • setup daily full backup with Cron
  • view daily the system logs, auth, www, errors …
  • setup a local firewall with less opened ports 80,25 ..
  • setup daily automatic updates by cron
  • reduce the count of users who can login
  • use no logical usernames
  • force long passwords by rules min 15 digits
  • setup a daily load monitor by „uptime“ to log
  • setup a realtime network monitor by „iftop“
  • use „nmap“ as local portscan to test settings
  • remove unneeded software packages and services, less is more..
  • change monthly passwords forced by rules
  • upload only via encrypted SFTP and use Login Keys
  • copy hourly your Logs on /var/log to a other external place (scp/rsync) by cron
  • use ECC-RAM to have save RAM usage againts RAM attacks
  • use 2 HDD’s as Raid 1 and setup mail of root to post failures to your box
  • mount the Webserver root file system readonly, that no one can modify /etc
  • dont use Java, PHP, Tomcat, or other Adminpanels if you really need them!

I hope this rules help you to protect your Server..