ImageMagick-6.9.12.93-1.fc37

Read Time:7 Second

FEDORA-2023-edbdccae2a

Packages in this update:

ImageMagick-6.9.12.93-1.fc37

Update description:

Update ImageMagick to 6.9.12.93

Read More

How to Safeguard Your LinkedIn Account and Strengthen Your Security

Read Time:5 Minute, 5 Second

If you’re a LinkedIn user, log in now and strengthen your security. Reports indicate that LinkedIn accounts are under attack.

First brought to light by Cyberint, LinkedIn users have taken to social media with word that their accounts have been frozen or outright hacked. In some cases, users received ransom notes for the return of their hacked accounts.

It appears that LinkedIn is weathering a wave of brute-force attacks. This type of attack works much like it sounds—hackers try to force their way into accounts by guessing passwords. With powerful hacking apps, they can guess millions of passwords in seconds.

As a result, one of two things is happening:

LinkedIn users receive an official, legitimate email from LinkedIn alerting them that their account has been locked due to unusual activity. This measure likely kicked in because of a brute force attack or because the attack occurred on an account using two-factor authentication. In this case, the account wasn’t compromised. However, these users then must reactivate their accounts per instructions provided by LinkedIn.
Users try to log in and find that their password has been changed. Effectively, their account has been hacked. Reports show that some of these accounts get deleted. In other cases, the hacker changes the account’s email to an address using the “rambler.ru” domain, which makes the account unrecoverable by the user.

Given the scope, scale, and consistent use of the rambler.ru domain, this has all the signs of an organized attack. As of this writing, no group has claimed credit.

How quickly can someone hack my password with a brute force attack?

If any event underscores the need for strong, unique passwords, this is it.

Given today’s computing power, the password generators hackers use for brute force attacks can create millions of passwords in seconds. Weak passwords have no chance against them. It’s a simple matter of statistics.

Consider a password that uses eight numbers, uppercase and lowercase letters, and symbols. Sounds pretty strong, right? Unfortunately, a brute force attack might crack that password in as fast as one second.

Password Length

(Using numbers, uppercase and lowercase letters, and symbols)

Time to Crack the Password

8
One Second

12
Eight Months

16
16 Million Years

 

However, increase that password length to twelve numbers, uppercase and lowercase letters, and symbols—it’d that eight months to crack that password. Bump it up to 16, and it would take 16 million years. The longer it is, the more complex it is. And thus tougher to crack. It’s the difference between one second and 16 million years. And if a hacker’s brute force attack on one password takes too long, it’ll simply move onto the next one.

How to protect yourself from the LinkedIn attacks.

Log into your LinkedIn account now and verify that it’s indeed secure. Then, take the following steps:

Enable two-factor authentication. You’ll find this in your security settings. Using two-factor authentication makes hacking your account far, far more difficult than hacking it with password protection alone.
Set a new password. Make it strong and unique, using numbers, uppercase letters, lowercase letters, and symbols. As illustrated above, the longer the better—14 or even up to 16 characters.
Confirm your contact email. LinkedIn will alert users of unusual activity. Ensure that the contact information in your account profile uses an email address that you regularly check.

How to create your own strong, unique password. One that you can still remember.

Fourteen characters? Even up to 16 characters? How do you create that without just mashing on your keyboard? (Not recommended.) A layered password can do the work. It’s a way of creating a phrase and turning it into a strong, unique password that you can still remember.

Pick a phrase that is memorable for you: Don’t use easily discovered information, like your birthdate or pet’s name. Try something linked with an interest or hobby. If you’re an avid runner, you might choose a phrase like, “Running 26.2 Rocks!”
Replace letters with numbers and symbols: Remove the spaces. Then, you can put symbols and numbers in the place of some of the letters. Runn1ng26.2R0ck$!
Include a mix of letter cases: Finally, you want lower and uppercase letters that aren’t in a clear pattern. Algorithms know how to look for common patterns like camelCase or PascalCase. Runn1NG26.2R0cK$!

Now, you have a 17-character password that challenges hackers and that’s still something you can remember.

Or, have a password manager handle the strong, unique passwords for you.

Granted, creating strong, unique passwords for dozens and dozens of accounts can take a bit of time. (To put it mildly.) It can take yet more time if you manage them, such as if change them regularly (which can help protect you from data breaches and brute force attacks like this one at LinkedIn). Here, a password manager can help.

A password manager can create, memorize, and store strong, unique passwords. It’ll use the random numbers, letters, and characters we mentioned earlier. The passwords won’t be memorable, but the manager does the memorizing for you. You can also use it to update passwords regularly. In a time of data breaches, this offers you extra protection. Taken together, every account you have gets powerful password protection when you hand the job over to a password manager.

Log in now and secure your LinkedIn account.

This wave of attacks reminds us just how powerful, or weak, our passwords can be. A strong, unique password in conjunction with two-factor authentication stands as your best defense as LinkedIn weathers these attacks. Strengthen your security.

Strengthen your other accounts as well. Hackers target websites and platforms of all sizes, and not every attack makes the headlines. Strong security measures for each of your accounts will protect you best if you end up as a hacker’s target.

The post How to Safeguard Your LinkedIn Account and Strengthen Your Security appeared first on McAfee Blog.

Read More

pypy3.10-7.3.12-1.3.10.fc39

Read Time:3 Minute, 24 Second

FEDORA-2023-ddde191e04

Packages in this update:

pypy3.10-7.3.12-1.3.10.fc39

Update description:

Automatic update for pypy3.10-7.3.12-1.3.10.fc39.

Changelog

* Wed Jul 26 2023 Miro Hrončok <mhroncok@redhat.com> – 7.3.12-1.3.10
– Initial PyPy 3.10 package
* Wed Jul 26 2023 Miro Hrončok <mhroncok@redhat.com> – 7.3.12-1.3.9
– Update to 7.3.12
– Fixes: rhbz#2203423
* Fri Jul 21 2023 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.11-5.3.9
– Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Mon May 29 2023 Charalampos Stratakis <cstratak@redhat.com> – 7.3.11-4.3.9
– Security fix for CVE-2023-24329
Resolves: rhbz#2174020
* Fri Feb 17 2023 Miro Hrončok <mhroncok@redhat.com> – 7.3.11-3.3.9
– On Fedora 38+, obsolete the pypy3.8 package which is no longer available
* Fri Jan 20 2023 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.11-2.3.9
– Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Fri Dec 30 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.11-1.3.9
– Update to 7.3.11
– Fixes: rhbz#2147520
* Fri Dec 2 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.9-5.3.9
– On Fedora 37+, obsolete the pypy3.7 package which is no longer available
* Mon Oct 10 2022 Lumír Balhar <lbalhar@redhat.com> – 7.3.9-4.3.9
– Backport fix for CVE-2021-28861
Resolves: rhbz#2120789
* Fri Jul 22 2022 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.9-3.3.9
– Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Tue Jun 28 2022 Charalampos Stratakis <cstratak@redhat.com> – 7.3.9-2.3.9
– Security fix for CVE-2015-20107
– Fixes: rhbz#2075390
* Wed Mar 30 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.9-1.3.9
– Update to 7.3.9
– Fixes: rhbz#2069873
* Tue Mar 1 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8-1.3.9
– Include the Python version in Release to workaround debuginfo conflicts
and make same builds of different PyPy sort in a predictable way (e.g. wrt Obsoletes)
– Namespace the debugsources to fix installation conflict with other PyPys
– Fixes: rhbz#2053880
– This is now the main PyPy 3 on Fedora 36+
– Fixes: rhbz#2059670
* Tue Feb 22 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8-1
– Update to 7.3.8 final
* Fri Feb 11 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8~rc2-1
– Update to 7.3.8rc2
* Wed Jan 26 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8~rc1-1
– Update to 7.3.8rc1
– Move to a CPython-like installation layout
– Stop requiring pypy3.9 from pypy3.9-libs
– Split tests into pypy3.9-test
* Fri Jan 21 2022 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.7-3
– Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Sat Jan 8 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.7-2
– Rebuilt for https://fedoraproject.org/wiki/Changes/LIBFFI34
* Thu Nov 11 2021 Miro Hrončok <mhroncok@redhat.com> – 7.3.7-1
– Initial pypy3.8 package
– Supplement tox
* Tue Oct 26 2021 Tomáš Hrnčiar <thrnciar@redhat.com> – 7.3.6-1
– Update to 7.3.6
– Remove windows executable binaries
– Fixes: rhbz#2003682
* Mon Sep 20 2021 Miro Hrončok <mhroncok@redhat.com> – 7.3.5-2
– Explicitly buildrequire OpenSSL 1.1, as Python 3.7 is not compatible with OpenSSL 3.0
* Mon Aug 16 2021 Miro Hrončok <mhroncok@redhat.com> – 7.3.5-1
– Update to 7.3.5
– Fixes: rhbz#1992600
* Mon Aug 9 2021 Tomas Hrnciar <thrnciar@redhat.com> – 7.3.4-4
– Rename pypy3 to pypy3.7
– pypy-stackless was removed

Read More

Applying AI to License Plate Surveillance

Read Time:55 Second

License plate scanners aren’t new. Neither is using them for bulk surveillance. What’s new is that AI is being used on the data, identifying “suspicious” vehicle behavior:

Typically, Automatic License Plate Recognition (ALPR) technology is used to search for plates linked to specific crimes. But in this case it was used to examine the driving patterns of anyone passing one of Westchester County’s 480 cameras over a two-year period. Zayas’ lawyer Ben Gold contested the AI-gathered evidence against his client, decrying it as “dragnet surveillance.”

And he had the data to back it up. A FOIA he filed with the Westchester police revealed that the ALPR system was scanning over 16 million license plates a week, across 480 ALPR cameras. Of those systems, 434 were stationary, attached to poles and signs, while the remaining 46 were mobile, attached to police vehicles. The AI was not just looking at license plates either. It had also been taking notes on vehicles’ make, model and color—useful when a plate number for a suspect vehicle isn’t visible or is unknown.

Read More

pypy3.10-7.3.12-1.3.10.fc40

Read Time:3 Minute, 24 Second

FEDORA-2023-c729dabeb1

Packages in this update:

pypy3.10-7.3.12-1.3.10.fc40

Update description:

Automatic update for pypy3.10-7.3.12-1.3.10.fc40.

Changelog

* Wed Jul 26 2023 Miro Hrončok <mhroncok@redhat.com> – 7.3.12-1.3.10
– Initial PyPy 3.10 package
* Wed Jul 26 2023 Miro Hrončok <mhroncok@redhat.com> – 7.3.12-1.3.9
– Update to 7.3.12
– Fixes: rhbz#2203423
* Fri Jul 21 2023 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.11-5.3.9
– Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Mon May 29 2023 Charalampos Stratakis <cstratak@redhat.com> – 7.3.11-4.3.9
– Security fix for CVE-2023-24329
Resolves: rhbz#2174020
* Fri Feb 17 2023 Miro Hrončok <mhroncok@redhat.com> – 7.3.11-3.3.9
– On Fedora 38+, obsolete the pypy3.8 package which is no longer available
* Fri Jan 20 2023 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.11-2.3.9
– Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Fri Dec 30 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.11-1.3.9
– Update to 7.3.11
– Fixes: rhbz#2147520
* Fri Dec 2 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.9-5.3.9
– On Fedora 37+, obsolete the pypy3.7 package which is no longer available
* Mon Oct 10 2022 Lumír Balhar <lbalhar@redhat.com> – 7.3.9-4.3.9
– Backport fix for CVE-2021-28861
Resolves: rhbz#2120789
* Fri Jul 22 2022 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.9-3.3.9
– Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Tue Jun 28 2022 Charalampos Stratakis <cstratak@redhat.com> – 7.3.9-2.3.9
– Security fix for CVE-2015-20107
– Fixes: rhbz#2075390
* Wed Mar 30 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.9-1.3.9
– Update to 7.3.9
– Fixes: rhbz#2069873
* Tue Mar 1 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8-1.3.9
– Include the Python version in Release to workaround debuginfo conflicts
and make same builds of different PyPy sort in a predictable way (e.g. wrt Obsoletes)
– Namespace the debugsources to fix installation conflict with other PyPys
– Fixes: rhbz#2053880
– This is now the main PyPy 3 on Fedora 36+
– Fixes: rhbz#2059670
* Tue Feb 22 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8-1
– Update to 7.3.8 final
* Fri Feb 11 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8~rc2-1
– Update to 7.3.8rc2
* Wed Jan 26 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.8~rc1-1
– Update to 7.3.8rc1
– Move to a CPython-like installation layout
– Stop requiring pypy3.9 from pypy3.9-libs
– Split tests into pypy3.9-test
* Fri Jan 21 2022 Fedora Release Engineering <releng@fedoraproject.org> – 7.3.7-3
– Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Sat Jan 8 2022 Miro Hrončok <mhroncok@redhat.com> – 7.3.7-2
– Rebuilt for https://fedoraproject.org/wiki/Changes/LIBFFI34
* Thu Nov 11 2021 Miro Hrončok <mhroncok@redhat.com> – 7.3.7-1
– Initial pypy3.8 package
– Supplement tox
* Tue Oct 26 2021 Tomáš Hrnčiar <thrnciar@redhat.com> – 7.3.6-1
– Update to 7.3.6
– Remove windows executable binaries
– Fixes: rhbz#2003682
* Mon Sep 20 2021 Miro Hrončok <mhroncok@redhat.com> – 7.3.5-2
– Explicitly buildrequire OpenSSL 1.1, as Python 3.7 is not compatible with OpenSSL 3.0
* Mon Aug 16 2021 Miro Hrončok <mhroncok@redhat.com> – 7.3.5-1
– Update to 7.3.5
– Fixes: rhbz#1992600
* Mon Aug 9 2021 Tomas Hrnciar <thrnciar@redhat.com> – 7.3.4-4
– Rename pypy3 to pypy3.7
– pypy-stackless was removed

Read More