Updated OnePlus Bullets Wireless on the way

An image of a man wearing OnePlus Bullets Wireless earbuds. OnePlus

  • A new version of OnePlus’ wireless headphones – perhaps called the OnePlus Bullets Wireless 2 – were just spotted at the FCC.
  • The new OnePlus Bullets Wireless have the model number BT32B. The original set were model number BT31B.
  • It is not clear what these headphones will have over their predecessors, but it’s likely they will launch with the OnePlus 6T.

OnePlus launched the OnePlus Bullets Wireless back in May alongside the OnePlus 6. Now, according to the FCC, we know that a sequel pair — perhaps called the OnePlus Bullets Wireless 2 — are on the way.

While we can’t say for certain, it’s a good bet we’ll see the OnePlus Bullets Wireless 2 at the launch event for the upcoming OnePlus 6T, which for right now looks to be in October.

The original Bullets Wireless had the model number BT31B, and the new filing with the FCC labels the new pair as BT32B. The filing also very clearly calls the headphone OnePlus Bullets Wireless and even includes a picture:

An image of the band of OnePlus Bullets Wireless 2 as filed by the FCC. FCC

Obviously, we can’t see the earbuds themselves in the photo, but at least we know that the new Bullets Wireless will feature the same “collar” design as the original Bullets Wireless did.

Editor’s Pick

If the design is similar and the name is pretty much the same, what could OnePlus bring to the table with these new headphones? That’s anyone’s guess at this point, but hopefully, the price point won’t go up significantly and OnePlus will actually keep the new Bullets Wireless in stock at OnePlus.com, as the original Bullets Wireless are frequently unavailable.

We learned today that the OnePlus 6T will absolutely feature an in-display fingerprint sensor and might launch on October 17. It’s a good bet we’ll find out all there is to know about the OnePlus Bullets Wireless 2 — if they are indeed called that — on the same date.

NEXT: OnePlus 6T in-display fingerprint sensor confirmed, October launch date teased?

Source: Android Zone

The post Updated OnePlus Bullets Wireless on the way appeared first on TuneMaster.ml.

Google likely bringing Digital Wellbeing to Assistant and Google Home

 

  • An APK teardown of the Google app suggests that Google is revamping the settings pages of Google Assistant.
  • Within those changes, it looks like Digital Wellbeing features are also coming to Assistant and Google Home products.
  • Digital Wellbeing tools already appear in Android 9 Pie (beta), YouTube, and Google Calendar.

A recent APK teardown of the Google app by XDA Developers suggests that Google is experimenting with a total revamp of the settings pages within the Google Assistant app. This is a welcome change, as the Assistant’s settings pages are kind of messy right now (to say nothing of Google Home’s settings).

Within that settings revamp for Google Assistant, 9to5Google found a new label for some tools within the app: Digital Wellbeing. It appears that Google is bringing Digital Wellbeing tools and settings to Google Assistant, which in turn means that the features are also coming to Google Home hardware.

Editor’s Pick

For those of you who don’t know, Digital Wellbeing is the catch-all term Google created to refer to its new initiative to focus on the healthy use of technology. Since we are increasingly becoming more addicted to our day-to-day tech — especially smartphones — Google feels a responsibility to offer tools that will help people disconnect and focus on their non-digital lives.

The main suite of Digital Wellbeing tools is in beta right now within Android 9 Pie. We’ve had some time with it and it’s been a very sobering experience.

According to 9to5Google, the Digital Wellbeing settings within the Google Assistant app don’t actually do anything yet, but we can make some assumptions based on what is shown. If you look below, on the left you’ll see the newly-designed settings page prior to the appearance of Digital Wellbeing, and on the right you’ll see the updated version:


The change from “Family Tools” to Digital Wellbeing is pretty self-explanatory, in that Google is making the feature set cohesive across applications. The two new options under Digital Wellbeing — Filters and Downtime — we assume refer to a way to filter applications, settings, and games from within Google Assistant (most likely to prevent children from accessing them), and a way to program times of the day when Google Assistant is unavailable on Google Home hardware.

This is just speculation at this point, but it’s very likely that’s what these tools do.

Unfortunately, APK teardowns don’t give us any indication on when we can expect to see the changes rollout to users; in fact, sometimes changes found in an APK never make it to release at all. But given Google’s emphasis of the importance of Digital Wellbeing and its distribution to Android 9 Pie, YouTube, and Google Calendar, it wouldn’t be surprising if more and more Google apps see similar features.

NEXT: YouTube’s own “Digital Wellbeing” tools available now for all

Source: Android Zone

The post Google likely bringing Digital Wellbeing to Assistant and Google Home appeared first on TuneMaster.ml.

11 Top Reasons Why WordPress Sites Get Hacked (and How to Prevent it)

Recently, one of our readers asked us why do WordPress sites get hacked? It is frustrating to find out that your WordPress site has been hacked. In this article, we will share the top reasons why WordPress site gets hacked, so you can avoid these mistakes and protect your site.

Why WordPress sites get hacked?

Why is WordPress Targeted by Hackers?

First, it is not just WordPress. All websites on the internet are vulnerable to hacking attempts.

The reason why WordPress sites are a common target is because WordPress is world’s most popular website builder. It powers over 31% of all websites meaning hundreds of millions of websites across the globe.

This immense popularity gives hackers an easy way to find websites that are less secure, so they can exploit it.

Hackers have different kind of motives to hack a website. Some are beginners who are just learning to exploit less secure sites.

Some hackers have malicious intents like distributing malware, using a site to attack other websites, or spamming the internet.

With that said, let’s take a look at some of the top causes of WordPress sites getting hacked, and how to prevent your website from getting hacked.

1. Insecure Web Hosting

Like all websites, WordPress sites are hosted on a web server. Some hosting companies do not properly secure their hosting platform. This makes all websites hosted on their servers vulnerable to hacking attempts.

This can be easily avoided by choosing the best WordPress hosting provider for your website. It ensures that your site is hosted on a safe platform. Properly secure servers can block many of the most common attacks on WordPress sites.

If you want to take extra pre-caution, then we recommend using a managed WordPress hosting provider.

2. Using Weak Passwords

Using weak passwords

Passwords are the keys to your WordPress site. You need to make sure that you’re using a strong unique password for each of the following accounts because they can all provide a hacker complete access to your website.

  • Your WordPress admin account
  • Web hosting control panel account
  • FTP accounts
  • MySQL database used for your WordPress site
  • Email accounts used for WordPress admin or hosting account

All these accounts are protected by passwords. Using weak passwords makes it easier for hackers to crack the passwords using some basic hacking tools.

You can easily avoid this by using unique and strong passwords for each account. See our guide on the best way to manage passwords for WordPress beginners to learn how to manage all those strong passwords.

3. Unprotected Access to WordPress Admin (wp-admin Directory)

The WordPress admin area gives a user access to perform different actions on your WordPress site. It is also the most commonly attacked area of a WordPress site.

Leaving it unprotected allows hackers to try different approaches to crack your website. You can make it difficult for them by adding layers of authentication to your WordPress admin directory.

First you should password protect your WordPress admin area. This adds an extra security layer, and anyone trying to access WordPress admin will have to provide an extra password.

If you run a multi-author or multi-user WordPress site, then you can enforce strong passwords for all users on your site. You can also add two factor authentication to make it even more difficult for hackers to enter your WordPress admin area.

4. Incorrect File Permissions

File permissions

File permissions are a set of rules used by your web server. These permissions help your web server control access to files on your site. Incorrect file permissions can give a hacker access to write and change these files.

All your WordPress files should have 644 value as file permission. All folders on your WordPress site should have 755 as their file permission.

See our guide on how to fix image upload issue in WordPress to learn how to apply these file permissions.

5. Not Updating WordPress

Some WordPress users are afraid of updating their WordPress sites. They fear that doing so would break their website.

Each new version of WordPress fixes bugs and security vulnerabilities. If you’re not updating WordPress, then you are intentionally leaving your site vulnerable.

If you are afraid that an update will break your website, then you can create a complete WordPress backup before running an update. This way, if something doesn’t work, then you can easily revert back to previous version.

6. Not Updating Plugins or Theme

Just like the core WordPress software, updating your theme and plugins is equally important. Using an outdated plugin or theme can make your site vulnerable.

Security flaws and bugs are often discovered in WordPress plugins and themes. Usually, theme and plugin authors are quick to fix them up. However, if a user does not update their theme or plugin, then there is nothing they can do about it.

Make sure you keep your WordPress theme and plugins up to date.

7. Using Plain FTP instead of SFTP/SSH

SFTP instead of FTP

FTP accounts are used to upload files to your web server using an FTP client. Most hosting providers support FTP connections using different protocols. You can connect using plain FTP, SFTP, or SSH.

When you connect to your site using plain FTP, your password is sent to the server unencrypted. It can be spied upon and easily stolen. Instead of using FTP, you should always use SFTP or SSH.

You wouldn’t need to change your FTP client. Most FTP clients can connect to your website on SFTP as well as SSH. You just need to change the protocol to ‘SFTP – SSH’ when connecting to your website.

8. Using Admin as WordPress Username

Using ‘admin’ as your WordPress username is not recommended. If your administrator username is admin, then you should immediately change that to a different username.

For detailed instructions check out our tutorial on how to change your WordPress username.

9. Nulled Themes and Plugins

Malware

There are many websites on the internet that distribute paid WordPress plugins and themes for free. Sometimes it’s easy to get tempted to use those nulled plugins and themes on your site.

Downloading WordPress themes and plugins from unreliable sources is very dangerous. Not only they can compromise the security of your website, but they can also be used to steal sensitive information.

You should always download WordPress plugins and themes from reliable sources such as the plugin/theme developers website or official WordPress repositories.

If you cannot afford or don’t want to buy a premium plugin or theme, then there are always free alternatives available for those products. These free plugins may not be as good as their paid counterparts, but they will get the job done and most importantly keep your website safe.

You can also find discounts for many of the popular WordPress products in the deals section on our website.

10. Not Securing WordPress Configuration wp-config.php File

WordPress configuration file wp-config.php contains your WordPress database login credentials. If it is compromised, then it will reveal information that could give a hacker complete access to your website.

You can add an extra layer of protection by denying access to wp-config file using .htaccess. Simply add this little code to your .htaccess file.

<files wp-config.php>
order allow,deny
deny from all
</files>

11. Not Changing WordPress Table Prefix

Many experts recommend that you should change the default WordPress table prefix. By default, WordPress uses wp_ as a prefix for the tables it creates in your database. You get an option to change it during the installation.

It is recommended that you use a prefix that is a little more complicated. This will make it harder for hackers to guess your database table names.

For detailed instructions, see our guide on how to change the WordPress database prefix to improve security.

Cleaning up a Hacked WordPress Site

Cleaning up a hacked WordPress site can be really painful. However, it can be done.

Here are some resources to get you started on cleaning up a hacked WordPress site:

Bonus Tip

For rock solid security, we use Sucuri on all our WordPress sites. Sucuri provides malware detection and removal services as well as a website firewall that will protect your website against the most common threats.

See how how Sucuri helped us block 450,000 WordPress attacks in 3 months

We hope this article helped you learn the top reasons why WordPress site gets hacked. You may also want to see our ultimate WordPress security guide to protect your WordPress site.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post 11 Top Reasons Why WordPress Sites Get Hacked (and How to Prevent it) appeared first on WPBeginner.

Source: Wordpres

The post 11 Top Reasons Why WordPress Sites Get Hacked (and How to Prevent it) appeared first on TuneMaster.ml.