PinePhone $149 Linux smartphone could support Ubuntu, Sailfish, Maemo, LuneOS and more




The PinePhone is a cheap, Linux-ready smartphone that’s expected to ship in limited quantities later this year. It’s not exactly a high-power device by modern smartphone standards, but with an expected starting price of $149, it will be a lot more affordable than some of the other Linux phones on the horizon.
It’s also starting to look like the PinePhone could be a very versatile device.
Pine64 has been sending out development kits for a while, and it looks like developers are porting a number of GNU/Linux-based operating systems to the platform.
-
- Login or register to post comments
Printer-friendly version
- 2444 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
Improving the security model of the LVFS
There are lots of layers of security in the LVFS and fwupd design, including restricted account modes, 2FA, and server side AppStream namespaces. The most powerful one is the so-called vendor-id that the vendors cannot assign themselves, and is assigned by me when creating the vendor account on the LVFS. The way this works is that all firmware from the vendor is tagged with a vendor-id string like USB:0x056A which in this case matches the USB consortium vendor assigned ID. Client side, the vendor-id from the signed metadata is checked against the physical device and the firmware is updated only if the ID matches. This ensures that malicious or careless users on the LVFS can never ship firmware updates for other vendors hardware. About 90% of the vendors on the LVFS are locked down with this mechanism.
Some vendors have to have IDs that they don’t actually own, a good example here is for a DFU device like the 8bitdo controllers. In runtime mode they use the USB-assigned 8bitdo VID, but in bootloader mode they use a generic VID which is assigned to the chip supplier as they are using the reference bootloader. This is obviously fine, and both vendor IDs are assigned to 8bitdo on the LVFS for this reason. Another example is where Lenovo is responsible for updating Lenovo-specific NVMe firmware, but where the NVMe vendor isn’t always Lenovo’s PCI ID.
| Programming: Vim, Qt Shader and Python
|
Games: Pygame, The Long Dark, DXVK and Shovel Knight
| today's howtos
|
Recent comments
1 min 1 sec ago
55 min 59 sec ago
7 hours 10 min ago
7 hours 57 min ago
8 hours 7 min ago
8 hours 15 min ago
8 hours 37 min ago
14 hours 6 min ago
15 hours 3 min ago
15 hours 10 min ago