Being a prudent IT-savvy user, I had exported all my two-factor authentication account data only a few days ago, to an older Android phone that also runs Google Authenticator. In fact, I have a calendar reminder to keep this 2FA backup updated, every couple of months. Naturally, I was feeling very safe and smug about it, thinking that I had nothing to worry about.

When I updated my Google Authenticator app to version 7.0, I discovered that the app now requires sign-in to Google. Normally this wouldn’t be a problem, but my phone is a Huawei phone, and due to the Huawei ban, it cannot connect to Google at the OS level. Instead, I use the Google apps such as Gmail, Calendar and Keep via the Brave browser (Chrome doesn’t sign in, and Firefox works but much slower). Other than that, it’s a good phone with a decent camera for its price range, and I’m happy with it, so I have no reason to change it.

But now, suddenly, I couldn’t use the Authenticator app, and all my 2FA codes were inaccessible. I immediately retrieved my backup phone from storage, only to find out that the battery had become a spicy pillow, and the phone would not start. Aaaargh!

Note that it hadn’t been more than a few weeks since this backup phone was usable, and I had kept recent backups of my 2FA codes in it. Naturally, I ordered a replacement battery for my backup phone. But this won’t be here for a few days, and I want access to my online accounts now.

Version 7.0: A drastic change. Too drastic, if you ask me!

My first thought was to look for an older version of the app and install that. Sure enough, looking at the APKPure, I found out that version 7.0 has this changelog entry:

Cloud syncing: Your Authenticator codes can now be synced to your Google Account and across your devices, so you can always access them even if you lose your phone.

Wow, thanks Google! That’s great and all, but unfortunately there is no option to NOT do this. It is not possible to continue using the app without signing in.

Downgrading the app from 7.0 to 6.0…

So I naturally downloaded version 6.0 from:

https://apkpure.com/google-authenticator/com.google.android.apps.authenticator2/downloading/6.0

I got a file named Google Authenticator_6.0_APKPure.apk which I now had to install. But, apparently, it’s not possible to downgrade Android apps, without first uninstalling the newer version! The Android OS won’t let you do it. At least not directly.

And I didn’t want to uninstall the app, because that would presumably delete my 2FA data.

So, what to do?

After some googling, I found out that it’s possible to install an older version of an Android app via the command line tool adb. I connected the phone to the computer with a USB cable and enabled debug mode.

The command that did the trick:

adb install -d Google\ Authenticator_6.0_APKPure.apk

And the output I got back:

Performing Streamed Install
Success

The -d option is the one that allows to downgrade the app. Version 6.0 was installed on my phone, and I regained access to all my 2FA codes.

Hope this helps someone.

The post Google Authenticator app 7.0 requires cloud sign-in. Here’s how to go back to 6.0. appeared first on Alexandros Georgiou.

Versions

On my Ubuntu 16 installation (let’s call it example1.com) I have a project on this version of trac:

$ lsb_release  -d
Description:    Ubuntu 16.10
$ tracd --version
tracd 1.0.12

I had good(-ish) reasons to migrate the entire project to a copy on an Ubuntu 10 machine.

$ lsb_release -d
Description:    Ubuntu 10.04.4 LTS

Installing trac

These are the resources that you need to be aware of:

• https://trac.edgewall.org/wiki/TracOnUbuntu
• https://trac.edgewall.org/wiki/MySqlDb

I first installed trac via the old-releases.ubuntu.com repository.

$ sudo apt-get install trac

This installed an earlier version than the one I had.

$ tracd --version
tracd 0.11.7

Setting up the new (old) trac

Rather than upgrading the entire system with do-release-upgrade, I decided to work with this version.

You will need the python-mysqldb module on example2.com to access a MySQL database. If you’re using PostgreSQL the procedure should be similar. YMMV.

$ sudo apt-get install python-mysqldb

First, copy the assets of the project environment. This is a directory tree that you can copy over using rsync.

rsync -r example1.com:/path-to-trac-env example2.com:/path-to-trac-env

For simplicity we’ll keep everything the same: file directories, database name and database credentials, although you could change these. Your database settings are in the /path-to-trac-env/conf/trac.ini file. You want the database variable under the [trac] section, which should look something like:

[trac]

database = mysql://tracuser:tracpassword@localhost:3306/trac-env

You will want to create an empty MySQL database where your project will live. You will need the MySQL client on example2.com, so if you don’t have it, install it with:

sudo apt-get install mysql-client

You will then want to login as root

mysql -u root -p

and create the database, (using the utf8_bin collation)

CREATE DATABASE `trac-env` DEFAULT CHARACTER SET utf8 COLLATE utf8_bin;

and finally create the user:

GRANT ALL ON `trac-env`.* TO tracuser@localhost IDENTIFIED BY 'tracpassword';

Exit the MySQL client with Ctrl-D and import a standard SQL dump of your database from example1.com. For instance, if you like one-liners, you might do this on example2.com:

ssh example1.com "mysqldump -u tracuser -ptracpassword --single-transaction trac-env | gzip -9" | zcat | mysql -u tracuser -ptracpassword trac-env

Nasty hack FTW

Now start tracd and visit the installation via your web browser. You should see an error like this:

 Trac detected an internal error:

ValueError: timestamp out of range for platform time_t

This is because all timestamps in this newer version of trac are in microseconds, rather than seconds. Here is a (somewhat) relevant ticket.

I went ahead and hacked the DB thusly:

update ignore attachment set time = floor( time / 10000000);
update ignore auth_cookie set time = floor( time / 10000000);
update ignore revision set time = floor( time / 10000000);
update ignore ticket set time = floor( time / 10000000);
update ignore ticket set changetime = floor( changetime / 10000000);
update ignore ticket_change set time = floor( time / 10000000);
update ignore version set time = floor( time / 10000000);
update ignore wiki set time = floor( time / 10000000);

These are all the timestamp columns in the DB. Dividing by a million converts millionths of a second to seconds and the floor function makes sure that the result is still an integer.

The ignore argument is there only because I had one single collision in one ticket comment. Needless to say, this is a nasty hack, so don’t rely on it too much.

But, for my purposes, “It Works”!

The post How to migrate trac MySQL-based project from trac 1.0.12 to trac 0.11.7 appeared first on Alexandros Georgiou.