Initially introduced as an exclusive feature for Galaxy devices, Quick Share allows users to share different types of content between Samsung phones, tablets and laptops with just a tap. Either its pictures, videos or documents that you want to share between your Galaxy devices, Quick Share is one of the most convenient ways to do it.Unfortunately, Quick Share would only allow users to transfer files wirelessly between Samsung’s phones, tablets and Windows laptops until recently. Since its launch back in 2020, only those with Samsung phones/tablets and laptops were able to make use of the Quick Share feature, but that’s about to change.
The most recent Quick Share update finally brings support for Windows PCs of other companies. The official changelog spotted by SamMobile also includes mentions of various other improvements and details about what other devices are supported:
Support specifications
OS: Windows 10 2004 version or higher
Bluetooth driver: (Intel) 22.50.02 version or higher
Wi-Fi driver: (Intel) 22.50.07 version or higher
Supported devices
Samsung Galaxy Book (including Qualcomm-based PCs released in 2020 or later)
Windows PC with Intel Bluetooth/Wi-Fi released by other manufacturers
While the update does make Quick Share available to non-Samsung PCs and laptops, the app is limited to Windows devices that pack Intel Wi-Fi and Bluetooth cards inside. Although Intel is a well-known tech company, there are quite a lot of other brands that have been left out.
On top of that, Samsung mentions that depending on the manufacturer and model, there may be restrictions on all or some features of Quick Share.
If you don’t own a non-Samsung PC or laptop equipped with Wi-Fi and/or Bluetooth cards, the latest Quick Share update won’t bring any benefits to you, so you’re still “stuck” with using other apps like Phone Link and Nearby Share.
Amazon has brought back one of its most popular deals ever, but it’s a bit different this time. Instead of offering three months of Amazon Music Unlimited, they are offering three months of Audible Premium with the Echo Dot.
So you’re getting the Echo Dot (5th Gen) which is typically a $49.99 value, along with three months of Audible Premium for just $22.99. That’s not a bad deal at all. Especially since Audible Premium is $14.95/month.
If you were looking to get the bigger Echo, that deal is also available. You can get the Echo (4th Gen) for $54.99 and that includes three months of Audible Premium too. Typically, the Echo is $99.99.
Why you should buy this Echo bundle
This Echo and Echo Dot bundle with the Audible Premium subscription is a really good one to grab. Not only are you getting a cheaper Echo, but you’re also going to be able to experience Audible Premium free for three months. Just remember to cancel before the three months are over, if you don’t want to keep Audible Premium. Otherwise you’ll be charged $14.95 per month.
Audible Premium is a great way to enjoy audiobooks, podcasts, and Audible Originals. With a Premium membership, you get one credit per month to use on any audiobook of your choice, plus unlimited access to the Audible Plus Catalog, which includes thousands of audiobooks, podcasts, and Audible Originals.
There are many benefits to signing up for Audible Premium. First, you get to choose from a huge selection of audiobooks. Whether you’re interested in fiction, nonfiction, self-help, or anything in between, you’re sure to find something you’ll love.
You can pick up the Echo Dot with Audible Premium or Echo with Audible Premium for three months by clicking the links below. This is only available for Prime members and those that are not currently Audible subscribers.
Threads recently launched, and well there’s a lot of things missing. One of the more interesting things that’s missing is ads. Considering how big of an ads platform Facebook and Instagram is, this was pretty surprising. However, according to Instagram boss, Adam Mosseri, that is not the priority right now.
Obviously, ads will be coming to Threads at some point, as the platform does need to make money. But as for right now, it’s not happening any time soon. Mosseri stated that “Honestly not the priority right now. So humbled by everyone signing up, but we gotta make sure this is an app people want to keep using before we worry about making money…”
What Mosseri said is completely true. You can build the best app out there, but if users don’t come, and keep using the platform, it’s going to die. That was the case with Google+.
Mosseri is also taking feature requests
It looks like there’s a pretty long list of features that the team is working on. If you stalk Adam Mosseri’s profile on Threads, you’ll see him responding to quite a few people about it being on the list. That includes a home feed that only shows people they follow, a viable search option, as well as web apps for Threads, among other things.
Though, this is already a more feature-rich alternative compared to Bluesky. Which took months to add the ability to block and mute people. So there’s that. Though, I’d expect this to be a pretty quick moving thing, since Meta does have a pretty sizeable team working on this platform.
Threads also surpassed 20 million signups in the first 12 hours it was available, according to Mark Zuckerberg. While that sounds like a lot, Twitter does have about 300 million monthly active users. So it’s still only about a 30th of the size of Twitter. But a really good head start. Just for reference, Mastodon has around 13 million accounts.
Recently, cybersecurity researchers at VulnCheck revealed that hundreds of internet-exposed SolarView systems on Shodan have been patched against a critical command injection vulnerability.
Experts indicated that both the Mirai botnet hackers and inexperienced individuals have already begun exploiting it, with more expected to join in.
Unit 42 researchers at Palo Alto Networks found that the Mirai botnet is exploiting a command injection vulnerability (CVE-2022-29303) in Contec’s SolarView Series software to spread.
Over 30,000 solar power stations utilize SolarView, and among the critical vulnerabilities, CVE-2022-29303 stands as one of three.
Flaw Profile
CVE ID: CVE-2022-29303
Description: SolarView Compact ver.6.00 was discovered to contain a command injection vulnerability via conf_mail.php.
CVSS Score: 9.8
Severity: CRITICAL
SolarView SystemsIndexed
Currently, there are over 600 systems indexed by Shodan. SolarView tracks and displays solar power generation and storage for small to medium-scale installations.
systems (Source – VulnCheck)
Given the indexed public exploits by VulnCheck Exploit Intelligence, experts delved into exploring the potential scope and impact of this exploitation in real-world scenarios.
Besides its introduction on more than 30000 power stations, Contec also highlights the deployment scenarios for:-
SolarView Air
SolarView Battery
This shows the hardware’s application in buildings and solar power plants that are commercial in nature.
While one should never come across an internet-accessible Contec SolarView due to its clear focus on ICS networks.
SolarView’s impacted versions include ‘ver.6.00,’ which dates back to 2019, and since then, SolarView Compact has undergone four firmware updates:-
6.20 in 2019
7.00 in 2021
8.00 in 2022
8.10 in 2023
It implies that a limited number of exposed hosts are susceptible to the vulnerability. CVE-2022-29303 impacts the conf_mail.php endpoint of the web server, and despite version 6.20 being released after the vulnerable 6.00, it did not address the problem.
Both versions 6.00 and 6.20 were affected, with experts discovering the existence of a simple command injection in conf_mail.php since version 4.00.
Validation was implemented for the attacker-controlled $mail_address variable only in version 8.00 when conf_mail.php was included in the auth require list.
The impact extends beyond what the CVE description suggests, as less than one-third of the internet-exposed SolarView series systems have addressed CVE-2022-29303.
Vulnerable Systems (Source – VulnCheck)
The blog from Unit 42 wasn’t the initial signal of the vulnerability being exploited; since May 2022, an Exploit-DB entry for CVE-2022-29303 has existed.
Other RCEs
The SolarView systems are also impacted by a few additional unauthenticated Remote Code Executions (RCEs), and here they are mentioned below:-
Up to version 8.00, the SolarView series is vulnerable to CVE-2023-23333, and it’s a simple command injection impacting the downloader.php endpoint.
Compact versions 4.0, 5.0, and 6.0 are susceptible to CVE-2022-44354, a file upload vulnerability enabling attackers to upload a PHP web shell onto the system.
Since the SolarView series primarily serve as a monitoring system, the worst-case scenario would likely involve a loss of visibility.
The exploitation’s impact can vary significantly depending on the network integration of the SolarView hardware, potentially resulting in substantial consequences.
It is crucial for organizations to monitor their public IP space and stay updated on public exploits targeting their essential systems.
“AI-based email security measures Protect your business From Email Threats!” – Request a Free Demo.
Threads has finally launched, and in the first 24 hours, notifications have been pretty insane. This is thanks to everyone signing up and following everyone from Instagram over onto Threads, so you get a notification every time someone that follows you joins. Which can get pretty overwhelming.
By default, all notifications are turned on, so if you’re popular, then you’re getting a lot of dings. Thankfully, one of the features that Threads debuted with is, the ability to pause notifications, as well as the ability to turn off notifications. We’re going to show you how to do both today.
How to Pause Notifications on Threads
To pause notifications, the method is the same on both iOS and Android. Just head over to your profile page.
Next, you’ll see an icon in the upper-right hand corner that looks like two lines (one shorter than the other). Tap on that.
Now, tap on Notifications.
At the very top, you’ll see a toggle to “Pause all” notifications. Tap on that.
Here, you’ll get a pop up asking for how long you want to pause all notifications. You have the option for 15 minutes, 1 hour, 2 hours, 4 hours, 8 hours or Cancel.
Unfortunately, you can’t pause for more than 8 hours at a time, but that might change in the future.
How to turn off Notifications on Threads
Out of the box, Threads does allow you to turn off all notifications, but it does take a bit longer. There’s no toggle to just turn off everything, instead you need to do it individually, and there’s two sections too. One for Threads and Replies and another for followers.
To turn off your notifications, tap on the icon in the upper-right hand corner of your profile page.
Then tap on Notifications.
Next, tap on Threads and replies (you can skip this step if you want these to remain on). Here, you’ll be able to turn off notifications for:
Likes
Replies
Mentions
Reposts
Quotes
First Threads
Next, tap on Following and Followers. Here you’ll be able to turn off notifications for:
New followers
Accepted follow requests (for private accounts)
Account suggestions
Pre-followed user joined Threads
Turn on of off each one that you want or don’t want to get. With Threads and replies, you can keep it on everyone, or people you follow, if you do want to keep it on, but don’t want every single notification. And that’s it. That’s how easy it is to turn off the notifications on your Threads account.
The Apple Watch Ultra was one of the most successful pro-grade watches to have ever come out in 2022, thanks in part due to its focus on free-diving and precision dual-frequency GPS. As a result, the next generation of Apple Watch Ultra, slated to release this year, had people excited for the new features, especially with the rumoured MicroLED display. However, recent reports from the South Korean publication The Elec indicate that the upcoming Apple Watch Ultra will not undergo significant changes, and the MicroLED display has been postponed to the first quarter of 2026.
Productions issues behind the delays
The speculations about MicroLEDs first began when reports emerged a few months ago, suggesting that Apple was looking to incorporate it into the next generation of the Apple Watch Ultra. But, industry analyst Ross Young quickly dismissed these claims, asserting that the second quarter of 2025 was a more realistic timeframe for Apple’s mass production of micro-LED displays.
However, according to the new report, the complexity of manufacturing micro-LED panels may be the cause of the 2026 delay. This is because MicroLEDs are still in their early stages and present challenges in terms of production, making it difficult for Apple to expedite the process. Additionally, the exorbitant costs associated with setting up new manufacturing lines for this technology have further complicated the process.
How are MicroLEDs different from other displays?
Although similar in essence to MicroOLEDs, MicroLEDs offer significant advantages over other display types as they are minuscule, with each pixel consisting of an array of micro LEDs, and the fact that they are not organic results in enhanced contrast, energy efficiency, and durability.
Furthermore, in an effort to reduce its reliance on Samsung, Apple has invested over $1 billion in developing this technology. This suggests that the company may implement the same technology in its AR/VR headsets and iPhones once mass production of the panels begins.
The Cisco ACI Multi-Site CloudSec encryption feature of the Cisco Nexus 9000 Series switches contains a critical flaw that enables attackers to easily read encrypted traffic.
The vulnerability resides in implementing the ciphers used by the CloudSec encryption feature on affected switches.
The Cisco ACI Multi-Site Orchestrator GUI is the sole graphical interface that one can employ to set up and oversee ACI and APIC implementations through the browser.
Exploitation of the Flaw
The vulnerability can be exploited by attackers having a position between the ACI sites could exploit the vulnerability by intercepting inter-site traffic.
A remote attacker could use cryptanalytic techniques to break the encryption. Successful exploitation lets an attacker read or modify intersite encrypted traffic.
Cisco stated that no update Flaw or workarounds are available to address this vulnerability.
To determine if CloudSec encryption is active on an ACI site, navigate to Infrastructure > Site Connectivity > Configure > Sites > site-name > Inter-Site Connectivity on the Cisco Nexus Dashboard Orchestrator (NDO).
Check if the “CloudSec Encryption” option is marked as “Enabled.”
To confirm whether your Cisco Nexus 9000 Series switch has CloudSec encryption enabled, simply input the command “show cloudsec sa interface all” into the switch command line.
The resulting output will clearly indicate the “Operational Status” and if CloudSec encryption is active on any interface. Be sure to follow these instructions precisely to accurately determine the encryption status of your switch.
Customers who are using the Cisco ACI Multi-Site CloudSec encryption feature for the Cisco Nexus 9332C and Nexus 9364C Switches and the Cisco Nexus N9K-X9736C-FX Line Card are advised to disable the feature.
The Cisco Nexus 9000 Series Fabric Switches in ACI mode that are running releases 14.0 and later, if they are part of a Multi-Site topology are affected.
“AI-based email security measures Protect your business From Email Threats!” – Request a Free Demo.
The July 2023 security update for Samsung Galaxy devices is one of the biggest releases in recent times. The company’s security updates tracker reveals that the latest SMR (Security Maintenance Release) contains as many as 90 vulnerability patches. As usual, the majority of those are part of Google’s July ASB (Android Security Bulletin), but there are many Galaxy-specific patches as well.
According to Samsung, the July SMR for Galaxy devices patches three critical Android OS issues. The patches come from Google or the vendor of the compromised component. These security issues could lead to remote code execution without the attacker needing additional execution privileges. Threat actors could exploit the issues to remotely control an affected Android device without the user’s knowledge.
Additionally, Google’s latest ASB contains about 50 other vulnerability patches classified as “high” severity security issues by the company. These could lead to local escalation of privileges, among other potential exploitations. The July SMR safeguards Samsung’s Android-powered devices against these vulnerabilities. Some of the new ASB patches don’t apply to Samsung products, though.
Meanwhile, the Korean firm has patched no less than 38 Galaxy-specific security issues this month. Called Samsung Vulnerabilities and Exposures (SVE), these flaws don’t exist on Android products from other brands. As expected, the company hasn’t detailed them all to avoid potential exploitation before users can install the latest security update. The majority of SVE items patched this month appear to be “moderate” and “high” severity issues.
Among those are a few flaws in the Radio Interface Layer (RILD) that allow attackers to execute arbitrary code. Samsung also fixed an issue with the Galaxy Themes Service that enabled local attackers to delete arbitrary non-preloaded apps. Additionally, the company patched an improper access control vulnerability in Settings that paved the way for a physical attacker to use a restricted user profile to access the device owner’s Google account data.
The July security update is already available for the Galaxy S23 and other devices
Samsung may have just detailed the content of the July SMR for Galaxy devices, but it has already rolled out the latest security patch to a few models. The Galaxy S23 series got it first, followed by the Galaxy S22 series. The company also recently pushed the update to the Galaxy A53 5G. More eligible models will pick up the new security patch in the coming days. We will keep you posted with all of those releases.
Ever since the inception of generative AIs like ChatGPT, experts and governments have had their concerns surrounding the unregulated development in the field. Now, in an effort to address these concerns, OpenAI is forming a dedicated team aimed at managing the potential risks associated with superintelligent AIs.
The team, led by Ilya Sutskever, co-founder of OpenAI, along with Jan Leike, a prominent member of OpenAI’s alignment team, will develop methods to handle the hypothetical scenario in which superintelligent AI systems surpass human intelligence and begin operating autonomously. Although this scenario may seem far-fetched, experts argue that superintelligent AIs could become a reality within the next decade, underscoring the importance of developing safeguards today.
“Currently, we don’t have a solution for steering or controlling a potentially superintelligent AI and preventing it from going rogue,” reads the blog post announcing the decision.
The Superalignment team
The Superalignment team, established by OpenAI, will have access to approximately 20% of the current computational resources, along with scientists and engineers from OpenAI’s previous alignment division to develop a “human-level automated alignment researcher,” which would primarily assist in evaluating other AI systems and conducting alignment research.
“As we make progress on this, our AI systems can take over more and more of our alignment work and ultimately conceive, implement, study and develop better alignment techniques than we have now,” reads another blog post.
An AI system to check other AIs
While the proposition of developing an AI system to check on other AIs may seem unusual, OpenAI argues that AI systems can make faster progress in alignment research compared to humans. This approach would not only save time for human researchers but also allow them to focus on reviewing alignment research conducted by AI rather than solely generating it themselves.
However, it is important to note that OpenAI acknowledges the potential risks and dangers associated with this approach. Additionally, the company plans to release a roadmap outlining its research direction in the future.
From which, we can decipher the following, very intriguing info:
Those who pay finally got their money’s worth
No one gets limitless scrolling
And while someone unlike myself would stir the pot further by implying that this has anything to do with money which — let’s face it, without context — is a pretty easy conclusion to reach, I’m actually here to share with you what I uncovered in a post over at Twitter’s blog (which I am obviously an avid reader of).
To address extreme levels of data scraping & system manipulation, we’ve applied the following temporary limits:
– Verified accounts are limited to reading 6000 posts/day – Unverified accounts to 600 posts/day – New unverified accounts to 300/day
Ahem, — “To ensure the authenticity of our user base, we must take extreme measures to remove spam and bots from our platform.” — Why do I feel like I’ve read this one before? Anyway — “That’s why we temporarily limited usage so we could detect and eliminate bots and other bad actors that are harming the platform.”
So basically, this was the next step in the grand-master-plan? Well, I could’ve told you that much. But then again, I vowed not to make predictions regarding Twitter anymore.
The blog post then goes on elaborating that, since Twitter users are basically online rioters at least 70% of the time, the company — as in, Musk — decided not to let anyone know that these limitations are being put in place.
The reinforcement behind this very radical decision yet again involved “Shush, it’s part of the plan!”, as Twitter claims that if said bad actors knew, they’d find a way to circumvent the limitation.
Over the past few days, we’ve taken action to keep making Twitter a great place for everyone. And we want you to know why https://t.co/sJuhSbmmzN
— Twitter Business (@TwitterBusiness) July 4, 2023
So Twitter just postponed the problem by staying silent for a while? Said a while being a very insignificant amount of time, because — again — Twitter users are rioters in 70% of their time. Sure?
Naturally, with the company needing those tasty advertisements in order to stay afloat, the blog addresses any concerns by stating that this limitation only affects a “minimal” amount of users.
Let me get this straight: Twitter decided to not tell anyone about the limitations out of fear that they’d be circumvented, but everyone found out about them anyway (because they are limitations?) and then said limitations are only affecting a very small percentage of users on the platform.
Well, if that’s the case, why have the limitation at all?
Twitter seems to be talking in a way that implies that there is a master plan, but that final line of “We will explain later, trust us” feels off in a very Big Brother kind of way. And speaking of which, that may very well be the next step in Twitter’s… Whatever we can call this route.