X

Aggregator

Japanese police claim China ran five-year cyberattack campaign targeting local orgs

The Register
3 months 3 weeks ago
‘MirrorFace’ group found ways to run malware in the Windows sandbox, which may be worrying

Japan’s National Police Agency and Center of Incident Readiness and Strategy for Cybersecurity have confirmed third party reports of attacks on local orgs by publishing details of a years-long series of attacks attributed to a China-backed source.…

Simon Sharwood

NASA's Jet Propulsion Lab Closed Due to Raging LA Fires

Slashdot
3 months 3 weeks ago
NASA's Jet Propulsion Laboratory (JPL), located at the base of the San Gabriel Mountains just north of Los Angeles, has been temporarily shuttered due to the nearby Eaton fire. "JPL is closed except for emergency personnel. No fire damage so far (some wind damage) but it is very close to the lab. Hundreds of JPLers have been evacuated from their homes & many have lost homes. Special thx to our emergency crews. Pls keep us in your thoughts & stay safe," JPL Director Laurie Leshin announced via X today (Jan. 8). Space.com reports: JPL is federally funded but managed by the California Institute of Technology in Pasadena. The center runs many of NASA's high-profile robotic missions, such as the Perseverance and Curiosity Mars rovers and the $5 billion Europa Clipper, which recently launched to explore an intriguing ocean moon of Jupiter. The Eaton fire sparked up on Tuesday evening (Jan. 7) near Altadena, which is just north of Pasadena. It has burned at least 1,000 acres (400 hectares) to date, according to CBS News, which cited the California Department of Forestry and Fire Protection (CalFire). The Eaton fire is one of several big blazes churning through the Los Angeles area, driven and spread by record-setting winds. The biggest and most destructive is the Palisades Fire, which is laying waste to the Pacific Palisades neighborhood on the west side of the city.

Read more of this story at Slashdot.

BeauHD

CodeSOD: Crossly Joined

The Daily WTF
3 months 3 weeks ago

Antonio's team hired some very expensive contractors and consultants to help them build a Java based application. These contractors were very demure, very mindful, about how using ORMs could kill performance.

So they implemented a tool that would let them know any time the Hibernate query generator attempted to perform a cross join.

public class DB2390Dialect extends org.hibernate.dialect.DB2390Dialect { private Logger logger = LoggerFactory.getLogger(DB2390Dialect.class); @Override public String getCrossJoinSeparator() { try { Exception e = new Exception(); throw e; } catch (Exception xe) { logger.warn("cross join ", xe.getMessage()); } return ", "; } }

I'm going to call this one a near miss. I understand what they were trying to do.

Hibernate uses a set of "dialect"s to convert logical operations in a query to literal syntax- as you can see here, this function turns a cross join operation into a ", ".

What they wanted to do was detect where in the code this happened and log a message. They wanted the message to contain a stack trace, and that's why they threw an exception. Unfortunately, they logged, not the stack trace, but the message- a message which they're not actually setting. Thus, the logger would only ever log "cross join ", but with no information to track down when or why it happened.

That said, the standard way in Java of getting the stack trace skips the exception throwing: StackTraceElement[] st = new Throwable().getStackTrace(). Of course, that would have made them do some actual logging logic, and not just "I dunno, drop the message in the output?"

The only remaining question is how much did this feature cost? Since these were "expert consultants", we can ballpark it as somewhere between "a few thousand dollars" to "many thousands of dollars"..

[Advertisement] ProGet’s got you covered with security and access controls on your NuGet feeds. Learn more.
Remy Porter