Security Leftovers

-
Google finds 'indiscriminate iPhone attack lasting years'
The attack was said to be carried out using websites which would discreetly implant malicious software to gather contacts, images and other data.
Google’s analysis suggested the booby-trapped websites were said to have been visited thousands of times per week.
Apple told the BBC it did not wish to comment.
-
McAfee warns of global malware resurgence, massive ransomware growth
Security firm McAfee has uncovered what it says is a global malware resurgence, with new ransomware growing 118% as cybercriminals adopt new tactics and code innovations.
-
Company Sues Blackhat Because People Mocked Their Sponsored Presentation And Called It Snake Oil
Sean Gallagher, over at Ars Technica, has a story about yet another bizarre lawsuit. A company called Crown Sterling, which claims it's disrupting the entire encryption business, is suing the Black Hat conference organizers after it paid $115,000 to be a "gold sponsor," only to find their presentation widely mocked. You can read the complaint here. It's quite something.
-
U.S. Export Controls and “Published” Encryption Source Code Explained
Throughout our long history of defending encryption, EFF has taken a special interest in ensuring that researchers and programmers who help build and strengthen digital security are not prevented from sharing their knowledge. Because of this history, we periodically get requests about the status of U.S. export controls and how they affect open source software that uses encryption. It can be a daunting topic to research, and our friends at the Internet Systems Consortium (with help from the terrific export regulation attorney Roz Thomsen) just helped us to refresh our understanding. We thought it might be also useful for the community to have a refresher as well.
First, a disclaimer: as part of our Coders’ Rights Project, EFF frequently provides pro bono (free!) assistance to coders, hackers, and security researchers who face legal challenges as a result of their work. But this post isn’t intended as legal advice, so if you find yourself facing a legal threat, we encourage you to consider reaching out so that we can try to help.
[...]
It should also be noted that updates to encryption source code may trigger a requirement to provide additional copies to both BIS and NSA. If you have provided a copy of the published source code, then you must notify the government again when the cryptographic functionality of the source code is updated or modified. If you have posted the source code on the Internet, then you don’t have to provide notice of changes to the encryption functionality, but you do have to notify BIS and the ENC Encryption Request Coordinator each time the Internet location is changed. For all of these notices, exporters should use the same email addresses: crypt@bis.doc.gov and to enc@nsa.gov.
After satisfaction of the notification requirements of the EAR, software falls out of EAR coverage and publishers may export or publish open-source encryption software.
If these requirements seem like empty bureaucratic formalism to you, we agree. There is even a good argument that the regulations are still unconstitutional. But we’re happy that the government has not tried to impose heavy export burdens to re-regulate encryption. We’d also point to a now nearly-two-decade-long track record of open source encryption publishers being free of harassment under the EAR.
-
Millions Of Biometric Records Collected By Companies And Governments Left Exposed On The Web
One of the many problems with collecting biometric data is you need to have someplace safe to store it. Sure, you could lock it away in something disconnected from the net, but then it's not much use to the dozens of private companies and government agencies that want access to the data they've collected. So, back on the web it goes, where it can be prodded for weaknesses by security researchers and malicious hackers alike.
[...]
Names and passwords are certainly being changed in the wake of this discovery. But this breach was full of biometric info linked to other personally identifiable information held by BioStar 2's customers. Fingerprints and other biometric markers can't be changed. These are inextricably tied to whatever other sensitive information was collected by multiple entities -- much of which was stored in unencrypted form.
Suprema and BioStar 2 will probably take security more seriously in the future, but the damage is done. The fact that the marketing team is issuing statements on the breach rather than someone with direct knowledge of the situation isn't exactly reassuring. Neither is the issued statement, which suggests the company would have rather kept the breach buried, rather than be honest and direct with its users.
-

- Login or register to post comments
Printer-friendly version- 2450 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is released
After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release.
|
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future Tech
The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world.
Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago