Tag: Recently Read

In the report above, the reporter holds up a key to one of those small cable locks that comes with most firearms. It’s flimsier than a paper clip. She says “experts tell me that you should keep the key on … Read More

The post All Guns Are Always Unlocked: Guns for Beginners appeared first on The Truth About Guns.

via The Truth About Guns
All Guns Are Always Unlocked: Guns for Beginners

This week brought news that pro-gun people everywhere should be celebrating. I’m talking about the US Treasury’s announcement that they plan to remove a Democrat from the $20 bill, and replace him with a gun-toting, Republican freedom fighter named Harriet Tubman. I’ve seen Tubman depicted with a variety of different types of guns in paintings[…..]

The post US Treasury To Put Gun-toting Republican Freedom Fighter on the $20 Bill appeared first on AllOutdoor.com.

via AllOutdoor.com
US Treasury To Put Gun-toting Republican Freedom Fighter on the $20 Bill

 I’ve previously evaluated MariaDB’s 10.1 implementation of data encryption at rest (http://ift.tt/1QnLtVl), and recently did the same for Oracle’s implementation (http://ift.tt/1Ve0tg1) in their MySQL 5.7. First, here’s a walkthrough of enabling encryption for MySQL 5.7:1. Install keyring plugin.1a. Add the following to the [mysqld] section of /etc/my.cnf:… early-plugin-load=keyring_file.so1b. Restart the server:… service mysqld restart1c. Verify:… mysql> SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE ‘keyring%’; +————–+—————+ | PLUGIN_NAME | PLUGIN_STATUS | +————–+—————+ | keyring_file | ACTIVE | +————–+—————+2. Ensure innodb_file_per_table is on.2a. Check…. mysql> show global variables like ‘innodb_file_per_table’; +———————–+——-+ | Variable_name | Value | +———————–+——-+ | innodb_file_per_table | ON | +———————–+——-+2b. If OFF, add the following to the [mysqld] section of /etc/my.cnf, restart, and alter each existing table to move it to its own tablespace: innodb_file_per_table=ONGet list of available InnoDB tables: mysql>select table_schema, table_name, engine from information_schema.tables where engine=’innodb’ and table_schema not in (‘information_schema’);Run ALTER … ENGINE=INNODB on each above InnoDB tables: mysql><strong>ALTER</strong> TABLE [TABLE_SCHEMA].[TABLE_NAME] ENGINE=INNODB; Next, I walked through some testing.1. Create some data…. [root@localhost ~]# mysqlslap –concurrency=50 –number-int-cols=2 –number-char-cols=3 –auto-generate-sql –auto-generate-sql-write-number=10000 –no-drop2. Observe the mysqlslap.t1 table is not automatically encrypted. Unlike MariaDB’s implementation, there is not an option to encrypt tables by default.2a. Via the mysql client:… mysql> SELECT TABLE_SCHEMA, TABLE_NAME, CREATE_OPTIONS FROM INFORMATION_SCHEMA.TABLES WHERE CREATE_OPTIONS LIKE ‘%ENCRYPTION=”Y”%’; Empty set (0.05 sec)2b. Via the command line:(Install xxd if required.)… [root@localhost ~]# yum install vim-common… [root@localhost ~]# xxd /var/lib/mysql/mysqlslap/t1.ibd | grep -v “0000 0000″ | less … 0010dc0: 5967 4b30 7530 7942 4266 664e 6666 3143 YgK0u0yBBffNff1C 0010dd0: 5175 6470 3332 536e 7647 5761 3654 6365 Qudp32SnvGWa6Tce 0010de0: 3977 6576 7053 3730 3765 4665 4838 7162 9wevpS707eFeH8qb 0010df0: 3253 5078 4d6c 6439 3137 6a7a 634a 5465 2SPxMld917jzcJTe …3. Insert some identifiable data into the table:… mysql> <strong>insert</strong> into mysqlslap.t1 values (1,2,”private”,”sensitive”,”data”); Query OK, 1 row affected (0.01 sec) mysql> select * from mysqlslap.t1 where charcol2=”sensitive”; +———+———+———-+———–+———-+ | intcol1 | intcol2 | charcol1 | charcol2 | charcol3 | +———+———+———-+———–+———-+ | 1 | 2 | private | sensitive | data | +———+———+———-+———–+———-+ 1 row in set (0.02 sec)4. Observe this data via the command line:… [root@localhost ~]# xxd /var/lib/mysql/mysqlslap/t1.ibd | grep -v “0000 0000″ | less … 04fa290: 0002 7072 6976 6174 6573 656e 7369 7469 ..privatesensiti …5. Encrypt the mysqlslap.t1 table:… mysql> <strong>alter</strong> table mysqlslap.t1 encryption=’Y’; Query OK, 10300 rows affected (0.31 sec) Records: 10300 Duplicates: 0 Warnings: 06. Observe the mysqlslap.t1 table is now encrypted:6a. Via the mysql client:… mysql> SELECT TABLE_SCHEMA, TABLE_NAME, CREATE_OPTIONS FROM INFORMATION_SCHEMA.TABLES WHERE CREATE_OPTIONS LIKE ‘%ENCRYPTION=”Y”%’; +————–+————+—————-+ | TABLE_SCHEMA | TABLE_NAME | CREATE_OPTIONS | +————–+————+—————-+ | mysqlslap | t1 | ENCRYPTION=”Y” | +————–+————+—————-+6b. Via the command line:… [root@localhost ~]# xxd /var/lib/mysql/mysqlslap/t1.ibd | grep “private” [root@localhost ~]#6c. Observe snippet of the file:… [root@localhost ~]# xxd /var/lib/mysql/mysqlslap/t1.ibd | grep -v “0000 0000″ | less … 0004160: 56e4 2930 bbea 167f 7c82 93b4 2fcf 8cc1 V.)0….|…/… 0004170: f443 9d6f 2e1e 9ac2 170a 3b7c 8f38 60bf .C.o……;|.8`. 0004180: 3c75 2a42 0cc9 a79b 4309 cd83 da74 1b06 &amp;lt;u*B….C….t.. 0004190: 3a32 e104 43c5 8dfd f913 0f69 bda6 5e76 :2..C……i..^v …7. Observe redo log is not encrypted:… [root@localhost ~]# xxd /var/lib/mysql/ib_logfile0 | less … 23c6930: 0000 0144 0110 8000 0001 8000 0002 7072 …D……….pr 23c6940: 6976 6174 6573 656e 7369 7469 7665 6461 ivatesensitiveda 23c6950: 7461 3723 0000 132e 2f6d 7973 716c 736c ta7#…./mysqlsl …This is expected because the documentation (http://ift.tt/1Ve0tg1) reports encryption of files outside the tablespace is not supported: “Tablespace encryption only applies to data in the tablespace. Data is not encrypted in the redo log, undo log, or binary log.”ConclusionsI found in my testing of MariaDB’s implementation of data encryption at rest that there were still places on the file system that a bad actor could view sensitive data. I’ve found the same in this test of Oracle’s implementation. Both leave data exposed in log files surrounding the tablespace files.BonusAs a bonus to this walkthrough, during this testing, the table definition caught my eye:… mysql> show create table mysqlslap.t1\G *************************** 1. row *************************** Table: t1 Create Table: CREATE TABLE `t1` ( `intcol1` int(32) DEFAULT NULL, `intcol2` int(32) DEFAULT NULL, `charcol1` varchar(128) DEFAULT NULL, `charcol2` varchar(128) DEFAULT NULL, `charcol3` varchar(128) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1 ENCRYPTION=’Y’ 1 row in set (0.00 sec)As discussed in http://ift.tt/1QnLtVn, the MariaDB implementation does not include the “encrypted=yes” information in the table definition when tables are implicitly encrypted.I was curious what would happen if I did a mysqldump of this encrypted table and attempted to restore it to a nonencrypted server. DBAs expect mysqldump to create a portable file to recreate the table definition and data on a different version of mysql. During upgrades, for example, you might expect to use this for rollback.Here is my test. I first did the dump and looked inside the file…. [root@localhost ~]# mysqldump mysqlslap t1 > mysqlslap_t1_dump [root@localhost ~]# less mysqlslap_t1_dump … CREATE TABLE `t1` ( `intcol1` int(32) DEFAULT NULL, `intcol2` int(32) DEFAULT NULL, `charcol1` varchar(128) DEFAULT NULL, `charcol2` varchar(128) DEFAULT NULL, `charcol3` varchar(128) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1 ENCRYPTION=’Y’; <strong>INSERT</strong> INTO `t1` VALUES ( … ,(1,2,’private’,’sensitive’,’data’);As expected, that definition makes the dump less portable. The restore from dump is not completed and throws an error (this is not remedied by using –force):On a slightly older 5.7 version:… mysql> select version(); +———–+ | version() | +———–+ | 5.7.8-rc | +———–+ [root@centosmysql57 ~]# mysql mysqlslap < mysqlslap_t1_dump ERROR 1064 (42000) at line 25: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘ENCRYPTION=’Y” at line 7On a different fork:… MariaDB [(none)]> select version(); +—————–+ | version() | +—————–+ | 10.1.12-MariaDB | +—————–+ 1 row in set (0.00 sec) [root@maria101 ~]# mysql mysqlslap < mysqlslap_t1_dump ERROR 1911 (HY000) at line 25: Unknown option ‘ENCRYPTION’This doesn’t have anything to do with the encrypted state of the data in the table, just the table definition. I do like the encryption showing up in the table definition, for better visibility of encryption. Maybe the fix is to have mysqldump strip this when writing to the dump file.
via Planet MySQL
Data Encryption at Rest in Oracle MySQL 5.7

We’re are rapidly moving through day one of the Percona Live Data Performance Conference, and I’m surrounded by incredibly smart people all discussing amazing database techniques and technology. The depth of solutions represented here, and …
via MySQL Performance Blog
Percona Live 2016: Let Robots Manage your Schema (without destroying all humans)!

via Dilbert
Dilbert 2016-04-19

via kottke.org
Rival Chinese construction firms battle with bulldozers

Percona is excited to announce the launch of Percona Monitoring and Management Beta!
Percona Monitoring and Management (PMM) is a fully open source solution for both managing MySQL platform performance and tuning query performance. It allows DBAs and application developers to optimize the performance of the Database Layer. PMM is an on-premises solution that keeps all of your performance and query data inside the confines of your environment, with no requirement for any data to cross the internet.
Assembled from a supported package of “best of breed” open source tools such as Prometheus, Grafana and Percona’s Query Analytics, PMM delivers results right out of the box.
With PMM, anyone with database maintenance responsibilities can get more visibility for actionable enhancements, realize faster issue resolution times, increase performance through focused optimization, and better manage resources. More information allows you to concentrate efforts on the areas that yield the highest value, rather than hunting and pecking for speed.
PMM monitors and provides performance data for Oracle’s MySQL Community and Enterprise Editions as well as Percona Server for MySQL and MariaDB.
Download Percona Monitoring and Management now.
via Planet MySQL
Percona Monitoring and Management

Do you remember the Green Destiny sword from Crouching Tiger, Hidden Dragon. I didn’t. But that damascus steel blade finished with jade is so damn gorgeous and stunningly detailed that after seeing the guys at Baltimore Knife and Sword make it, I don’t think I’ll ever forget it again. The whole build process is so intensive. From how they alternate and stack different metals to folding the metal on top of each other to etching out the design and carving the jade and then adding the finishing touches, it’s one of the most beautifully intricate swords they’ve ever made.

SPLOID is delicious brain candy. Follow us on Facebook, Twitter, and YouTube.

via Gizmodo
Forging This Beautifully Intricate Sword Is So Damn Impressive

 We get to see the Earth in high definition every day, it’s true, but we’re limited to a certain ground-level point of view. Not so much the astronauts aboard the International Space Station. And they’ve just sent down a batch of stunning 4K footage of the Earth taken with their fancy RED Epic Dragon camera. Read More

via TechCrunch
ISS beams down 4K footage of Earth shot with the RED Epic Dragon