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.

Sign up for GitHub

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

Jump to bottom

Areas in authentication: user-to-machine, machine-to-user, user-to-user, machine-to-machine #6

Open
2 of 4 tasks
dbosk opened this issue Mar 1, 2017 · 4 comments
Open
2 of 4 tasks

Areas in authentication: user-to-machine, machine-to-user, user-to-user, machine-to-machine #6

dbosk opened this issue Mar 1, 2017 · 4 comments
Assignees
@dbosk
Labels
lecture Affects lecture content
Milestone
v2020

Comments

@dbosk
Copy link
Member

dbosk commented Mar 1, 2017 •
edited
Loading

The area of authentication that we are interested in can be divided into these categories:
@dbosk
Copy link
Member Author

dbosk commented Apr 20, 2017 •
edited
Loading

User--machine and machine--user authentication are discussed in overview. The machine-to-machine authentication is basically the main topic of fverifprotocols, that should move here.

@dbosk dbosk changed the title Three areas in authentication: user-to-machine, machine-to-user, machine-to-machine Three areas in authentication: user-to-machine, machine-to-user, user-to-user, machine-to-machine Apr 22, 2017
@dbosk dbosk changed the title Three areas in authentication: user-to-machine, machine-to-user, user-to-user, machine-to-machine [overview] Three areas in authentication: user-to-machine, machine-to-user, user-to-user, machine-to-machine Apr 22, 2017
dbosk added a commit that referenced this issue Apr 23, 2017
@dbosk
Clarifies user--machine and machine--user authentication
504cd12 
This is WIP #6. We should move the machine--machine authentication from
fverif to here.
@dbosk dbosk modified the milestone: v1.0 May 24, 2017
@dbosk
Copy link
Member Author

dbosk commented Mar 5, 2019

Machine-to-machine might also be covered by keyauth.

@dbosk dbosk added the lecture Affects lecture content label Mar 5, 2019
@dbosk
Copy link
Member Author

dbosk commented Mar 5, 2019

These are usually chained when using crypto and involving hardware.

@dbosk dbosk self-assigned this Mar 5, 2019
@dbosk dbosk changed the title [overview] Three areas in authentication: user-to-machine, machine-to-user, user-to-user, machine-to-machine Areas in authentication: user-to-machine, machine-to-user, user-to-user, machine-to-machine Apr 14, 2019
@dbosk dbosk modified the milestones: v2019, v2020 Apr 14, 2019
@dbosk
Copy link
Member Author

dbosk commented Jan 24, 2020

User-to-user (through-machine) will probably require distance bounding in some cases.

@dbosk dbosk mentioned this issue Jan 24, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dbosk dbosk

Labels
lecture Affects lecture content
Projects
None yet
Milestone
v2020
Development

No branches or pull requests
1 participant
@dbosk