HN user

Moral_

1,587 karma

Security (Arm based)

Posts31
Comments118
View on HN
media.defense.gov 6y ago

Patch Critical Cryptographic Vulnerability in Microsoft Windows [pdf]

Moral_
714pts228
plzdonthack.me 8y ago

What to do about duplicates in bug bounty programs?

Moral_
1pts0
android-developers.googleblog.com 8y ago

Android Security Ecosystem Investments Pay Dividends for Pixel

Moral_
2pts0
pleasestopnamingvulnerabilities.com 8y ago

Exploring Previously Unknown Remote Kernel Bugs Affecting Android Phones

Moral_
126pts32
fivethirtyeight.com 9y ago

How Evan McMullin Could Win Utah and the Presidency

Moral_
3pts0
bugzilla.mozilla.org 10y ago

Bug 647959 – Add Honest Achmed's root certificate (2011)

Moral_
111pts68
git.kernel.org 10y ago

Compensate for Rockchip calendar deviation on November 31st

Moral_
131pts37
motherboard.vice.com 10y ago

Court Docs Show Carnegie Mellon University Helped FBI Bust Silk Road 2

Moral_
8pts0
tsyrklevich.net 11y ago

Hacking Team: A Zero-Day Market Case Study

Moral_
14pts0
googlefiberblog.blogspot.com 11y ago

Google Fiber Is Coming to Salt Lake City

Moral_
204pts102
medium.com 11y ago

Quantum Experiment Shows How Time ‘Emerges’ from Entanglement (2013)

Moral_
1pts0
www.openwall.com 11y ago

CVE-2015-0235 glibc gethostbyname Overflow writeup

Moral_
13pts1
info.cern.ch 11y ago

Home of the first website

Moral_
1pts0
evil32.com 11y ago

Evil 32: Check Your GPG Fingerprints

Moral_
31pts9
news.ycombinator.com 11y ago

Ask HN: Are you still using TrueCrypt? What alternatives are there?

Moral_
2pts2
jhalderm.com 11y ago

Green Lights Forever: Analyzing the Security of the Traffic Infrastructure [pdf]

Moral_
8pts0
blog.logrhythm.com 12y ago

Xfinity pineapple – Mimicking an xfinitywifi AP

Moral_
4pts0
seclists.org 12y ago

OpenSSL vulnerable to timing attack?

Moral_
53pts38
hczhcz.github.io 12y ago

Flappy 2048

Moral_
2pts0
privatecore.com 12y ago

A Hypervisor that runs solely in L3 and encrypts ALL I/O

Moral_
1pts0
www.kuro5hin.org 12y ago

We Are Morons: a quick look at the Win2k source (2004)

Moral_
3pts0
afreak.ca 12y ago

Tracking users via wireless networking at BSides Vancouver

Moral_
3pts0
codegolf.stackexchange.com 12y ago

Programming Images with all colors

Moral_
7pts0
medium.com 12y ago

Does Your Learning Management System Marginalize Women?

Moral_
3pts3
poppopret.org 12y ago

Reverse Engineering a Furby

Moral_
103pts26
toys.usvsth3m.com 12y ago

You Can't Do Binary Under Pressure

Moral_
9pts4
blog.kismetwireless.net 12y ago

Wi-Fi isn't radio?

Moral_
15pts0
blog.infobytesec.com 12y ago

Perverting Embedded devices

Moral_
1pts0
www.wired.com 12y ago

Google Street View Comes Aboard Emirates’ Luxurious A380

Moral_
4pts0
blog.ioactive.com 12y ago

Car Hacking Whitepaper and tools released

Moral_
97pts23

Now they're getting counter sued by Qualcomm because it turns out they allegedly violated their own TLA (license to get off the shelf cores) and their ALA (architecture license).

Qualcomm is claiming that Arm is refusing to license the v10 architecture to them and refused to license some other TLA cores requiring them to get the Nuvia Custom CPU team to build cores for those products instead.

This explains their expansion into Risc-V it's a hedge against Arm interfering with QC's business.

SEAR and the Apple team does an excellent job of security on iOS, and should be commended greatly on that.

Not only are they willing to develop hardware features and plumb that throughout the entire stack, they're willing to look at ITW exploits and work on ways to mitigate that. PPL was super interesting, they decided it wasn't 100% effective so they ditched it and came up with other thigs.

Apple's vertical makes it 'easy' to do this compared to Android where they have to convince the CPU guys at QC or Mediatek to build a feature, convince the linux kernel to take it, get it in AOSP, get it in upstream LLVM, etc etc.

Pointer authentication codes (PAC) is a good example, Apple said f-it we'll do it ourselves. They maintained a downstream fork of LLVM, and built full support, leveraged in the wild bypasses and fixed those up.

Quoting Arm stock prices is hilarious considering that there is only 10% float available to be traded and 95% of that 10% is owned by institutions already. That stock is so heavily manipulated so the big boys can make insane profits on options.

On the other topic

>Outside of Snapdragon its basically 5G Telecoms atm

seems to be the only thing going for it.

Did you guys forget the $4B a year in auto rev that they generate, they essentially captured the entire auto market from Nvidia and NXP.

This is the exact reason why they bought Arduino... So now startups have a way to buy say 1,000 devices for prototyping. Qualcomm gets used to supporting smaller developers/startups/tinkerers and will hopefully push different types of chips into the Arduino product lines.

I wish folks would test these against current gen Qualcomm modems. We're comparing a brand new modem to a 2 1/2 year old Modem. Android uses x80 and Qualcomm just released x85. So a fair comparison would be C1 vs x80.

I understand that is what the iPhone 16 uses, but that's an Apple problem they purposefully took an older generation modem from Qualcomm for their 16 series. Knowing Apple's modus operandi they probably decided to use the x71 so when they released C1 it appeared better than it really is. They did this during the Intel Modem days when they shipped that.

None the less it will be interesting to see how this modem develops further and what products it ends up in.

It was also further delayed until December of 2024 because during Depositions Qualcomm learned that ARM didn't destroy nuvia designs like they were required to when they terminated the ALA.

So ARM is suing Qualcomm stating that the IP rights were non-assignable per the ALA, then Qualcomm finds out that ARM also did not hold up its side of the ALA termination agreement and is using Nuvia IP in their current gen designs.

Is it a balloon? /s

“One possibility is that X7’s gas and dust were ejected at the moment when two stars merged,” Ciurlo said. “In this process, the merged star is hidden inside a shell of dust and gas, which might fit the description of the G objects. And the ejected gas perhaps produced X7-like objects.”

This is pretty interesting, so much ejection due to a merger that the light is no longer visible.

Space stories like this always melt my mind because this has all happened already , but we're observing it now.

A lot of the reasons they've had to build most of this stuff themselfs is because they decided for some reason to use freeBSD.

The NUMA work they did, I remember being in a meeting with them as a Linux Developer at Intel at the time. They bought NVMe drives or were saying they were going to buy NVMe drives from Intel which got them access to "on the ground" kernel developers and CPU people from Intel. Instead of talking about NVMe they spent the entire meeting asking us about howt the Linux kernel handles NUMA and corner cases around memory and scheudling. If I recall correctly I think they asked if we could help them upstream BSD code for NVMe and NUMA. I think in that meeting there was even some L9 or super high up NUMA CPU guy from Hillsborough they some how convinced to join.

The conversation and technical discussion was quite fun, but it was sort of funny to us at the time they were having to do all this work on the BSD kernel that was solved years ago for linux.

Technical debt I guess.

Backblaze S-1 IPO 5 years ago

This is the exact reason why I didn't use backblaze, that and their linux support. I didn't want my entire PC backed up, and wanted to hand select a few hefty folders.

Those flash translation layers on the SSDs are generally used to maintain QoS/and do wear leveling, block management etc.

I don't think we'll see file systems go away, but what we may see is more knowledge pushed into the file system, instead of keeping it down in the controller.

We have started to see that with the advent of LightNVM which exposes a more RAW API into the drive and the FTL is maintained in the kernel. The current "generic" implementation of the LightNVM FTL is called pblk:

https://elixir.bootlin.com/linux/latest/source/drivers/light...