2017 August 10 | AIVAnet

10

Aug

Meet TIKAD: the gun-toting drone that can aim, fire, and compensate for recoil

Why it matters to you

Sending soldiers on foot into some of the world’s toughest warzones isn’t always the best solution. TIKAD’s creators hope this drone could provide a solution.

Have you ever looked at a drone and thought, “Yeah, that’s kind of neat, but I sure wish it came with some mounted firearms?” If so, you may be interested to hear about the TIKAD: a new drone that’s described by its Florida-based creators Duke Robotics as the “Future Soldier.”

Intended for military deployment, TIKAD is an unmanned aerial vehicle (UAV) designed to replace boots on the ground in some of the toughest warzones on the planet. It weighs 110 pounds (50kg), can fly at an altitude of anywhere from 30 – 1,500 feet and — oh yes — did we mention that it can sport a plethora of semi automatic weapons, and a 40mm grenade launcher for good measure?

“As a former Special Mission Unit commander, I have been in the battlefield for many years, and more than once I hoped that a different solution other than sending in the troops existed,” CEO Raziel Atuar told Digital Trends. “At Duke Robotics, we wanted to create something that would be a game changer in future battles, [and] that could save lives of troops, as well as uninvolved civilians, in the combat zone.”

Atuar says that, as classic army versus army confrontations on battlefield have become increasingly rare, tools intended for guerilla warfare have become more important than ever. That’s where the requirement for a drone that’s capable of firing small arms from the air comes into play. TIKAD features plenty of smart tech, but perhaps its smartest tools are its high levels of accuracy and a proprietary robotic stabilization system that enables it to absorb the recoil of its mounted gun as it’s fired. (This stabilization platform can also be used as a standalone unit for snipers on the ground.)

“TIKAD is ready to be delivered,” Atuar continued. “We are in the process of implementing an initial order from the Israeli Ministry of Defense, and we are in contact with selected governments as potential customers. For obvious reasons, our government customers are highly sensitive regarding this type of information, and it is up to them to decide if and when to share more information [about where these drones are deployed].”

And, just like that, we’re one step closer to the opening montage of a Terminator movie!

10

Aug

Man responsible for strong password requirements regrets his 2003 guidelines

Why it matters to you

Here is a look into how the current password requirement system came to be and why the rules are now changing.

The man responsible for your requirement to use a combination of lower-case letters, upper-case letters, numbers, and symbols in passwords at least eight characters long is now regretting his advice. Former National Institute of Standards and Technology manager Bill Burr recently admitted in an interview with The Wall Street Journal that his 2003 document about crafting strong passwords and changing them every 90 days was somewhat off the mark.

At the time, he said that users will choose an easily remembered, easily guessed password, and likely one stemming from a batch of “a few thousand commonly chosen passwords.” In turn, hackers trying to gain access to user accounts, computers, and so on would try the most likely chosen passwords first. But even though services would reject specific passwords given their common use, Burr suggested a more secure alternative.

On page 52 of the 2003 document, he clearly states that systems should rely on a password of eight characters or more that are selected from an alphabet of 94 printable characters. This password should also include at least one upper case letter, one lower case letter, one number, and one special character. Systems should even rely on a dictionary that prevents users from including familiar words and using their login name as the password too.

The problem with this method is that users tend to have patterns when creating a password. For instance, they may take a familiar word, such as “password,” and alter it slightly to meet the requirements. The result could be something like P@zzwurd2017, which isn’t all that original, and something we conjured up in a matter of seconds.

Right now, systems give users a thumbs-up when they follow the current standard and even provide a visual measurement tool indicating the password’s strength against hacking. But then users are requested/forced to change their password every 90 days, thus they may use the same base word, but alter the character usage to please the update process (such as P@ssw0rd2K17).

When the guidelines were created in 2003, they were not based on collected data. System administrators would not cough up any passwords for examination, thus Burr turned to a whitepaper published in the 1980s — long before the general American population purchased a modem and jumped onto the world wide web using Netscape or America Online.

Fast forward to 2017, and the National Institute of Standards and Technology provides new guidelines for systems to follow. Authored by technical adviser Paul Grassi, it tosses out much of what Burr established years ago. But Grazzi admits that Burr’s system lasted for 14 years, and hopes that his revised password ruleset lasts just as long. He suggests that systems remove the 90-day password refresh and the requirement for special characters.

Ultimately, the best practice for everyone is to throw out familiar, easily linked ideas, such as the name of your favorite movie or pet. Instead, create a phrase of words that doesn’t make much sense, and does not include spaces. Password managers like LastPass are helpful too when you are required to remember a multitude of unique passwords across dozens of services.