harbour-foilauth-1.1.5-1.aarch64.rpm | 346.14 KB | 15/01/2023 - 06:22 |
harbour-foilauth-1.1.5-1.armv7hl.rpm | 317.69 KB | 15/01/2023 - 06:22 |
harbour-foilauth-1.1.5-1.i486.rpm | 362.39 KB | 15/01/2023 - 06:22 |
harbour-foilauth-1.1.4-1.aarch64.rpm | 331.35 KB | 26/09/2022 - 20:00 |
harbour-foilauth-1.1.4-1.armv7hl.rpm | 303.98 KB | 26/09/2022 - 20:00 |
harbour-foilauth-1.1.4-1.i486.rpm | 347 KB | 26/09/2022 - 20:00 |
harbour-foilauth-1.1.3-1.aarch64.rpm | 332.16 KB | 17/08/2022 - 02:32 |
harbour-foilauth-1.1.3-1.armv7hl.rpm | 303.84 KB | 17/08/2022 - 02:32 |
harbour-foilauth-1.1.3-1.i486.rpm | 346.76 KB | 17/08/2022 - 02:32 |
harbour-foilauth-1.1.2-1.aarch64.rpm | 321.5 KB | 25/07/2022 - 04:57 |
harbour-foilauth-1.1.2-1.armv7hl.rpm | 292.19 KB | 25/07/2022 - 04:57 |
harbour-foilauth-1.1.2-1.i486.rpm | 335.18 KB | 25/07/2022 - 04:57 |
harbour-foilauth-1.1.1-1.aarch64.rpm | 365.23 KB | 13/06/2022 - 04:58 |
harbour-foilauth-1.1.1-1.armv7hl.rpm | 328.79 KB | 13/06/2022 - 04:58 |
harbour-foilauth-1.1.1-1.i486.rpm | 372.66 KB | 13/06/2022 - 04:58 |
harbour-foilauth-1.1.0-1.aarch64.rpm | 364.06 KB | 20/03/2022 - 21:13 |
harbour-foilauth-1.1.0-1.armv7hl.rpm | 327.55 KB | 20/03/2022 - 21:13 |
harbour-foilauth-1.1.0-1.i486.rpm | 370.51 KB | 20/03/2022 - 21:13 |
harbour-foilauth-1.0.21-1.aarch64.rpm | 364.35 KB | 15/11/2021 - 02:26 |
harbour-foilauth-1.0.21-1.armv7hl.rpm | 327.73 KB | 15/11/2021 - 02:26 |
harbour-foilauth-1.0.21-1.i486.rpm | 372.17 KB | 15/11/2021 - 02:26 |
harbour-foilauth-1.0.20-1.aarch64.rpm | 364.29 KB | 05/11/2021 - 04:45 |
harbour-foilauth-1.0.20-1.armv7hl.rpm | 721.42 KB | 05/11/2021 - 04:45 |
harbour-foilauth-1.0.20-1.i486.rpm | 843.93 KB | 05/11/2021 - 04:45 |
harbour-foilauth-1.0.19-1.aarch64.rpm | 363.92 KB | 10/10/2021 - 21:43 |
harbour-foilauth-1.0.19-1.armv7hl.rpm | 327.26 KB | 10/10/2021 - 21:43 |
harbour-foilauth-1.0.19-1.i486.rpm | 370.8 KB | 10/10/2021 - 21:43 |
harbour-foilauth-1.0.18-1.aarch64.rpm | 369.01 KB | 30/07/2021 - 21:13 |
harbour-foilauth-1.0.18-1.armv7hl.rpm | 331.71 KB | 30/07/2021 - 21:13 |
harbour-foilauth-1.0.18-1.i486.rpm | 375.73 KB | 30/07/2021 - 21:13 |
harbour-foilauth-1.0.17-22.1.aarch64.rpm | 353.09 KB | 18/04/2021 - 00:26 |
harbour-foilauth-1.0.17-22.1.armv7hl.rpm | 309.04 KB | 18/04/2021 - 00:26 |
harbour-foilauth-1.0.17-22.1.i486.rpm | 361.11 KB | 18/04/2021 - 00:26 |
harbour-foilauth-1.0.16-21.1.aarch64.rpm | 348.66 KB | 23/02/2021 - 20:07 |
harbour-foilauth-1.0.16-21.1.armv7hl.rpm | 305.05 KB | 23/02/2021 - 20:07 |
harbour-foilauth-1.0.16-21.1.i486.rpm | 357.06 KB | 23/02/2021 - 20:07 |
harbour-foilauth-1.0.15-20.1.aarch64.rpm | 346.32 KB | 23/02/2021 - 05:19 |
harbour-foilauth-1.0.15-20.1.armv7hl.rpm | 304.09 KB | 09/01/2021 - 07:06 |
harbour-foilauth-1.0.15-20.1.i486.rpm | 355.31 KB | 09/01/2021 - 07:06 |
harbour-foilauth-1.0.14-19.1.armv7hl.rpm | 303.1 KB | 20/12/2020 - 06:53 |
harbour-foilauth-1.0.14-19.1.i486.rpm | 354.77 KB | 20/12/2020 - 06:53 |
harbour-foilauth-1.0.13-18.1.armv7hl.rpm | 301.55 KB | 11/12/2020 - 06:45 |
harbour-foilauth-1.0.13-18.1.i486.rpm | 353.98 KB | 11/12/2020 - 06:45 |
harbour-foilauth-1.0.12-17.1.armv7hl.rpm | 302.42 KB | 30/11/2020 - 18:17 |
harbour-foilauth-1.0.12-17.1.i486.rpm | 353.5 KB | 30/11/2020 - 18:17 |
harbour-foilauth-1.0.11-16.1.armv7hl.rpm | 300.52 KB | 16/11/2020 - 13:58 |
harbour-foilauth-1.0.11-16.1.i486.rpm | 352.83 KB | 16/11/2020 - 13:58 |
harbour-foilauth-1.0.10-15.1.armv7hl.rpm | 300.43 KB | 16/11/2020 - 03:39 |
harbour-foilauth-1.0.10-15.1.i486.rpm | 352.43 KB | 16/11/2020 - 03:39 |
harbour-foilauth-1.0.9-14.1.armv7hl.rpm | 299.11 KB | 13/10/2020 - 01:29 |
harbour-foilauth-1.0.9-14.1.i486.rpm | 351.27 KB | 13/10/2020 - 01:29 |
harbour-foilauth-1.0.8-12.1.armv7hl.rpm | 300.59 KB | 08/10/2020 - 02:23 |
harbour-foilauth-1.0.8-12.1.i486.rpm | 353.29 KB | 08/10/2020 - 02:23 |
harbour-foilauth-1.0.7-11.1.armv7hl.rpm | 298.25 KB | 03/01/2020 - 19:39 |
harbour-foilauth-1.0.7-11.1.i486.rpm | 350.45 KB | 03/01/2020 - 19:39 |
harbour-foilauth-1.0.6-10.1.armv7hl.rpm | 297.09 KB | 12/11/2019 - 03:02 |
harbour-foilauth-1.0.6-10.1.i486.rpm | 348.5 KB | 12/11/2019 - 03:02 |
harbour-foilauth-1.0.5-9.1.armv7hl.rpm | 289.9 KB | 22/04/2019 - 13:06 |
harbour-foilauth-1.0.5-9.1.i486.rpm | 340.12 KB | 22/04/2019 - 13:06 |
harbour-foilauth-1.0.4-8.1.armv7hl.rpm | 289.68 KB | 13/04/2019 - 00:41 |
harbour-foilauth-1.0.4-8.1.i486.rpm | 339.26 KB | 13/04/2019 - 00:41 |
harbour-foilauth-1.0.3-7.1.armv7hl.rpm | 288.45 KB | 11/04/2019 - 15:03 |
harbour-foilauth-1.0.3-7.1.i486.rpm | 337.9 KB | 11/04/2019 - 15:03 |
harbour-foilauth-1.0.2-6.1.armv7hl.rpm | 287.17 KB | 11/04/2019 - 01:18 |
harbour-foilauth-1.0.2-6.1.i486.rpm | 336.38 KB | 11/04/2019 - 01:18 |
harbour-foilauth-1.0.1-5.1.armv7hl.rpm | 285.06 KB | 10/04/2019 - 18:37 |
harbour-foilauth-1.0.1-5.1.i486.rpm | 335.06 KB | 10/04/2019 - 18:37 |
harbour-foilauth-1.0.0-4.1.armv7hl.rpm | 284.31 KB | 10/04/2019 - 14:46 |
harbour-foilauth-1.0.0-4.1.i486.rpm | 333.54 KB | 10/04/2019 - 14:46 |
Comments
poetaster
Fri, 2023/02/03 - 12:28
Permalink
Just wanted to note that fail auth works really well. Thanks!
jolla4ever
Tue, 2022/08/23 - 00:55
Permalink
@slava, a must have programm. Thank you very much!
slava
Fri, 2022/06/17 - 01:48
Permalink
If Foil Auth settings page doesn't show up, you may have to fix
/usr/share/jolla-settings/pages/ApplicationsGrid.qml
(look forroot.openSandboxed
) or you can modify/apps/harbour-foilauth/autoLock
from the command line e.g.dconf write /apps/harbour-foilauth/autoLock false
. Sadboxing may have messed things up in the application settings area too.norayr
Thu, 2021/11/04 - 19:06
Permalink
3vixan, i did that once and it worked.
lqramen
Thu, 2021/11/04 - 13:32
Permalink
SF 4.3, cannot install due to missing libcrypto.so.1
lpr
Sun, 2021/11/07 - 21:53
Permalink
https://openrepos.net/sites/default/files/packages/7598/openssl-libs10-1... will give you libcrypto.so.1
slava
Thu, 2021/11/04 - 14:47
Permalink
I swear I didn't delete it)) Seriously speaking, it looks like I have no choice but to link openssl statically in order to keep the app compatible with both systems not having libcrypto.so.10 and those not having libcrypto.so.1.1 which sadly will make the app HUGE. That sucks. It really does. Especially considering that libcrypto.so.10 was allowed in Jolla Store.
In the meantime, you can find a build linked against your favorite release from Chum. With the introduction of SFOS 4.3, releases are no longer backward compatible. It's hard to describe how I detest that.
lpr
Sun, 2021/11/07 - 21:55
Permalink
another round here: no, don't do that but link dynamically to openssl1.1 and jolla1 users just install openssl from here: https://openrepos.net/content/lpr/curl
slava
Sun, 2021/11/07 - 22:09
Permalink
And another round here: Chum is your friend if you want an armv7hl build linked against openssl1.1. There's nothing wrong with linking openssl1.0 or anything else statically if it's not part of the OS anymore.
lpr
Sun, 2021/11/07 - 22:16
Permalink
to all SFOS users: please update your openssl.
Then a version linked against 1.1.1 is backward compatible
slava
Sun, 2021/11/07 - 22:31
Permalink
Oh come on. A version dynamically linked with openssl1.1 can't be backward compatible with the systems which don't have openssl1.1.
lpr
Mon, 2021/11/08 - 02:26
Permalink
just install 1.1 then it is
slava
Mon, 2021/11/08 - 04:26
Permalink
I can't do it for the user. And if the user is skilled enough to do it, then he/she must be skilled enough to install a variant of my app linked against openssl1.1 from already mentioned Chum. Right?
I did consider statically linking openssl1.1, but it didn't compile out of the box against sufficiently old SDK. So it's not as trivial as you're trying to make it sound.
3vixan
Thu, 2021/11/04 - 18:59
Permalink
Can I copy the last key file in another SFOS phone and reload the OTPs?
slava
Thu, 2021/11/04 - 19:27
Permalink
If you copy the key
~/.local/share/foil/foil.key
and encrypted files from~/Documents/FoilAuth
to another phone, the secrets should get loaded. Note, however, that if you overwrite~/.local/share/foil/foil.key
with a different one, you lose access to the secrets encrypted with the old key. Be careful.Another (and safer) way to transfer OTP secrets between devices is a QR code - show it on one device and then read from the other, that works between devices with different keys. There is even a bulk sharing function on the Select page. No bulk import though (yet).
cquence
Sat, 2021/06/05 - 02:48
Permalink
I had to download the aarch64 rpm from the github page, somehow it was not available through Openrepos. Thanks for this great app. Migration from XA2 was easy using the QR code
slava
Sat, 2021/06/05 - 04:10
Permalink
Strange, aarch64 rpm is available from this page too. Anyway, I'm glad that you've got it installed one way or the other. Cheers!
MacGyver
Fri, 2020/10/23 - 02:33
Permalink
Just wondering, if you ever thought of having a way to backup things to SD card from app itself?
Now I have a script, that creates a backup of the files on my SD card, but its a bit of a hassle.
slava
Fri, 2020/10/30 - 06:05
Permalink
Yes, I did think about it (and even drafted a prototype) but decided to write a separate backup app instead, which would cover all my Foil apps at once and possibly any custom user-specified dconf/filesystem entries in addition to that. But that app isn't ready yet.
MacGyver
Fri, 2020/10/30 - 15:50
Permalink
Ok, cool, I will keep my eyes open for it then :)
MacGyver
Fri, 2019/11/29 - 03:49
Permalink
Are you adding HOTP support in near future? Id like to use this app instead of SailOTP, just cause it has the codes behind encrypted password and not open to everyone like SailOTP if they get access to phone.
I guess no need for import/export, cause you can just copy the
~/Documents/FoilAuth
file? Do I need to backup the~/.local/share/foil/foil.key
file too? Just wanna know how correctly backup things, if anything bad happens to phone!I have multiple Jolla devices and would like to copy tokens to those too. How can I accomplish this?
slava
Fri, 2019/11/29 - 18:36
Permalink
You mean counter-based OTP? That shouldn't be too hard, I just wasn't sure if anyone is using that.
As for backup/export, yes you need both
~/Documents/FoilAuth
directory and~/.local/share/foil/foil.key
file - the latter is the RSA private key required for decrypting your tokens (the key itself being AES-encrypted with your password)MacGyver
Sat, 2019/11/30 - 05:46
Permalink
Actually, I might need to recheck, if HOTP is used anymore, I guess TOTP has surpassed it these days.
And thanks for the backup info, now I can sleep knowing my tokens are safely backed up, and encrypted.
Surprisingly few authentication apps have own password as added security layer. I guess most people think it more of a hassle...
slava
Sat, 2019/11/30 - 15:11
Permalink
I'll tell you more :) If you build foilmsg tool then you can decrypt your auth tokens on your computer, you don't need a phone for that. Suppose you have pulled a file named
5E6FD647B7683FAC
from your~Documents/FoilAuth
directory. Andfoil.key
file too, of course. Then you can do something like this:where
foil.key
is your foil private key file,xxxxxxxx
is your foil password. Your secret token is written to the file namedsecret
in the binary form, i.e. as a sequence of raw bytes - in order to get the token string the way you see it in FoilAuth app, you would have to run your secret bytes through a Base32 encoder.MacGyver
Sat, 2019/11/30 - 18:31
Permalink
Interesting, so you could easily move your tokens to other apps too using this method, if needed? Anything can happen, gotta be prepared :)
24mu13
Sun, 2019/11/17 - 20:12
Permalink
Interesting thinking about fingerprint authentication: I'm still convinced it's useful and convenient, anyway. What about to have both for instance? Password first time, fingerprint for kind of quick unlock?
nobodyinperson
Sat, 2019/10/12 - 13:29
Permalink
This is a really neat app!
TheJullus
Mon, 2019/09/02 - 18:32
Permalink
Would it be possible to make an option to use fingerprint authtentication for unlocking these foil apps? (Possible in sense of being able to do it and also if it's against the security idea you have (as in "password stronger that PIN code"))
slava
Mon, 2019/09/02 - 19:01
Permalink
Hehe, I was actually considering something like that but it turned out to be impractical and in many ways less secure. Probably the best argument which I heard against that or any kind of biometric authentication in general - "you can change your password but you can't change your fingerprint". When it comes to the actual implementation, it turns out that on most systems you don't have access to raw fingerprint images. You can only match the current fingerprint against the training set and that's it. It's just not enough to generate any kind of hash or anything that could be used as an encryption key.
TheJullus
Mon, 2019/08/05 - 10:58
Permalink
Is it some how possible to use old codes after resetting the phone? I tried to use this app with same password but it says there is no codes (or notes in FoilNotes) Ps. Would it be possible to use fingerprint authentication to open the Foil apps?
Pages