Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development #170

Closed
amilopowers opened this issue Dec 15, 2017 · 10 comments
Closed

Development #170

amilopowers opened this issue Dec 15, 2017 · 10 comments

Comments

@amilopowers
Copy link

Hello

Is this app still under development?

F-Droid says that it has "a known vulnerability". And I am wondering what that might be.

Thanks for that amazing app!

@amilopowers
Copy link
Author

Age below gives more info but I am a regular user and don't really know what that means.

https://f-droid.org/wiki/page/AntiFeature:KnownVuln

@ghost
Copy link

ghost commented Dec 29, 2017

Yea other people would also like to know about this? if its updated here why isnt it pushed to F-droid then?

@smichel17
Copy link

The most recent version on f-droid is 1.5, updated 706 days ago. I see there have been many commits since then, so a new release would be nice.

@ben-8409
Copy link

I realize F-Droid is probably the preferred way to get this app, but an update on Google Play would be appreciated, too.

@mario-d-s
Copy link

@npmccallum Please let us know this project isn't dead 🙏

I don't know who's in charge of the FreeOTP org but seeing 0 people (not even yourself) is worrying.
Do you intend to pass the torch?

@max-wittig
Copy link
Contributor

I think andOTP is the best alternative with many features, including keystore encryption, backups etc.
Also it is updated and maintained.

npmccallum added a commit to npmccallum/freeotp-android that referenced this issue Jul 6, 2018
This commit contains a long-awaited rewrite to address many long-standing
issues. This patch contains:

1. a totally new UI focused on Material Design compliance
2. all tokens are stored in the Android KeyStore
3. support for sending codes over Bluetooth LE to computers via Jelling
4. extensive unit testing
5. expanded branding options (cf. image= and color=)
6. default branding for major issuers (needs docs)
7. sane behavior surrounding the addition of multiple tokens
8. warnings on weak cryptographic parameters
9. token locking (authentication required to get token code)

All this goodness comes with some costs:

1. Android API 23+ is required. This is necessary for KeyStore access.
2. Manual token adding is removed. Use a QR code or click a otpauth:// link.
3. Use of the KeyStore makes token secrets impossible to extract.
4. Tokens are now immutable. Existing changes will be discarded during upgrade.

Closes: freeotp#190
Closes: freeotp#96
Closes: freeotp#78
Closes: freeotp#77
Closes: freeotp#68
Closes: freeotp#55
Closes: freeotp#48
Closes: freeotp#45
Closes: freeotp#43
Closes: freeotp#16
Fixes: freeotp#187
Fixes: freeotp#185
Fixes: freeotp#176
Fixes: freeotp#175
Fixes: freeotp#172
Fixes: freeotp#170
Fixes: freeotp#167
Fixes: freeotp#161
Fixes: freeotp#144
Fixes: freeotp#142
Fixes: freeotp#136
Fixes: freeotp#123
Fixes: freeotp#122
Fixes: freeotp#110
Fixes: freeotp#90
Fixes: freeotp#89
Fixes: freeotp#84
Fixes: freeotp#74
Fixes: freeotp#69
Fixes: freeotp#67
Fixes: freeotp#66
Fixes: freeotp#65
Fixes: freeotp#63
Fixes: freeotp#62
Fixes: freeotp#61
Fixes: freeotp#58
Fixes: freeotp#54
Fixes: freeotp#53
Fixes: freeotp#49
Fixes: freeotp#40
Fixes: freeotp#21
Fixes: freeotp#14
Fixes: freeotp#8
Fixes: freeotp#7
Fixes: freeotp#6
npmccallum added a commit to npmccallum/freeotp-android that referenced this issue Jul 6, 2018
This commit contains a long-awaited rewrite to address many long-standing
issues. This patch contains:

1. a totally new UI focused on Material Design compliance
2. all tokens are stored in the Android KeyStore
3. support for sending codes over Bluetooth LE to computers via Jelling
4. extensive unit testing
5. expanded branding options (cf. image= and color=)
6. default branding for major issuers (needs docs)
7. sane behavior surrounding the addition of multiple tokens
8. warnings on weak cryptographic parameters
9. token locking (authentication required to get token code)

All this goodness comes with some costs:

1. Android API 23+ is required. This is necessary for KeyStore access.
2. Manual token adding is gone. Use a QR code or click a otpauth:// link.
3. Use of the KeyStore makes token secrets impossible to extract.
4. Tokens are immutable. Existing changes will be discarded during upgrade.

Closes: freeotp#190
Closes: freeotp#96
Closes: freeotp#78
Closes: freeotp#77
Closes: freeotp#68
Closes: freeotp#55
Closes: freeotp#48
Closes: freeotp#45
Closes: freeotp#43
Closes: freeotp#16
Fixes: freeotp#187
Fixes: freeotp#185
Fixes: freeotp#176
Fixes: freeotp#175
Fixes: freeotp#172
Fixes: freeotp#170
Fixes: freeotp#167
Fixes: freeotp#161
Fixes: freeotp#144
Fixes: freeotp#142
Fixes: freeotp#136
Fixes: freeotp#123
Fixes: freeotp#122
Fixes: freeotp#110
Fixes: freeotp#90
Fixes: freeotp#89
Fixes: freeotp#84
Fixes: freeotp#74
Fixes: freeotp#69
Fixes: freeotp#67
Fixes: freeotp#66
Fixes: freeotp#65
Fixes: freeotp#63
Fixes: freeotp#62
Fixes: freeotp#61
Fixes: freeotp#58
Fixes: freeotp#54
Fixes: freeotp#53
Fixes: freeotp#49
Fixes: freeotp#40
Fixes: freeotp#21
Fixes: freeotp#14
Fixes: freeotp#8
Fixes: freeotp#7
Fixes: freeotp#6
npmccallum added a commit to npmccallum/freeotp-android that referenced this issue Jul 6, 2018
This commit contains a long-awaited rewrite to address many long-standing
issues. This patch contains:

1. a totally new UI focused on Material Design compliance
2. all tokens are stored in the Android KeyStore
3. support for sending codes over Bluetooth LE to computers via Jelling
4. extensive unit testing
5. expanded branding options (cf. image= and color=)
6. default branding for major issuers (needs docs)
7. sane behavior surrounding the addition of multiple tokens
8. warnings on weak cryptographic parameters
9. token locking (authentication required to get token code)

All this goodness comes with some costs:

1. Android API 23+ is required. This is necessary for KeyStore access.
2. Manual token adding is gone. Use QR code or otpauth:// link.
3. Use of the KeyStore makes token secrets impossible to extract.
4. Tokens are immutable. Existing changes will be discarded on upgrade.

Closes: freeotp#190
Closes: freeotp#96
Closes: freeotp#78
Closes: freeotp#77
Closes: freeotp#68
Closes: freeotp#55
Closes: freeotp#48
Closes: freeotp#45
Closes: freeotp#43
Closes: freeotp#16
Fixes: freeotp#187
Fixes: freeotp#185
Fixes: freeotp#176
Fixes: freeotp#175
Fixes: freeotp#172
Fixes: freeotp#170
Fixes: freeotp#167
Fixes: freeotp#161
Fixes: freeotp#144
Fixes: freeotp#142
Fixes: freeotp#136
Fixes: freeotp#123
Fixes: freeotp#122
Fixes: freeotp#110
Fixes: freeotp#90
Fixes: freeotp#89
Fixes: freeotp#84
Fixes: freeotp#74
Fixes: freeotp#69
Fixes: freeotp#67
Fixes: freeotp#66
Fixes: freeotp#65
Fixes: freeotp#63
Fixes: freeotp#62
Fixes: freeotp#61
Fixes: freeotp#58
Fixes: freeotp#54
Fixes: freeotp#53
Fixes: freeotp#49
Fixes: freeotp#40
Fixes: freeotp#21
Fixes: freeotp#14
Fixes: freeotp#8
Fixes: freeotp#7
Fixes: freeotp#6
npmccallum added a commit to npmccallum/freeotp-android that referenced this issue Jul 6, 2018
This commit contains a long-awaited rewrite to address many long-standing
issues. This patch contains:

1. a totally new UI focused on Material Design compliance
2. all tokens are stored in the Android KeyStore
3. support for sending codes over Bluetooth LE to computers via Jelling
4. extensive unit testing
5. expanded branding options (cf. image= and color=)
6. default branding for major issuers (needs docs)
7. sane behavior surrounding the addition of multiple tokens
8. warnings on weak cryptographic parameters
9. token locking (authentication required to get token code)

All this goodness comes with some costs:

1. Android API 23+ is required. This is necessary for KeyStore access.
2. Manual token adding is gone. Use QR code or otpauth:// link.
3. Use of the KeyStore makes token secrets impossible to extract.
4. Tokens are immutable. Existing changes will be discarded on upgrade.

Closes: freeotp#190
Closes: freeotp#96
Closes: freeotp#78
Closes: freeotp#77
Closes: freeotp#68
Closes: freeotp#55
Closes: freeotp#48
Closes: freeotp#45
Closes: freeotp#43
Closes: freeotp#16
Fixes: freeotp#187
Fixes: freeotp#185
Fixes: freeotp#176
Fixes: freeotp#175
Fixes: freeotp#172
Fixes: freeotp#170
Fixes: freeotp#167
Fixes: freeotp#161
Fixes: freeotp#144
Fixes: freeotp#142
Fixes: freeotp#136
Fixes: freeotp#123
Fixes: freeotp#122
Fixes: freeotp#110
Fixes: freeotp#90
Fixes: freeotp#89
Fixes: freeotp#84
Fixes: freeotp#74
Fixes: freeotp#69
Fixes: freeotp#67
Fixes: freeotp#66
Fixes: freeotp#65
Fixes: freeotp#63
Fixes: freeotp#62
Fixes: freeotp#61
Fixes: freeotp#58
Fixes: freeotp#54
Fixes: freeotp#53
Fixes: freeotp#49
Fixes: freeotp#40
Fixes: freeotp#21
Fixes: freeotp#14
Fixes: freeotp#8
Fixes: freeotp#7
Fixes: freeotp#6
@oilian
Copy link

oilian commented Aug 27, 2018

Thanks for creating freeotp. It's a great application.
As the question was not answered by now, I would like to know if freeotp is still maintained, or if this is no longer the case.
Also, when will a new version with the commit from July 6th be released?

Thanks
Oliver

@dpal
Copy link

dpal commented Jul 30, 2019

The project is still alive.

Dmitri

@adambkaplan
Copy link
Contributor

This project has restarted active development. We're working on Backup & Restore capabilities as the primary feature for a v2.0.0 release.

@max-wittig
Copy link
Contributor

@adambkaplan Wouldn't it make more sense to contribute missing features to https://github.com/andOTP/andOTP. FreeOTP is so far behind.

justin-stephenson pushed a commit to justin-stephenson/freeotp-android that referenced this issue Jan 22, 2021
This commit contains a long-awaited rewrite to address many long-standing
issues. This patch contains:

1. a totally new UI focused on Material Design compliance
2. all tokens are stored in the Android KeyStore
3. support for sending codes over Bluetooth LE to computers via Jelling
4. extensive unit testing
5. expanded branding options (cf. image= and color=)
6. default branding for major issuers (needs docs)
7. sane behavior surrounding the addition of multiple tokens
8. warnings on weak cryptographic parameters
9. token locking (authentication required to get token code)

All this goodness comes with some costs:

1. Android API 23+ is required. This is necessary for KeyStore access.
2. Manual token adding is gone. Use QR code or otpauth:// link.
3. Use of the KeyStore makes token secrets impossible to extract.
4. Tokens are immutable. Existing changes will be discarded on upgrade.

Closes: freeotp#190
Closes: freeotp#96
Closes: freeotp#78
Closes: freeotp#77
Closes: freeotp#68
Closes: freeotp#55
Closes: freeotp#48
Closes: freeotp#45
Closes: freeotp#43
Closes: freeotp#16
Fixes: freeotp#187
Fixes: freeotp#185
Fixes: freeotp#176
Fixes: freeotp#175
Fixes: freeotp#172
Fixes: freeotp#170
Fixes: freeotp#167
Fixes: freeotp#161
Fixes: freeotp#144
Fixes: freeotp#142
Fixes: freeotp#136
Fixes: freeotp#123
Fixes: freeotp#122
Fixes: freeotp#110
Fixes: freeotp#90
Fixes: freeotp#89
Fixes: freeotp#84
Fixes: freeotp#74
Fixes: freeotp#69
Fixes: freeotp#67
Fixes: freeotp#66
Fixes: freeotp#65
Fixes: freeotp#63
Fixes: freeotp#62
Fixes: freeotp#61
Fixes: freeotp#58
Fixes: freeotp#54
Fixes: freeotp#53
Fixes: freeotp#49
Fixes: freeotp#40
Fixes: freeotp#21
Fixes: freeotp#14
Fixes: freeotp#8
Fixes: freeotp#7
Fixes: freeotp#6
justin-stephenson pushed a commit that referenced this issue Jan 5, 2023
This commit contains a long-awaited rewrite to address many long-standing
issues. This patch contains:

1. a totally new UI focused on Material Design compliance
2. all tokens are stored in the Android KeyStore
3. support for sending codes over Bluetooth LE to computers via Jelling
4. extensive unit testing
5. expanded branding options (cf. image= and color=)
6. default branding for major issuers (needs docs)
7. sane behavior surrounding the addition of multiple tokens
8. warnings on weak cryptographic parameters
9. token locking (authentication required to get token code)

All this goodness comes with some costs:

1. Android API 23+ is required. This is necessary for KeyStore access.
2. Manual token adding is gone. Use QR code or otpauth:// link.
3. Use of the KeyStore makes token secrets impossible to extract.
4. Tokens are immutable. Existing changes will be discarded on upgrade.

Closes: #190
Closes: #96
Closes: #78
Closes: #77
Closes: #68
Closes: #55
Closes: #48
Closes: #45
Closes: #43
Closes: #16
Fixes: #187
Fixes: #185
Fixes: #176
Fixes: #175
Fixes: #172
Fixes: #170
Fixes: #167
Fixes: #161
Fixes: #144
Fixes: #142
Fixes: #136
Fixes: #123
Fixes: #122
Fixes: #110
Fixes: #90
Fixes: #89
Fixes: #84
Fixes: #74
Fixes: #69
Fixes: #67
Fixes: #66
Fixes: #65
Fixes: #63
Fixes: #62
Fixes: #61
Fixes: #58
Fixes: #54
Fixes: #53
Fixes: #49
Fixes: #40
Fixes: #21
Fixes: #14
Fixes: #8
Fixes: #7
Fixes: #6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants