Flash Nexus7 like a rock star

Are you tired of typing a hostname, username, password and WiFi password every time you flash Nexus7 with Ubuntu Core images?

Do you wish to automate those boring steps?

Do you wish you could reboot into fastboot mode over ssh without reaching and fiddling with volume down and power keys?

Now you can!

$ bzr branch lp:~ubuntu-nexus7/ubuntu-nexus7/preseed

Has a nifty command called

$ ./prepare-preseed

By default it takes preseed.cfg, attempts to copy wifi.cfg or fetch current active WiFi connection settings from Network Manager's /etc/NetworkManager/system-connections/* downloads latest bootimg and twiddles it to include all of the above.

After that you can fastboot flash standard user-data image + this cusom bootimg and voila, upon fastboot reboot ubiquity will come up and will automatically answer all the questions for you and boot into desktop with wifi connected.

If you want to customize settings simply edit the sample preseed.cfg.
If you do not want to always type in sudo password to get the network password you can run:

$ ./get-network-info > wifi.cfg

After that each reflash will be a breeze and not require root password. (Note that I uploaded udev rules in fastboot a while a go to allow using fastboot as a non-privileged user, if you need to support more devices please file bugs against android-tools with the output of lsusb when your device is connected).

So what about rebooting back into fastboot mode?

Well, I recently uploaded upstart 1.6.1-1ubuntu3 into Raring that supports:

$ sudo reboot -f bootloader

That will get you back into fastboot mode.

Happy Hacking everyone!

Comments

Achieving actually full disk encryption of UEFI ESP at rest with TCG OPAL, FIPS, LUKS

Achieving full disk encryption using FIPS, TCG OPAL and LUKS to encrypt UEFI ESP on bare-metal and in VMs Many security standards such as CIS and STIG require to protect information at rest. For example, NIST SP 800-53r5 SC-28 advocate to use cryptographic protection, offline storage and TPMs to enhance protection of information confidentiality and/or integrity. Traditionally to satisfy such controls on portable devices such as laptops one would utilize software based Full Disk Encryption - Mac OS X FileVault , Windows Bitlocker , Linux cryptsetup LUKS2 . In cases when FIPS cryptography is required, additional burden would be placed onto these systems to operate their kernels in FIPS mode. Trusted Computing Group works on establishing many industry standards and specifications, which are widely adopted to improve safety and security of computing whilst keeping it easy to use. One of their most famous specifications them is TCG TPM 2.0 (Trusted Platform Module). TPMs are now...

Encrypt all the things

xkcd #538: Security Went into blogger settings and enabled TLS on my custom domain blogger blog. So it is now finally a https://blog.surgut.co.uk However, I do use feedburner and syndicate that to the planet. I am not sure if that is end-to-end TLS connections, thus I will look into removing feedburner between my blog and the ubuntu/debian planets. My experience with changing feeds in the planets is that I end up spamming everyone. I wonder, if I should make a new tag and add that one, and add both feeds to the planet config to avoid spamming old posts. Next up went into gandi LiveDNS platform and enabled DNSSEC on my domain. It propagated quite quickly, but I believe my domain is now correctly signed with DNSSEC stuff. Next up I guess, is to fix DNSSEC with captive portals. I guess what we really want to have on "wifi" like devices, is to first connect to wifi and not set it as default route. Perform captive portal check, potentially with a reduced DNS server capabil...

Security-only OpenSSL tarball releases for CVE-2026-2673

On Friday May the 13th OpenSSL project has published advisory details for CVE-2026-2673 . The CVE is treated as non-important by the project. The patches are only provided as commits on the stable branches. No git tag, no precise fixed version, and no source tarballs provided. The patches that were merged to openssl-3.5 and openssl-3.6 branches were not based on top of the last stable point release and did not split code changes & documentation updates. It means that cherry-picking the commits referenced in the advisory will always lead to conflicts requiring manual resolution. It is not clear if support is provided for snapshot builds off the openssl-3.5 and openssl-3.6 branches. As the builds from the stable branches declare themselves as dev builds of the next unreleased point release. For example, in contrast to projects such as vim and glibc, with every commit to stable branches explicitly recommended for distributors to ship and is supported. I have requested OpenSSL ups...

Surgut

Search This Blog