The congressman thinks it’s time for a “Data Center Bill of Rights.”

We’ve probably all got one item in our toolboxes or chests that we really, really don’t like, but find too handy to toss. For [Someone Should Make That], that item was the bolt-rounding adjustable wrench. Rather than continuing to gripe about it, or alter his habits to make greater use of the full wrench set he also owns, he decided to build a better mousetrap. By mousetrap, we mean adjustable wrench.

It took a couple of iterations on-screen before he hits on a solution that seems to work quite well indeed. The problem [Someone] had with his adjustable wrench was one of physical slop: once adjusted, there’s just too much play in the mechanism, which results in rounded-off bolt heads. [Someone]’s CNC’d solution takes inspiration from the CNC machine that manufactures it: he’s using spring-loading in the adjustment screw akin to what you find in the anti-backlash nut on your CNC mill or 3D printer’s ball threads. The tension from the springs keeps the wrench tight to the bolt, and that keeps [Someone] from rounding them off. Speaking of 3D printers, he prototyped in plastic before machining, and the screw in the end product stayed that way. It would be interesting to see how well that holds up.

Not only do we appreciate that it’s solved a common problem many of us have, the ethos of “this angers me, so I shall hack it” is one we support 100%, so do give a watch unless you’re one of those people who absolutely can’t stand videos, even when they’re spring-loaded to have no slop. There’s some good tips for beginner CNC operators in there, too.

This isn’t the first time someone’s tried to reinvent this particular wheel, though the last version we liked was a ratchet.

from the surveillance-society dept

Recent reports have raised alarm about the use of PatronScan, an ID-checking and face-scanning system, at multiple LGBTQ+ bars in San Francisco’s Castro neighborhood. Much of the attention has focused on reports that the system photographs patrons as they enter venues and questions about whether those images are used for facial recognition.

A broader privacy concern also deserves scrutiny. For years, PatronScan has marketed itself not just as an ID-verification tool, but as a system that allows bars and clubs to identify patrons, keep records about them, and share information across venues. As one news article published in 2019 documented, PatronScan built a network that allowed participating bars to flag patrons and share information about them with other establishments. 

And in California, it’s not at all clear how PatronScan’s business model of scanning IDs and sharing the information from those scans with other bars comports with the law. California’s ID privacy law, which was amended in 2018 to add ID “scans,” states that no businesses shall “retain or use” any information from a scanned ID card except for limited purposes such as to verify age, comply with a legal requirement, or prevent fraud. 

Californians should be deeply concerned about businesses that collect information from government-issued IDs and use it to build databases about where people go, whom they associate with, and whether they should be allowed into other public gathering places. That concern is especially strong in LGBTQ+ spaces, which have long served as refuges for people to go without being tracked, monitored, or put on lists. 

We reached out to Patronscan with questions regarding their practices and their views on California ID law. They referred us to their published FAQ question “Is Patronscan privacy compliant in California?” which claims that the use of Patronscan kiosks is legal in California. They also said “Patronscan does not do facial recognition in North America, or any kind of automated analysis of the ID or the live photo image.” 

The California Legislature Has Investigated PatronScan’s Business Model 

In 2018, the California Legislature published bill analyses (on that year’s AB 2769) that went into detail about PatronScan’s business. Reviewing PatronScan’s own materials, the California Senate Judiciary Committee found that the company had collected and retained information on 561,087 customers in Sacramento alone during the first five months of 2018—a remarkable figure for a city whose population had only recently topped 500,000.

Lawmakers also found that at that time, PatronScan retained information for at least 90 days or longer in some cases, shared information among participating bars, and maintained bans that lasted an average of more than 19 years. A PatronScan “Public Safety Report” used 10,000 scans collected on a single day to report on “where customers live, how far they have traveled, and how many different venues the customers patronized.” 

This was not simply checking IDs at the door. PatronScan was building a database. 

An immigrants’ rights group, the Coalition for Human Immigrant Rights (CHIRLA), wrote about its concern at the time with these growing ID databases, saying that “placing individuals on a database that labels them a “threat to public safety” has “significant immigration consequences that could lead to deportation, revoking of current status, or denial of future immigration relief.” 

Today, PatronScan states that it retains personal information about all customers for 21 days, and about flagged customers for up to five years. This includes the customer’s name, date of birth, photograph, gender, and zip code. It also includes the dates and times that the customer entered particular bars. Such databases are a grave privacy threat. Personal data is routinely stolen by thieves, misused by a company’s employees, seized by government agencies, and diverted to new purposes by a company’s executives. 

California Law Still Bans ID-Scan Databases, And Bars Should Follow That Law

In 2018, California lawmakers closed what they viewed as a loophole. Existing law already prohibited businesses from retaining or using information obtained when they “swiped” a driver’s license, except for the narrow purposes of legal requirements (like a judicial warrant) or “preventing fraud, abuse, or material misrepresentation.” 

After reviewing companies like PatronScan, the Legislature amended the law to make clear that the same restrictions that apply to businesses that “swipe” ID cards also apply when those IDs are “scanned.” PatronScan opposed that change, arguing it wanted to preserve the ability to share information among bars so participating venues could decide whether to admit patrons.

The bill became law anyway. Yet PatronScan continues to market and sell a system that apparently retains information from scanned IDs, and allows participating venues to flag patrons and share information across its network. 

At a minimum, that raises serious questions about how those practices fit with California’s existing ID privacy law. Bar and nightlife venue owners who utilize PatronScan should think twice about its effects on their customers, and consider going back to standard, visual ID checks. These physical checks have been effective at keeping underage patrons out of 21-and-over venues for decades, and don’t present the serious privacy dangers of creating a private database of bar patrons. 

For venues serving vulnerable communities like immigrants or the LGBTQ+ community, the stakes of using this technology are even higher. It’s disappointing and alarming to see some of California’s more well-known LGBTQ+ nightlife spots instead lining up as PatronScan’s early adopters. A venue cannot claim to be a safe space while feeding its patrons’ data to a third party database. These businesses should reject PatronScan, return to the standard ID checks that every other bar has been able to utilize, and prove to their customers that their privacy and security still matters. 

Originally published to the EFF’s Deeplinks blog.

Filed Under: age verification, california, id privacy, id scans, id verification, privacy

Companies: patronscan

I couldn’t believe it. Had Roku really just casually inserted global viral raccoon sensation Jimothy into Roku City? I’d seen a post claiming so, but knowing how easy it is to fake things with AI, I had to see it for myself.

I powered up one of my home’s half-dozen Roku streaming boxes and spent 10 minutes trying to force the platform into screen-saver mode, which then opens up Roku City. Ever since the most recent Roku platform update, I see this interface far less often than I used to.

Protection against unauthorized remote logins to your cloud server is a matter of SSH key-based authentication, a strict security policy on the firewall, two-factor authentication, and a secure communication channel – no individual component will give adequate protection by itself. The major risk point in breaches is not the server but the open door to remote login. To patch that vulnerability, you need a series of countermeasures, not a magical setting.

Why Remote Server Access Is a Common Attack Vector

Every cloud server exposes at least one remote access point – usually SSH on port 22 – and that port is scanned constantly by bots looking for weak credentials. Password-based login is the most common way a system can be attacked by brute force, and it is quite common with a standard setup that the system is left in a state where an admin/user of that system – “root user” – can log in directly by guessing the user ID and the password combination. Add in shared team credentials, forgotten firewall rules from old projects, and staging servers left publicly reachable, and it’s clear why misconfigured remote access – not zero-day exploits – is behind most cloud server compromises. The fix is simple, though you’ll need to do some setup yourself instead of trusting the default setting.

How to lock down SSH access in the right way

The best way to secure remote access is through a series of small improvements rather than one major overhaul. The following is a real working method:

1. Switch to SSH key authentication, then turn off password login completely in the same location: sshd_config. Keys are far harder to brute-force than passwords.
2. Disable root login over SSH and require a non-root user with sudo privileges instead; this is a security advantage that even without any change, one key compromising would limit the impact.
3. Change the default SSH port away from 22 to cut down on automated scanning noise (not a security measure on its own, but it reduces log clutter).
4. Restrict access by IP using your firewall or security group, allowing SSH only from known office or VPN IP ranges rather than the entire internet.
5. Add a VPN as a connection layer for anyone accessing servers from outside a trusted network – a VPN like Planet VPN’s free VPN service can encrypt the connection between a remote worker’s laptop and the server before SSH traffic ever leaves their device, which matters especially on public wi-fi or shared networks.

Every step you take closes the doors that the attacker may open slightly, and when you combine everything, you would have a door to a series of locked gates.

Why Do I Need a Bastion Host?

When it comes to teams working with many servers, deploying a bastion host (jump box) may be a clean and effective way to solve the long-term problem. With this method, you only expose SSH to the bastion, and the other servers accept it only when it’s from the bastion’s internal IP. This centralizes logging and makes auditing access far simpler.

Using a virtual private network (VPN) and a bastion host together is perfectly fine – and many solutions use both: a safe way to access the private network via a VPN, followed by use of a bastion host to restrict which servers can be accessed. Some teams may decide to forgo the bastion because they don’t have the manpower to manage one, and so use a combination of a VPN and a set of firewall rules that still quite a bit lowers the exposure, but without the extra effort.

Mistakes Leading to Leaving Cloud Servers Open

The Mistakes That Cause Leaving Cloud Servers Open: Even the safest development teams may have slip-ups from time to time. One of the most frequent is leaving staged, or test servers with relaxed firewall rules equivalent to those of the production environment – hackers don’t concern themselves with which environment they first land on. Another frequent error is reusing the same SSH key on several servers and clients, causing one hacked laptop to compromise all servers that key has access to.

Another common human error is not removing or changing access when someone leaves the team, so stale credentials remain valid and accessible. At last, putting trust in the strategy of “security through obscurity” – meaning one thinks that setting up the unusual port or hiding the hostname from the public is actually sufficient security – creates a wrong impression of security. This is mostly true; in reality, modern-day attackers scan all ports anyway, and there is no way to hide from them.

System Administrators Guide to Secure Remote Access 

Prohibit SSH password logins totally and depend exclusively on key-based authentication

• Surely no one wants to type in the password every time; because of this, use only key-based authentication 
• Deter the user from logging in as root by default and instead use the sudo command to do root tasks
• A firewall or security group rule can provide great help with IP address-based restrictions on SSH logins 
• For access that comes from untrusted sources or external networks, use a secure tunnel like a vpn or bastion host
• Periodically change SSH keys and inspect access lists
• Maintain records of login attempts and detect brute-force attacks as quickly as possible

Frequently Asked Questions

The El Capitan Theatre and the Walt Disney Studios lot have long been reserved for some of Disney’s biggest moments. Citizen Kane held its Hollywood premiere on that same stage in 1941, and decades later, The Lion King, the Avengers films, and a steady run of Pixar premieres have rolled out the red carpet at the same historic Hollywood venue.

This September, though, Disney is handing the spotlight to a different kind of storyteller… creators. Created in LA is a new two-day creator summit and film festival conceived by creator Jon Youshaei and presented by Disney. The event will bring 350 creators and storytellers together on September 17–18 for a premiere event at the El Capitan Theatre before moving to the Walt Disney Studios lot for a day of conversations.