Intel said it was the victim of a hacker who stole financially sensitive information from its corporate website on Thursday, prompting the company to release its earnings statement ahead of schedule.ÂFrom a report: The US computer chipmaker believed an attacker had obtained advanced details about a strong earnings report it was due to publish after the stock market closed, said George Davis, chief financial officer. It published its formal earnings announcement upon discovering the problem, six minutes before the market closed. Intel's shares rose more than 6 per cent on Thursday, including almost 2 per cent in the final 15 minutes of trading. "An infographic was hacked off of our PR newsroom site," Mr Davis said. "We put [our earnings] out as soon as we were aware." He did not provide more details, but said that the leak was the result of an illicit action that had not involved any unintentional disclosure by the company itself. An Intel spokesperson added: "We were notified that our infographic was circulating outside the company. I do not believe it was published. We are continuing to investigate this matter."

The US National Security Agency has issued a security advisory this month urging system administrators in federal agencies and beyond to stop using old and obsolete TLS protocols. From a report: "NSA recommends that only TLS 1.2 or TLS 1.3 be used; and that SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.1 not be used," the agency said. "Using obsolete encryption provides a false sense of security because it seems as though sensitive data is protected, even though it really is not," the agency added. Even if TLS 1.2 and TLS 1.3 are deployed, the NSA warns against configuring these two protocols with weak cryptographic parameters and cipher suites.

An anonymous reader quotes a report from ZDNet: A suspected Chinese hacking group has been attacking the airline industry for the past few years with the goal of obtaining passenger data in order to track the movement of persons of interest. The intrusions have been linked to a threat actor that the cyber-security has been tracking under the name of Chimera. Believed to be operating in the interests of the Chinese state, the group's activities were first described in a report [PDF] and Black Hat presentation [PDF] from CyCraft in 2020. The initial report mentioned a series of coordinated attacks against the Taiwanese superconductor industry.

But in a new report published last week by NCC Group and its subsidiary Fox-IT, the two companies said the group's intrusions are broader than initially thought, having also targeted the airline industry. These attacks targeted semiconductor and airline companies in different geographical areas, and not just Asia, NCC and Fox-IT said. In the case of some victims, the hackers stayed hidden inside networks for up to three years before being discovered. "The goal of targeting some victims appears to be to obtain Passenger Name Records (PNR)," the two companies said. While the NCC and Fox-IT report didn't speculate why the hackers targeted the airline industry and why they stole passenger data, this is pretty obvious. In fact, it is very common for state-sponsored hacking groups to target airline companies, hotel chains, and telcos to obtain data they could use to track the movements and communications of persons of interest.

US cyber-security firm Malwarebytes said it was hacked by "Dark Halo," the same group which breached IT software company SolarWinds last year. ZDNet reports: Malwarebytes said its intrusion is not related to the SolarWinds supply chain incident since the company doesn't use any of SolarWinds software in its internal network. Instead, the security firm said the hackers breached its internal systems by exploiting an Azure Active Directory weakness and abusing malicious Office 365 applications. Malwarebytes said it learned of the intrusion from the Microsoft Security Response Center (MSRC) on December 15.

At the time, Microsoft was auditing its Office 365 and Azure infrastructures for signs of malicious apps created by the SolarWinds hackers, also known in cyber-security circles as UNC2452 or Dark Halo. Malwarebytes said that once it learned of the breach, it began an internal investigation to determine what hackers accessed. "After an extensive investigation, we determined the attacker only gained access to a limited subset of internal company emails," said Marcin Kleczynski, Malwarebytes co-founder and current CEO.

Cybersecurity firm FireEye has released today a report detailing the techniques used by the SolarWinds hackers inside the networks of companies they breached. From a report: Together with the report, FireEye researchers have also released a free tool on GitHub named Azure AD Investigator that they say can help companies determine if the SolarWinds hackers (also known as UNC2452) used any of these techniques inside their networks. Today's FireEye report comes as the security firm has spearheaded investigations into the SolarWinds supply chain compromise, together with Microsoft and CrowdStrike. The SolarWinds hack came to light on December 13, 2020, when FireEye and Microsoft confirmed that a threat actor broke into the network of IT software provider SolarWinds and poisoned updates for the Orion app with malware.

With the release of Brave 1.19 today, Brave has become the first major browser maker to support IPFS, a peer-to-peer protocol meant for accessing decentralized or censored content. From a report: Released in 2015, IPFS stands for InterPlanetary File System. It is a classic peer-to-peer protocol similar to BitTorrent and designed to work as a decentralized storage system. IPFS allows users to host content distributed across hundreds or thousands of systems, which can be public IPFS gateways or private IPFS nodes. Users who want to access any of this content must enter an URL in the form of ipfs://{content_hash_ID}. Under normal circumstances, users would download this content from the nearest nodes or gateways rather than a central server. However, this only works if users have installed an IPFS desktop app or a browser extension.

Brave says that with version 1.19, users will be able to access URLs that start with ipfs://, directly from the browser, with no extension needed, and that Brave will natively support ipfs:// links going forward. Since some major websites like Wikipedia have IPFS versions, users in oppressive countries can now use Brave's new IPFS support to go around national firewalls and access content that might be blocked inside their country for political reasons and is available via IPFS.

The Intercept's Nikita Mazurov warns that Zoom has digital watermarks that could expose sources working with journalists or government officials. An anonymous reader shares an excerpt from the report: Many users may not realize it, but Zoom has the capability to insert both video and audio watermarks into a meeting. The video watermarks are readily perceptible to meeting participants. When enabled, the video watermarking feature superimposes the username portion of each participant's email address over the content they are viewing when another participant shares their screen and places the same watermark over the current active speaker. Because the video watermark appears across the entirety of the video frame, blurring may adversely impact the visibility of the underlying material. In contrast, the audio watermarks are not readily perceptible to casual listeners, though they are what in watermarking parlance is known as "overt." That means the fact that they are embedded is easily discerned by meeting participants: When a Zoom meeting has the audio watermark, or what Zoom also calls the "audio signature," feature enabled, the meeting will have a green circular icon with a sound wave and a padlock at the top left of the frame next to the encryption icon.

It is not immediately apparent at what point Zoom injects its "ultrasonic" audio watermark into the audio stream -- whether this happens only if a meeting attendee presses the Record button in Zoom or if the audio stream is watermarked prior to that point. Nonetheless, when recording a Zoom meeting, it is best to avoid using Zoom's built-in recording option and to capture the meeting using a third-party audio/video recorder. Zoom mentions that in order to identify the participant who recorded the meeting, they need at least two minutes of audio from the meeting, though it stands to reason that shorter snippets may also be identifiable if they happen to contain the audio watermark. Journalists should also be wary of publishing raw audio leaked from Zoom meetings, particularly if the source is not sure whether audio watermarking was enabled or not.

Aside from Zoom's own watermarks, a number of elements appearing on an individual's own device may inadvertently give away the identity of the person who is recording. If the meeting video is being recorded either via screen recording software or a camera, there are a number of elements to watch out for...

The OpenWRT forum, a large community of enthusiasts of alternative, open-source operating systems for routers, announced a data breach over the weekend. Bleeping Computer reports: The attack occurred on Saturday, around 04:00 (GMT), when an unauthorized third party gained admin access to and copied a list with details about forum users and related statistical information. The intruder used the account of an OpenWRT administrator. Although the account had "a good password," additional security provided by two-factor authentication (2FA) was not active. Email addresses and handles of the forum users have been stolen, the moderators say. They add that they believe the attacker was not able to download the forum database, meaning that passwords should be safe. However, they reset all the passwords on the forum just to be on the safe side and invalidated all the API keys used for project development processes.

Users have to set the new password manually from the login menu by providing their user name and following the "get a new password" instructions. Those logging in using GitHub credentials are advised to reset or refresh it. The OpenWRT forum credentials are separate from the Wiki. Currently, there is no suspicion that the Wiki credentials have been compromised in any way. OpenWRT forum administrators warn that since this breach exposed email addresses, users may become targets of credible phishing attempts.

An anonymous reader shares a report: As far back as June, Microsoft explained in somewhat legalistic terms that it's happily recording so much Teams activity for the benefit of employers and it's up to them what they do with it. Sample wording from Redmond's fine lawyers: "Our customers are controllers for the data provided to Microsoft, as set forth in the Online Services Terms, and they determine legal bases of processing." From what I could see, Teams hoovers up all your chats, voicemails, shared meetings, files, transcriptions, your profile details including your email address and phone number, and a detailed analysis of what you were wearing on the call. (I may have made up that last one.) Cut to September and Microsoft offered a little more about the Teams Activity Report (since updated). Here's a sentence that's unsurprising but still a touch uncomfortable: "The table gives you a breakdown of usage by user." Everything from how many meetings that user organized to how many urgent messages they sent is recorded. Separate numbers are given for scheduled meetings and those that were ad hoc. Even individuals' screen-share time is there. It's remarkably detailed. But, I hear you cry, is it detailed enough?

In October, then, Redmond offered "a new analytics and reporting experience for Microsoft Teams." (This was updated last week.) I confess that just staring at this made me swivel several times in wonder. Microsoft is measuring privacy settings, device types, time stamps, reasons why someone may have been blocked, and "the number of messages a user posted in a private chat." I know you'll tell me this is all normal. This is entirely what's to be expected in today's techno-marvelous world. Yet, as far as I could tell, employees don't have too much say in all this. They're forced onto a particular platform without much control over what that platform may record about them personally, with their employer being the potential beneficiary. I imagined an individual -- or even a whole team -- being summoned by their boss and told: "You didn't respond to 47 Teams messages last month." What do you say to that? "Well, I suspect those 47 messages were sent by brown-nosing halfwits who send as many Teams messages as possible, so their innate industry shows up on your Teams analytics reports."

Privacy-focused search engine DuckDuckGo reached a major milestone in its 12-year-old history last week when it recorded on Monday its first-ever day with more than 100 million user search queries. From a report: The achievement comes after a period of sustained growth the company has been seeing for the past two years, and especially since August 2020, when the search engine began seeing more than 2 billion search queries a month on a regular basis. The numbers are small in comparison to Google's 5 billion daily search queries but it's a positive sign that users are looking for alternatives. DuckDuckGo's popularity comes after the search engine has expanded beyond its own site and now currently offers mobile apps for Android and iOS, but also a dedicated Chrome extension. More than 4 million users installed these apps and extension, the company said in a tweet in September 2020.

GitHub is admitting that a Jewish employee was fired in error and is offering him his job back. The news comes after the company hired an independent law firm to investigate the termination, and found that "significant mistakes were made." The company's head of HR, Carrie Olesen, is also resigning. From a report: "Yesterday evening, the investigation reached the conclusion that significant mistakes were made that are not consistent with our internal practices or the judgement we expect from our leaders," wrote GitHub CEO Nat Friedman in an internal message to employees on January 16th. He said the company would be issuing a public apology on its blog this weekend. In the post, GitHub COO Erica Brescia said: "To the employee we wish to say publicly: we sincerely apologize." The controversial firing came just two days after the employee warned colleagues in Washington DC to stay safe from Nazis -- news first reported by Business Insider. He posted the message on January 6th, the day of the insurrection in Washington DC, as rioters associated with neo-Nazi organizations stormed the Capitol. The warning sparked criticism from a colleague who took offense at the use of the word "Nazi" and prompted GitHub's HR team to reprimand the Jewish employee. Two days later, he was fired.

The New York Times reports on an "exodus" of tech workers from the San Francisco Bay Area, where "Rent was astronomical. Taxes were high. Your neighbors didn't like you" — and your commute could be over an hour. The biggest tech companies aren't going anywhere, and tech stocks are still soaring... But the migration from the Bay Area appears real. Residential rents in San Francisco are down 27% from a year ago, and the office vacancy rate has spiked to 16.7%, a number not seen in a decade. Though prices had dropped only slightly, Zillow reported more homes for sale in San Francisco than a year ago. For more than a month last year, 90% of the searches involving San Francisco on moveBuddha were for people moving out...

There are 33,000 members in the Facebook group Leaving California and 51,000 in its sister group, Life After California. People post pictures of moving trucks and links to Zillow listings in new cities.
They've apparently scattered across the country — even to tropical islands like Puerto Rico and Costa Rica They fled to more affordable places like Georgia. They fled to states without income taxes like Texas and Florida... The No. 1 pick for people leaving San Francisco is Austin, Texas, with other winners including Seattle, New York and Chicago, according to moveBuddha, a site that compiles data on moving. Some cities have set up recruiting programs to lure them to new homes.
The Times also notes "there is a very vocal Miami faction, led by a few venture capital influencers, trying to tweet the city's startup world into existence," as other cities begin to realize that "the talent and money of newly remote tech workers are up for grabs." Topeka, Kansas, started Choose Topeka, which will reimburse new workers $10,000 for the first year of rent or $15,000 if they buy a home. Tulsa, Oklahoma, will pay you $10,000 to move there. The nation of Estonia has a new residency program just for digital nomads. A program in Savannah, Georgia, will reimburse remote workers $2,000 for the move there, and the city has created various social activities to introduce the newcomers to one another and to locals...
But the article also points out that "More money was made faster in the Bay Area by fewer people than at any other time in American history," and speculates on what long-time residents may be thinking: People who distrusted the young newcomers from the start will say this change is a good thing. Hasn't this steep growth in wealth and population in a tiny geography always seemed unsustainable? These tech workers came like a whirlwind. Virtually every community from San Jose in the south to Marin County in the north has fought the rise of new housing for the arrivals of the last decade. Maybe spreading the tech talent around America is smart.

Locals have also seen this play before. Moving trucks come to take a generation of tech ambition away, and a few years later moving trucks return with new dreamers and new ambitions.
UPDATE (7/18/2021): "Tech workers who swore off the Bay Area are coming back," the New York Times reported six months later.

Legendary programmer Jamie Zawinski has worked on everything from the earliest releases of the Netscape Navigator browser to XEmacs, Mozilla, and, of course, the XScreenSaver project.

Now Slashdot reader e432776 writes: JWZ continues to track issues with screensavers on Linux (since 2004!), and discusses a new bug in cinnamon-screensaver. Long-standing topics like X11, developer interaction, and code licensing all feature. Solutions to these long-standing issues remain elusive.
Jamie titled his blog post "I told you so, 2021 edition": You will recall that in 2004 , which is now seventeen years ago, I wrote a document explaining why I made the design trade-offs that I did in XScreenSaver, and in that document I predicted this exact bug as my example of, "this is what will happen if you don't do it this way."

And they went and made that happen.

Repeatedly.

Every time this bug is re-introduced, someone pipes up and says something like, "So what, it was a bug, they've fixed it." That's really missing the point. The point is not that such a bug existed, but that such a bug was even possible. The real bug here is that the design of the system even permits this class of bug. It is unconscionable that someone designing a critical piece of security infrastructure would design the system in such a way that it does not fail safe .

Especially when I have given them nearly 30 years of prior art demonstrating how to do it right, and a two-decades-old document clearly explaining What Not To Do that coincidentally used this very bug as its illustrative strawman!

These bugs are a shameful embarrassment of design -- as opposed to merely bad code...
ZDNet reports that Linux Mint has issued a patch for Cinnamon that fixes the screensaver bug. But HotHardware notes that it was discovered when "one Dad let the kids play with the keyboard. This button-mashing actually crashed the machine's screensaver by sheer luck, allowing them onto the desktop, ultimately leading to the discovery of a high priority security vulnerability for the Linux Mint team."

But that's not the only thing bothering Jamie Zawinski: Just to add insult to injury, it has recently come to my attention that not only are Gnome-screensaver, Mint-screensaver and Cinnamon-screensaver buggy and insecure dumpster fires, but they are also in violation of my license and infringing my copyright.

XScreenSaver was released under the BSD license, one of the oldest and most permissive of the free software licenses. It turns out, the Gnome-screensaver authors copied large parts of XScreenSaver into their program, removed the BSD license and slapped a GPL license on my code instead -- and also removed my name. Rude...

Mint-screensaver and Cinnamon-screensaver, being forks and descendants of Gnome-screensaver, have inherited this license violation and continue to perpetuate it. Every Linux distro is shipping this copyright- and license-infringing code.

I eagerly await hearing how they're going to make this right.

Dallas, TX-based cloud security firm Trend Micro interviewed 500 IT directors and managers, CIOs and CTOs — and discovered that over two-fifths of them believe they'll be replaced by AI by 2030.

ZDNet reports: Only 9% of respondents were confident that AI would definitely not replace their job within the next decade. In fact, nearly a third (32%) said they thought the technology would eventually work to completely automate all cybersecurity, with little need for human intervention.

Almost one in five (19%) believe that attackers using AI to enhance their arsenal will be commonplace by 2025.

Around a quarter (24%) of IT leaders polled also claimed that by 2030, data access will be tied to biometric or DNA data, making unauthorised access impossible. In the shorter term, respondents also predicted the following outcomes would happen by 2025. They predict that most organisations will have significantly reduced investment in property as remote working becomes the norm (22%)

Nationwide 5G will have entirely transformed network and security infrastructure (21%), and security will be self-managing and automated using AI (15%).

However, attackers using AI to enhance their arsenal will be commonplace (19%)

Yesterday long-time tech pundit Robert Cringley reviewed the predictions he'd made at the beginning of last year. "Having done this for over 20 years, historically I'm correct abut 70 percent of the time, but this year could be a disappointment given that I'm pretty sure I didn't predict 370,000 deaths and an economy in free-fall.

"We'll just have to see whether I was vague enough to get a couple right."

Here's some of the highlights: I predicted that IBM would dump a big division and essentially remake itself as Red Hat, its Linux company. Well yes and no. IBM did announce a major restructuring, spinning-off Global Technology Services just as I predicted (score one for me) but it has all happened slowly because everything slows down during a pandemic. The resulting company won't be called Red Hat (yet), but the rest of it was correct so I'm going to claim this one, not that anybody cares about IBM anymore...

I predicted that working from home would accelerate a trend I identified as the end of IT, by which I meant the kind of business IT provided and maintained by kids from that office in the basement. By working from home, we'd all become our own IT guys and that would lead to acceleration in the transition of certain technologies, especially SD-WAN and Secure Access Service Edge (SASE)... "That's the end-game if there is one — everything in the cloud with your device strictly for input and output, painting screens compressed with HTML5. It's the end of IT because your device will no longer contain anything, so it can be simply replaced via Amazon if it is damaged or lost, with the IT kid in the white shirt becoming an Uber driver (if any of those survive)."

It was a no-brainer, really, and I was correct: Internet-connected hardware sales surged, SASE took over whether you even knew it or not, and hardly any working from home was enabled by technology owned by the business, itself. It's key here that the operant term for working from home became "Zooming" — a third-party public brand built solely in the cloud.

Finally, I predicted that COVID-19 would accelerate the demise of not just traditional IT, but also IT contractors, because the more things that could be done in the cloud the less people would be required to do them. So what actually happened? Well I was right about the trend but wrong about the extent. IT consulting dropped in 2020 by about 19 percent, from $160 billion to $140 billion. That's a huge impact, but I said "kill" and 19 percent isn't even close to dead. So I was wrong.

An anonymous reader quotes a report from ZDNet: For more than five years, macOS users have been the targets of a sneaky malware operation that used a clever trick to avoid detection and hijacked the hardware resources of infected users to mine cryptocurrency behind their backs. Named OSAMiner, the malware has been distributed in the wild since at least 2015 disguised in pirated (cracked) games and software such as League of Legends and Microsoft Office for Mac, security firm SentinelOne said in a report published this week. But the cryptominer did not go entirely unnoticed. SentinelOne said that two Chinese security firms spotted and analyzed older versions of the OSAMiner in August and September 2018, respectively. But their reports only scratched the surface of what OSAMiner was capable of, SentinelOne macOS malware researcher Phil Stokes said yesterday.

The primary reason was that security researchers weren't able to retrieve the malware's entire code at the time, which used nested run-only AppleScript files to retrieve its malicious code across different stages. As users installed the pirated software, the boobytrapped installers would download and run a run-only AppleScript, which would download and run a second run-only AppleScript, and then another final third run-only AppleScript. Since "run-only" AppleScript come in a compiled state where the source code isn't human-readable, this made analysis harder for security researchers.

Besides the intended differences, web browsers based on Chromium offer an underlying experience that's mostly identical to Chrome. Google recently discovered that users of third-party Chromium browsers have inadvertently been able to access data and other sync features reserved for Chrome. From a report: "Some" Chromium browsers today can leverage features and APIs that are "only intended for Google's use." This includes Click to Call and, notably, Chrome Sync. The latter is responsible for syncing bookmarks, extensions, history, settings, and more across signed-in devices running the first-party browser. As a result, users logged into Google sites on Chromium browsers are able to see their old bookmarks and other data from previous Chrome usage. This inadvertent access was discovered during a recent audit and Google will be "limiting access to [its] private Chrome APIs" from March 15th.

The US National Security Agency has published this week a guide on the benefits and risks of encrypted DNS protocols, such as DNS-over-HTTPS (DoH), which have become widely used over the past two years. From a report: The US cybersecurity agency warns that while technologies like DoH can encrypt and hide user DNS queries from network observers, they also have downsides when used inside corporate networks. "DoH is not a panacea," the NSA said in a security advisory [PDF] published today, claiming that the use of the protocol gives companies a false sense of security, echoing many of the arguments presented in a ZDNet feature on DoH in October 2019. The NSA said that DoH does not fully prevent threat actors from seeing a user's traffic and that when deployed inside networks, it can be used to bypass many security tools that rely on sniffing classic (plaintext) DNS traffic to detect threats. Furthermore, the NSA argues that many of today's DoH-capable DNS resolver servers are also externally hosted, outside of the company's control and ability to audit.

Apple is planning upgraded MacBook Pro laptops this year with much faster processors, updated displays and the return of its magnetic charger, Bloomberg reported Friday, citing a person with knowledge of the plans. From the report: The new laptops are planned to come in two screen sizes, a 14-inch model codenamed J314 and a 16-inch version internally dubbed J316. Both will use next-generation versions of Apple's in-house Mac processors, upgraded with more cores and enhanced graphics, the person said, asking not to be named as the products are not yet announced.

These devices will mark Apple's first high-end laptops to move away from Intel components. The company updated its base 13-inch MacBook Pro with its own M1 chip in November, to broadly positive reviews. Beyond the more powerful chips, Apple is also planning to step up the displays in its new MacBook Pros with brighter, higher-contrast panels, the person said. The new Macs will look similar to the current versions, albeit with minor design changes. Apple is aiming to launch the new MacBook Pros around the middle of the year. A major change to the new computers will be how they charge. Over the past five years, Apple has relied on USB-C ports for both power and data transfer on its laptops, making them compatible with other manufacturers' chargers. But the company is now bringing back MagSafe, the magnetic power adapter that means any accidental yanking of the power cable would simply detach it from the laptop rather than pull down the entire computer.

Ford Motor is halting production of its most popular car model in Europe for a full month because of the shortage of semiconductors disrupting the world's biggest automakers. From a report: The automaker's Focus factory in Saarlouis, Germany, will idle from Jan. 18 through Feb. 19, according to a spokesman, who said lower consumer demand also is playing a factor. The plant is Ford's lone manufacturing facility for the Focus and employs about 5,000 workers. The facility is the latest to fall victim to a supply issue that's disrupting carmakers around the globe. Ford already was forced to idle a sport utility vehicle plant in Kentucky this week, joining Volkswagen AG, Daimler AG, Toyota Motor Corp. and others in scaling back output because of the bottleneck of chips that play a function in everything from brakes to windshield wipers.