Japan: Abe Assassinated with Electrically Fired Homemade, Double-Barreled Gun!?

https://www.ammoland.com/wp-content/uploads/2022/07/Homemade-Gun-Abe-Assassination-Twitter-731–500×337.jpg

The homemade gun was used to assassinate former PM Abe in Japan. IMG Twitter

U.S.A.-(AmmoLand.com)-— Former Japanese Prime Minister Shinzo Abe was assassinated with a homemade gun on July 8th, 2022, in the Japanese city of Nara.

From video of the event, it appears the assassin fired his weapon at Abe from a distance of 20 to 30 feet. The two distinct shots were fired about a second apart and produced copious amounts of white smoke.

Early reports were of wounds to the neck and chest. It is unknown what sort of projectiles were used in the homemade weapon.

Such firearms are extremely easy to make for anyone with a rudimentary ability to use hand tools.

This correspondent made several similar homemade, electrically actuated, multishot, muzzleloading black powder firearms 40 years ago. Electrical firing mechanisms are much easier to make than percussion systems used in modern firearms. A simple switch is a trigger for each barrel. Batteries supply the power to ignite each charge.  If you want multiple shots, multiple barrels are used. A nine-volt battery worked well in my 40-year-old experiments, as did a four-pack of AA batteries.

A simple galvanized water pipe is plenty strong to withstand black powder pressures for a few shots. The firearm used in the assassination appears to be close to a 12 gauge bore size. Larger bores and projectiles create sufficient energies at the lower velocities on such firearms.

The propellants for such guns are easily made at home. Many high school students successfully made black powder in my youth. Fireworks can be disassembled as another source of propellant. It has been reported that people in prisons and the former Soviet Union used ground-up match heads as a propellant. Making propellant is much more dangerous than making the guns.

Japan Abe Assassinated with Electrically Fired Homemade Double Barreled Gun
Japan Abe Assassinated with Electrically Fired Homemade Double-Barreled Gun

This correspondent disagrees with professor Daniel Foote of Tokyo.

From Bloomberg.com:

“This actually shows the extent that Japan gun laws are working,” said Daniel Foote, a professor at the University of Tokyo specializing in law and society. “Very few people have the ability to create such a weapon.”

It is unlikely the professor has ever done the experimental work to make such weapons. Forty years ago, this correspondent was able to make a four-shot repeater from 12 dollars of materials obtained from a hardware store and Radio Shack, using about 12 hours’ worth of labor. In order to be effective with such weapons, testing and practice is necessary. It appears the former Naval officer did the preparation required.

From the newyorkpost.com:

Police found several possible explosives during a raid on Yamagami’s home, and the suspect confessed that he had “manufactured multiple pistols and explosives so far,” NHK said.

Other local reports said that he told cops he initially planned to blow up Abe, but decided to instead build a gun because he feared a bomb was less reliable.

Some sources are saying the assassination occurred at 10 feet. In the video referenced above, the distance appears to be 20 to 30 feet.  There did not appear to be any sights on the homemade firearm. Today, some sort of laser pointer would be easy to install and bore sight. But NO mention of a laser has been made to this correspondent’s knowledge.

The successful assassination of former Japanese PM Abe, with a homemade firearm in a country with some of the most extreme firearms restrictions on the planet, shows how difficult it is to regulate what is essentially a 15th-century technology.


About Dean Weingarten:

Dean Weingarten has been a peace officer, a military officer, was on the University of Wisconsin Pistol Team for four years, and was first certified to teach firearms safety in 1973. He taught the Arizona concealed carry course for fifteen years until the goal of Constitutional Carry was attained. He has degrees in meteorology and mining engineering, and retired from the Department of Defense after a 30 year career in Army Research, Development, Testing, and Evaluation.

Dean Weingarten

AmmoLand Shooting Sports News

How Shovels are Made

https://theawesomer.com/photos/2022/07/how_shovels_are_made_t.jpg

How Shovels are Made

Link

Mega Process takes us on a tour of Zion Industrial Co., which apparently is the last shovel factory in South Korea. The laborious process starts with freshly-cut oak trees, milling the timber into boards, sanding until round, trimming, then splitting, steaming, and bending the wood to hold the shape for its handle.

The Awesomer

How Shovels are Made

https://theawesomer.com/photos/2022/07/how_shovels_are_made_t.jpg

How Shovels are Made

Link

Mega Process takes us on a tour of Zion Industrial Co., which apparently is the last shovel factory in South Korea. The laborious process starts with freshly-cut oak trees, milling the timber into boards, sanding until round, trimming, then splitting, steaming, and bending the wood to hold the shape for its handle.

The Awesomer

Encrypting Laravel Eloquent models with CipherSweet


Encrypting Laravel Eloquent models with CipherSweet

July 1st, 2022

CipherSweet is a backend library developed by Paragon Initiative Enterprises for implementing searchable field-level encryption. It can encrypt and decrypt values in a very secure way. It is also able to create blind indexes. A blind index can be used to perform some targeted searches on the encrypted data. The indexes themselves are unreadable by humans.

We’ve just released laravel-ciphersweet. This package is a wrapper over CipherSweet, which allows you to easily use it with Laravel’s Eloquent models.

Preparing your model and choosing the attributes that should be encrypted#

Add the CipherSweetEncrypted interface and UsesCipherSweet trait to the model that you want to add encrypted fields to.

You’ll need to implement the configureCipherSweet method to configure CipherSweet.

use Spatie\LaravelCipherSweet\Contracts\CipherSweetEncrypted;
use Spatie\LaravelCipherSweet\Concerns\UsesCipherSweet;
use ParagonIE\CipherSweet\EncryptedRow;
use Illuminate\Database\Eloquent\Model;

class User extends Model implements CipherSweetEncrypted
{
    use UsesCipherSweet;
    
    public static function configureCipherSweet(EncryptedRow $encryptedRow): void
    {
        $encryptedRow
            ->addField('email')
            ->addBlindIndex('email', new BlindIndex('email_index'));
    }
}

Generating an encryption key#

We’ve also added a small helper command to the package that allows you to generate a new key in a way that is suggested by Paragon Initiative Enterprises.

This encryption key is used to encrypt your values.

php artisan ciphersweet:generate-key

Encrypting model attributes#

Once everything is set up, you can start encrypting your model values:

php artisan ciphersweet:encrypt <your-model-class> <generated-key>

The command will update all the encrypted fields and blind indexes of the model.

If you have a lot of rows, this process can take a long time since encryption is a resource intensive operation. Don’t worry if it times out for some reason, the command is always restartable and only tries to encrypt models when it’s needed.

Updating your .env file#

After the fields have been encrypted, you should add the generated CipherSweet key to your .env file.

CIPHERSWEET_KEY=<YOUR-KEY>

The key will be used by your application to read encrypted values.

Searching on blind indexes#

Even though values are encrypted, you can still search them using a blind index. The blind indexes will have been built up when you ran the command to encrypt the model values.

Our package provides a whereBlind and orWhereBlind scope to search on blind indexes.

The first parameter is the column, the second the index name you set up when calling ->addBlindIndex, the third is the raw value, the package will automatically apply any transformations and hash the value to search on the blind index.

In closing#

CipherSweet is a very powerful library, and our package makes it very approachable. Of course, be very sure about what columns actually need encrypting, and don’t overdo it, encryption is resource intensive and comes with some downsides.

We’ll be using this package sparingly in the development of our upcoming SaaS mailcoach.cloud to protect the personal information that will be stored by our users.

Of course, laravel-ciphersweet isn’t the first package that our team has built. On our company website, check out all of our open source packages in this long list. If you want to support us, consider picking up any of our paid products.

Laravel News Links

Here’s What Separating and Recycling an Entire Car Looks Like

https://s3files.core77.com/blog/images/1296465_81_116224_PliTBUJ7m.jpg

Do you have any idea what this crazy thing is?

So that’s a vehicle drainage rack (!) made by Seda, an Austrian company that makes machines used to dismantle automobiles. You’ve probably seen a video of a car being crushed. What you may not have realized is that prior to crushing it, the cars must be drained of all fluids (gas, oil, brake fluid, radiator fluid, etc.). Dismantling technicians cut into hoses, then the vehicle is lifted and tilted by the rack to drain every last drop of toxic goodness.

I wanted to find video of this in action, and got more than that: Here Seda demonstrates, in about 90 seconds, how to dismantle and recycle an entire car using their machines, including the draining rack:

Seeing the wiring alone was staggering. I’d heard that modern cars have nearly one mile of wiring in them, but seeing it all pulled out and placed in that bin was really something.

Core77

Encrypt and Decrypt Eloquent Model Fields in Laravel Apps

https://laravelnews.imgix.net/images/laravel-ciphersweet.png?ixlib=php-3.3.1

Laravel Ciphersweet is a package by Spatie to integrate searchable field-level encryption in Laravel applications. The package’s readme explains the problem Ciphersweet can help solve as follows:

In your project, you might store sensitive personal data in your database. Should an unauthorised person get access to your DB, all sensitive can be read which is obviously not good.

To solve this problem, you can encrypt the personal data. This way, unauthorized persons cannot read it, but your application can still decrypt it when you need to display or work with the data.

This package is a wrapper for Ciphersweet to integrate its features into Laravel models easily. Here’s an example of a model from the readme’s setup instructions that illustrates what a model looks like using Ciphersweet:

1use Spatie\LaravelCipherSweet\Contracts\CipherSweetEncrypted;

2use Spatie\LaravelCipherSweet\Concerns\UsesCipherSweet;

3use ParagonIE\CipherSweet\EncryptedRow;

4use Illuminate\Database\Eloquent\Model;

5 

6class User extends Model implements CipherSweetEncrypted

7{

8 use UsesCipherSweet;

9 

10 public static function configureCipherSweet(EncryptedRow $encryptedRow): void

11 {

12 $encryptedRow

13 ->addField('email')

14 ->addBlindIndex('email', new BlindIndex('email_index'));

15 }

16}

This allows you the encrypt a user’s email to keep it safe from unauthorized people reading the data, but give you the ability to decrypt the data to display it or work with it.

Once you have configured this package and set up a model, you can search encrypted data in the database using blind indexes:

1$user = User::whereBlind('email', 'email_index', 'rias@spatie.be');

This package also aids in generating encrypting keys and encrypting model attributes to speed up integration with Ciphersweet.

I want to point out that you should not use this package blindly without understanding the ins and outs of the use case you are trying to solve. You can learn more about CipherSweet on this page, which has many linked resources.

CipherSweet also has PHP-specific documentation to help get you up to speed with the underlying PHP package.

I would also recommend reading Rias’ post, Encrypting Laravel Eloquent models with CipherSweet.

To get started with this package, check it out on GitHub at spatie/laravel-ciphersweet.

Laravel News

The FBI Said This is the Best Handgun (And Why They’re Wrong)

In response to numerous inquiries from local law enforcement departments, the FBI undertook a comprehensive evaluation of the sidearms available in 1987 (most of which are still made today) to determine which pistol was the best. Thirteen of the most talented instructors that the Federal Bureau of Investigation had to offer all met at a […]

Read More …

The post The FBI Said This is the Best Handgun (And Why They’re Wrong) appeared first on The Firearm Blog.

The Firearm Blog

Darktable celebrates its 10-year anniversary with substantial version 4.0.0 update

https://3.img-dpreview.com/files/p/E~C0x0S1404x1053T1200x900~articles/6340644378/screenshot_lighttable.jpeg

Just about a year after releasing darktable 3.6, the darktable team has announced darktable 4.0.0. The update celebrates 10 years of darktable offering photographers open source raw image editing. The major release adds many new features to the open source photography workflow app and raw image editor, including color and exposure mapping, filmic v6, guided Laplacian highlight reconstruction, a new perceptually uniform color space, revamped user interface, performance improvements, and much more.

Color and exposure mapping comprise a new feature in the ‘exposure’ and ‘color calibration’ modules that allows you to define and save a specified target color/exposure for the color pickers. You can match any source object against an arbitrary target color. You can use this tool to perform white balance adjustments against non-gray objects of known color, or ensure consistent color across a batch of images.

Filmic v6 includes a new color science. Darktable writes, ‘This change removes the mandatory desaturation close to medium white and black and replaces it with a true gamut mapping against the output (or export) color space. This allows for more saturated colors, notably in blue skies.’ Darktable 4.0.0 now includes a ‘fully-sanitized color pipeline’ from input (color calibration), creative changes (color balance RGB) and through to output (filmic v6).

Within the ‘highlight reconstruction’ module is a new ‘guided Laplacian’ method. This uses a ‘multi-scale wavelet scheme to extract valid details from non-clipped RGB channel(s)’ and ‘propagates the color gradients from neighboring valid regions using edge-aware color diffusion.’ The team writes that this feature promises to limit color bleeding through edges, such as green leaves bleeding color into a reconstructed blue sky. This method is only available for images captured with a Bayer sensor, so Fujifilm X-Trans users are out of luck here.

Darktable 4 introduces the darktable Uniform Color Space 2022 (darktable UCS 22). It’s a perceptually uniform color space built using psychoperceptual experimental data that was gathered for artistic saturation changes. What’s this actually mean? Darktable UCS 22 ‘ uses a brightness-saturation scheme that compensates for the Helmholtz-Kohlraush effect (accounting for the contribution of colorfulness in perceived brightness) and allows an efficient gamut-mapping against pipeline RGB at a constant brightness. It will make the saturation control in color balance RGB better behaved.’ You can learn a bit more about the Helmholtz-Kohlraush effect in the latter half of the video below.

The user interface has been completely revamped to improve the overall look and consistency. Padding, margins, color, contrast, alignment and icons have been reworked throughout the application. Collapsible sections within modules have been redesigned to improve functionality, plus channel mixer RGB, exposure and color calibration modules include new collapsible sections. The vignetting module has been split into two sections. Superfluous sections have been removed in ‘crop’ and ‘white balance’ tools. The default theme is now Elegant Gray, which is the recommended choice of the darktable team.

The app’s performance and OpenCL settings have been optimized, so performance is more tunable by the user and should be improved overall. There are many more other changes, including a color glossary, new contrast parameters, a new ‘collection filters’ module, improved search, improved export options, improved shortcuts when using sliders, a new raw exposure function, and more. Plus, there are many new bug fixes in the latest update. For the full details, visit darktable.

Darktable 4.0.0 is available now for Linux, macOS and Windows. At that link, you can also download the software’s source code. If you would like to give darktable 4.0.0 a try but don’t know where to start, there’s a very detailed user manual available here.

Articles: Digital Photography Review (dpreview.com)

This is the most based pro-gun campaign ad I’ve ever seen

https://media.notthebee.com/articles/62c5f66420cd962c5f66420cda.jpg

Former ASU football standout and inspirational speaker Jerone Davison is running for Congress on the Republican ticket in Arizona. So far, it looks like Mr. Davison will be pulling ZERO punches in this fight.

Not the Bee

4 Errors You Should Avoid While Handling Money With PHP

https://dev.to/social_previews/article/1119335.png



1. Not knowing which datatype to use in MySQL

I once heard it’s better to use integers when handling financial data. You convert a price like €10 to its lowest unit (cents in this case). This way you end up using 1000 as the amount to work with. This way you avoid the floating-point problem. The floating-point problem is best shown by typing the following in your Google Chrome console:

0.1 + 0.2 > 0.30000000000000004

If you want to learn more about this problem visit this website. Working with integers is dramatic for readability (how much is 13310 in euros?). The disadvantage of working with integers is also that it has a limit of 2147483647 which is roughly € 21,474,836.47. Although with the euro you probably wouldn’t run into this issue quickly but with the Vietnamese Dong, this wouldn’t work. Learnings: use decimals (not floats!) in MySQL to store monetary values. Depending on how many decimals you need decimal(15,2) oftentimes is enough.



2. Not having something to fact-check the numbers

Imagine we have a shopping cart where there’s 1 product for € 100, the VAT of € 21 and a total of € 131. The first time you’re sharp and you immediately see your mistake. After the 100th time, you start to be blind to those mistakes.

That’s why you need something to fact-check the numbers if they’re correct. I’ve created a Google Sheet for me and my team where we can all fact-check this. Especially if you work with people who test your product but don’t have access to the code this is crucial. How should they know if the price displayed is the correct one?



3. Not splitting the price into all the components

Every part of a price should be stored separately. If not, there’s no way to reproduce the components if you need to later on. So save the VAT amount, the discount amount, the base price, and the total all separately. Big chance there are gonna be more price components in your app in the future.



4. Using foreign keys in the ‘orders’ table

One of my dumbest mistakes. I had an ‘orders’ table where all the orders of an e-commerce store were placed. Unfortunately, it had a reference to the actual products which I got the product price from. Everything was fine until one of the product prices changed and older orders were affected by it😅

I’ve made many mistakes even though I have been developing applications for years. But without resistance, there’s no growth, so I tend to share my mistakes so you might prevent them.

I’m planning on writing an ebook on developing applications where you work with money. If you’re interested you might wanna subscribe to get free access to the first chapter.

Subscribe here

Laravel News Links