bugraonal/passman

Password manager application

CS320 Fall 2017 Project

PassMan - Password Manager

Getting Started

Prerequisites

You have to have the following tools in order to successfully compile the code.

Java 6 or later

Project Structure

General folder structure

In general, we agreed on an MVC structure.

There are four different folders called

• GUI
• GUIListeners
• PassMan
• Tests

GUI

In GUI we keep the user interface of the software. All view related methods and functionalities will be here.

GUIListeners

This is where we create the listeners that the user interface will use to communicate with the user. Any graphical changes requiring input will reside here.

PassMan

Here we keep all non-view related source. Database IO, Passman execution, AES/SHA256 encryption and so will have their sources here.

Tests

All of our tests will be here. The tests will be done with JUnit. If any test fail we should create an issue for that test.

Documents

Report

Report

Contributing

Please don't make direct changes to the master branch. Use a seperate branch with

git checkout -b <things-that-you're-going-to-change>

and after testing it thoroughly, merge it to master and inform your partners about master changes.

Authors

• Emir Ünlütürk
• Buğra Önal
• Onur Yıkılmazoğlu
• Doruk Çelebi
• Onat Güngör

^{Contents of the project are subject to change, do keep in mind that project is under active development}

passman's Issues

Password settings

Will there be settings for password generation such as the password length?

Storage System

Please check over the storage implementation. I'll try to write a test.

Reminder implementation

The reminder system may have two implementations for the update:

1. check every set period (ex. 2 hours)
2. check every time the program is started
   Please give me your opinions as to how we should do it.

Reminder update pop-ups

From what I have understood currently we are pushing pop-ups when a password needs to be updated. However there may be cases in which multiple updates are necessary. Pushing multiple pop-ups one after the other might not be a great idea.
As an alternative we could create a list that holds the passwords that need to be updated and maybe push a signle pop-up that says "There are passwords that need to be updated"

password frequency

currently the password is asked once before starting the gui
should we change this to every time the database is accessed? for better security?
or should I just keep it like this?
it would be pretty easy to implement this

New methods new tests

I just implemented a few new methods to the reminder class, I need someone to test them. The intended use of the methods have been described above the methods.

ReminderTest

The reminderTest class has been edited by someone and it has tests for encryption. I beleive this was a mistake but if the author wants to carry the test over to a new test class I can do that.

Profile System

We are going to need a profile system implemented. Every profile should have its own master password and database. The reminders and passwords should all be completely separated. This shall be used by the GUI in the login panel where a user can pick the profile to sign on and reveal the main panel for that profile.

password creation panel

Instead of a creation panel wouldnt it be better to have a few pop dialogs with textboxes?

Test Cases

We should properly implement test cases for as many instructions as possible to have a good amount of coverage.