StageStyle.UNIFIED doesn't work properly on all machines, try to figure out why and propose fix for this issue. According to my findings this related to hardware problems - graphic card.

Windows have clipboard history.

https://www.howtogeek.com/671222/how-to-enable-and-use-clipboard-history-on-windows-10/

Although it could be disabled - user might want it to be enabled or user can be unaware that it is enabled.

The problem is that if user used clipboard to copy/paste password - it will be saved in the clipboard history.

To reproduce:

1. Open pasSHA UI and copy password using CTRL + C
2. Verify immediately that you can paste it.
3. Wait for the clipboard timeout to pass and verify that password is no longer in clipboard.
4. Press WIN + V. The clipboard history will be shown with a password in it.

Since we're caring about clearing the clipboard after a timeout we could also care to cleaning up a history.

• Replace XC with exceptions.

• Modules in a lower level should throw low level exceptions. If module on a higher level catches low level exceptions it should be wrapped with higher level exception as a cause. For example if Database creation should throw exception CreateDatabaseError exception, while it can be cause by either PermissionDenied, FileNotFound or any other lower level exception.

When you enter master password it takes long time to load database - it looks like freeze.

It would be really great to see progress bar showing the progress of loading and keep UI responsive same time (be able to move window).

P.S. I can implement it, but I can't compile and run project because javafx is missing and should be added as dependency.

currently if any directories are missing - pasSHA will not launch.

Migrate to RSA-4096, also review whole algorith and prime number generation.

Definition of Done

1. After minimize, Application should restore at the same coords
2. After close, Application should restore at the same coords

RCA: Bug occurs due to JavaFX framework causes stage.X & .Y change upon press of minimization button, despite if we are catching an event.

• Get rid of Vector and any other old data structures.

• Try and use as much as possible generic collections, rather then specific implementations, where possible. In general for parameters and fields it's better to have the most generic type possible. For example: method that only iterates elements should receive Iterable<X> instead of any collection, like List<X>.

• Replace our homemade logger with a library Log4j2.

• Create configuration for the users. I suggest having circular logging to files.

• Create template configuration for developers. I think best to have 2 outputs.

1. Async output to file with lowest log level output. Circular logging to files.
2. Sync output to console. Default level to be INFO. Developers then can alter the level as they need. Default pattern can be same as we have currently.

Blocked by #42

• Use JUnit and Mockito for testing

• Increase coverage of tests

New password feature - no preview, no options to change rules, no option to regenerate password.

1. Ctrl+V
2. Type-in default

• Import current eclipse formatter config

• Adjust it as you see fit and reformat all code

• Remove eclipse configuration from repository

• Export intellij configuration

• Create/Update CONTRIBUTING.md with practice to use auto code format.

It's necessary to prevent data loss if PC powers off while save in progress.

Given:

class B {
    private A a;
}

Instead of having:

class A {
}

Should have:

interface A {
}

class X implements A {
}

Additionally class B should not instantiate A or X.
Class B should either receive A in a constructor or through setter.

This will decrease coupling and allow testing separately different components.

Blocked by #43.

• Implement pipeline in GitHub.

• Create a coverage report.

• Optionally we can set up CD as well.

It is more more cooler now, but could we implement this:

• Write stages - Key generation, Password loading etc.
• Approx. estimation of completion based on some metrics

Blocked by #42.

If still anything left after 42:

• Try and get rid from static methods as much as possible

• Try and get rid from singletone patterns. They are bad for testing.

Blocked by #41.

• Check that there are no methods like getOn...Action where not necessary.
  In most cases they can be replaced with on...Action.

• Instead of saving Java objects using Object stream use JSON.

• Jackson library can be used to easy POJO conversion into JSON string and backwards.

• Re-design user data file. I think it is better to use have one JSON object (encrypted of course) that holds different fields (including all passwords). @lyubick please comment on that.
  Also I think it would be better to have binary instead of text file for passwords.

This might be needed to store passwords file on a cloud (using Google Drive, DropBox e.t.c)

Use FXML everywhere.

• Create list of screens/forms that must be moved to FXML and create checkbox items in this list.

• @curious-odd-man create branch and create sample how to use FXML

After @curious-odd-man refactoring russian language broke.

Probably, we should consider an option to change Master Password (and all created passwords as a result),

Java have built in implementation for SHA and RSA (and any other) algorithms.

We could use built-in algorithms and as a bonus we can leave choice of algorithms for the end users.

https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#ciphertrans

• Create configuration for inspections in IntelliJ idea.

• Export the configuration so that everyone one a project could use it.

• Create/Update CONTRIBUTING.md file with practices that should be followed by each developer.

Window size should take into consideration Password Names when setting width.

After adding and deleting password, state does not change to "unchanged".