# HSTS
<IfModule mod_headers.c>
Header set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" env=HTTPS
</IfModule>
# X-XSS-Protection
<IfModule mod_headers.c>
Header set X-XSS-Protection "1; mode=block"
</IfModule>
# X-Frame-Options
<IfModule mod_headers.c>
Header always append X-Frame-Options SAMEORIGIN
</IfModule>
# X-Content-Type nosniff
<IfModule mod_headers.c>
Header set X-Content-Type-Options nosniff
</IfModule>
Ran into a problem with a synology DS1815+ and though this could be helpful for others.
On the latest auto update to 6.0.1-3793 the iSCSI target(s) can become corrupt on the DS thus breaking the iscsi connection to the DS.
You can change the chap authentication info on the DS’s target and the globalsan iscsi initiator client, all you will see in the /var/log/iscsi.log is the following in regards to authentication.
Jun 6 00:23:20 syndisk kernel: [ 108.880447] iSCSI: iSCSI Login negotiation failed. Jun 6 00:23:25 syndisk kernel: [ 108.880447] iSCSI: iSCSI Login negotiation failed. Jun 6 00:23:33 syndisk kernel: [ 108.880447] iSCSI: iSCSI Login negotiation failed. Jun 6 00:23:45 syndisk kernel: [ 108.880447] iSCSI: iSCSI Login negotiation failed. Jun 6 00:23:55 syndisk kernel: [ 108.880447] iSCSI: iSCSI Login negotiation failed. Jun 6 00:24:08 syndisk kernel: [ 108.880447] iSCSI: iSCSI Login negotiation failed.
But you just changed passwords on the DS target and client connecting, how could this be? The config file is either corrupt or has become unstable and the act of deleting the target (saving the lun) and recreating the target , pointing at that old lun suddenly gets you back in business.
Steps to fix:
Delete current target on the DS (save the lun)
Create a new target (set password)and attach to the lun you just saved, verify pass on globalsan client.
And that’s it.
WordPress .htacess for cpanel ~dev environment.
For use when the site is installed @ domain.com but needs to be accessed from server.com/~username/ for testing.
# BEGIN WordPress
RewriteEngine On
RewriteBase /~username/
RewriteRule ^index\.php$ – [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
# END WordPress
Why is SSL important? It protects data in transit as it transverses over routers on the internet. From simple web pages to business transactions and purchases your data is worth something to someone.
In the age of shared and open WiFi it’s very easy for someone to ease drop on your traffic and possibly use the information collected to attack you and your assets. For the most part if you are looking at websites and forums the worries are advertisers watching you to hacker(s) watching to build a dossier for use in exploiting your assets.
With that said Lets Encrypt is a Free option to secure your data with a free certificate to be used in your web server. While only in beta, The project is showing amazing progress.
On Friday democratic senators announced plans to seek an investigation into Verizon Wireless’s use of dreaded “super cookie” after finding evidence these unique tracking codes could be used to track devices and thus people. With current usage levels this could potentially impact over 100 million devices. The fact that these super cookies are being used with no control by the end user should scary every end user and parent to the core!
Whom outside of Verizon has access to these codes? Are any data brokers selling a feature that would link super cookie to personal data for tracking habits?