├── .github
├── ISSUE_TEMPLATE
│ ├── bug_report.md
│ └── feature_request.md
└── pull_request_template.md
├── .gitignore
├── CODE_OF_CONDUCT
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── app
└── app-debug.apk
└── program
├── include
├── add_user.h
├── apdu_functions.h
├── authenticate.h
└── nfc_functions.h
├── makefile
├── obj
└── placeholder.txt
└── src
├── add_user.c
├── apdu_functions.c
├── authenticate.c
└── nfc_functions.c
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | **Screenshots**
24 | If applicable, add screenshots to help explain your problem.
25 |
26 | **Desktop (please complete the following information):**
27 | - OS: [e.g. iOS]
28 | - Browser [e.g. chrome, safari]
29 | - Version [e.g. 22]
30 |
31 | **Smartphone (please complete the following information):**
32 | - Device: [e.g. iPhone6]
33 | - OS: [e.g. iOS8.1]
34 | - Browser [e.g. stock browser, safari]
35 | - Version [e.g. 22]
36 |
37 | **Additional context**
38 | Add any other context about the problem here.
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 | # Overview
2 | *Please provide an overview of the new feature or bug fix*
3 |
4 | # Describe
5 | *Please provide a detailed description of the changes you have made and how you have implemented them*
6 |
7 | # Contributors
8 | *Please tag any people who have contributed with you on this change*
9 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Prerequisites
2 | *.d
3 |
4 | # Object files
5 | *.o
6 | *.ko
7 | *.obj
8 | *.elf
9 |
10 | # Linker output
11 | *.ilk
12 | *.map
13 | *.exp
14 |
15 | # Precompiled Headers
16 | *.gch
17 | *.pch
18 |
19 | # Libraries
20 | *.lib
21 | *.a
22 | *.la
23 | *.lo
24 |
25 | # Shared objects (inc. Windows DLLs)
26 | *.dll
27 | *.so
28 | *.so.*
29 | *.dylib
30 |
31 | # Executables
32 | *.exe
33 | *.out
34 | *.app
35 | *.i*86
36 | *.x86_64
37 | *.hex
38 |
39 | # Debug files
40 | *.dSYM/
41 | *.su
42 | *.idb
43 | *.pdb
44 |
45 | # Kernel Module Compile Results
46 | *.mod*
47 | *.cmd
48 | .tmp_versions/
49 | modules.order
50 | Module.symvers
51 | Mkfile.old
52 | dkms.conf
53 |
54 | # Programs
55 | /program/add_user
56 | /program/authenticate
57 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT:
--------------------------------------------------------------------------------
1 | Contributor Covenant Code of Conduct
2 | Our Pledge
3 | We as members, contributors, and leaders pledge to make participation in our
4 | community a harassment-free experience for everyone, regardless of age, body
5 | size, visible or invisible disability, ethnicity, sex characteristics, gender
6 | identity and expression, level of experience, education, socio-economic status,
7 | nationality, personal appearance, race, caste, color, religion, or sexual identity
8 | and orientation.
9 | We pledge to act and interact in ways that contribute to an open, welcoming,
10 | diverse, inclusive, and healthy community.
11 | Our Standards
12 | Examples of behavior that contributes to a positive environment for our
13 | community include:
14 |
15 | * Demonstrating empathy and kindness toward other people
16 | * Being respectful of differing opinions, viewpoints, and experiences
17 | * Giving and gracefully accepting constructive feedback
18 | * Accepting responsibility and apologizing to those affected by our mistakes,
19 | and learning from the experience
20 | * Focusing on what is best not just for us as individuals, but for the
21 | overall community
22 |
23 | Examples of unacceptable behavior include:
24 |
25 | * The use of sexualized language or imagery, and sexual attention or
26 | advances of any kind
27 | * Trolling, insulting or derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others’ private information, such as a physical or email
30 | address, without their explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | Enforcement Responsibilities
35 | Community leaders are responsible for clarifying and enforcing our standards of
36 | acceptable behavior and will take appropriate and fair corrective action in
37 | response to any behavior that they deem inappropriate, threatening, offensive,
38 | or harmful.
39 | Community leaders have the right and responsibility to remove, edit, or reject
40 | comments, commits, code, wiki edits, issues, and other contributions that are
41 | not aligned to this Code of Conduct, and will communicate reasons for moderation
42 | decisions when appropriate.
43 | Scope
44 | This Code of Conduct applies within all community spaces, and also applies when
45 | an individual is officially representing the community in public spaces.
46 | Examples of representing our community include using an official e-mail address,
47 | posting via an official social media account, or acting as an appointed
48 | representative at an online or offline event.
49 | Enforcement
50 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
51 | reported to the community leaders responsible for enforcement at
52 | [INSERT CONTACT METHOD].
53 | All complaints will be reviewed and investigated promptly and fairly.
54 | All community leaders are obligated to respect the privacy and security of the
55 | reporter of any incident.
56 | Enforcement Guidelines
57 | Community leaders will follow these Community Impact Guidelines in determining
58 | the consequences for any action they deem in violation of this Code of Conduct:
59 | 1. Correction
60 | Community Impact: Use of inappropriate language or other behavior deemed
61 | unprofessional or unwelcome in the community.
62 | Consequence: A private, written warning from community leaders, providing
63 | clarity around the nature of the violation and an explanation of why the
64 | behavior was inappropriate. A public apology may be requested.
65 | 2. Warning
66 | Community Impact: A violation through a single incident or series
67 | of actions.
68 | Consequence: A warning with consequences for continued behavior. No
69 | interaction with the people involved, including unsolicited interaction with
70 | those enforcing the Code of Conduct, for a specified period of time. This
71 | includes avoiding interactions in community spaces as well as external channels
72 | like social media. Violating these terms may lead to a temporary or
73 | permanent ban.
74 | 3. Temporary Ban
75 | Community Impact: A serious violation of community standards, including
76 | sustained inappropriate behavior.
77 | Consequence: A temporary ban from any sort of interaction or public
78 | communication with the community for a specified period of time. No public or
79 | private interaction with the people involved, including unsolicited interaction
80 | with those enforcing the Code of Conduct, is allowed during this period.
81 | Violating these terms may lead to a permanent ban.
82 | 4. Permanent Ban
83 | Community Impact: Demonstrating a pattern of violation of community
84 | standards, including sustained inappropriate behavior, harassment of an
85 | individual, or aggression toward or disparagement of classes of individuals.
86 | Consequence: A permanent ban from any sort of public interaction within
87 | the community.
88 | Attribution
89 | This Code of Conduct is adapted from the Contributor Covenant,
90 | version 2.0, available at
91 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
92 | Community Impact Guidelines were inspired by
93 | Mozilla’s code of conduct enforcement ladder.
94 | For answers to common questions about this code of conduct, see the FAQ at
95 | https://www.contributor-covenant.org/faq. Translations are available
96 | at https://www.contributor-covenant.org/translations.
97 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Introduction
2 | Hello, and welcome to this project! I am very pleased to have you check it out and would love any contributions you may have. The key premise of this project is a way of unlocking your computer using NFC, ideally in a smartphone. I initially created this for my final university project, but have now opened it up to the community in order to make it the best it possibly can be. This contributing file is quite short for now, but as this project expands I will be updating it more reguarly, so do please keep checking for updates.
3 |
4 | Following these guidelines helps with all aspects of this project, and shows that you respect the efforts of the community. In return, you will receive fast responses to any queries, and as much support as possible for your development work.
5 |
6 | As a student myself, I am more than happy for anyone to work on and contribute to this project, no matter your level of experience! All you need is a positive attitude and a willingness to learn!
7 |
8 | # Contents
9 | 1. [Ground Rules](#ground-rule)
10 | 2. [Your first contribution](#your-first-contribution)
11 | 3. [Currently required features and enhancements](#currently-required-features-and-enhancements)
12 | 4. [Getting started](#getting-started)
13 | 5. [How to report a bug](#how-to-report-a-bug)
14 | 6. [How to suggest a feature or enhancement](#how-to-suggest-a-feature-or-enhancement)
15 | 7. [Code review process](#code-review-process)
16 | 8. [Conventions](#conventions)
17 | 9. [Where can I ask for help](#where-can-I-ask-for-help)
18 |
19 | # Ground rules
20 | - Always be considerate to other developers on this project - remember, not everyone will be the same skill level
21 | - Do not add any features not already specified to the project unless discussed and approved by the owner
22 | - Be welcoming to newcomers, and give as much help and support as you are able to
23 | - Only work on one feature at a time, keeping the pull requests small for easy reviewing
24 | - Ensure that all code follows the conventions specified
25 | - Discuss everything transparently and get community feedback
26 | - Have fun!
27 |
28 | # Your first contribution
29 | Unsure about where to begin? Look at the [Currently required features](#currently-required-features) to see what is needed by the project, and check to see if a branch/pull request already exists for it. There is no contribution too small, so work on any issue/feature that best suits your skill level!
30 |
31 | # Currently required features and enhancements
32 | ## Priority
33 | - Get project to actually unlock the computer and not just run from the command line
34 | - Use a secure channel for the NFC communication
35 | - UI for adding and managing users
36 | - Create a wiki to fully document this project
37 | - Refactor the code into the shortest/most optimal format
38 |
39 | ## Extension
40 | *Please get in touch with the owner of this project before attempting anything from this section*
41 | - Windows/MacOS version
42 |
43 | # Getting started
44 | For information on cloning, compiling and running this project, please see the README, and let me know if there are any issues. Once that has been setup, to begin work:
45 | 1. Create a new fork for your contribution (see [Conventions](#conventions))
46 | 2. Do all your changes on that fork
47 | 3. Create a pull request to main once your feature is finished, although keep each pull request to one feature
48 |
49 | # How to report a bug
50 | Please submit any bugs found using the bug issue template, under the issues tab.
51 |
52 | # How to suggest a feature or enhancement
53 | Please submit any new feature ideas using the feature issue template, under the issues tab.
54 |
55 | # Code review process
56 | At this moment in time, any pull requests will be reviewed by me, as and when I can get to them (within a week). Please provide as much description and information as possible in your pull request so I can understand what your change does and how it works. In future, I plan on adding extra reviewers to this process, but that depends on the size of the community and contributors.
57 |
58 | # Conventions
59 | ## Git conventions
60 | - Name your branches/forks as a maximum of three words describing the change, separated by hypens. eg. fix-encryption-bug
61 | - Give your pull requests meaningful names that accuratley describe what they do
62 | - Provide detailed description for your pull request so that the reviewer can easily tell what it does
63 |
64 | ## Coding conventions
65 | - Comment your code so it is clear as to what it does
66 | - Use camel casing for variable names and function names
67 | - Keep related functions in one C file, and create new files for unrelated functions
68 | - Put references to everything in the header files
69 |
70 | # Where can I ask for help
71 | Anywhere! Get in touch with the community via the discussions, or feel free to get in touch with me directly, and I will respond as fast as I can!
72 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 |
635 | Copyright (C)
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | Copyright (C)
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # linux_pam_nfc
2 | ## CONTENTS
3 | 1. [Description](#DESCRIPTION)
4 | 2. [Contribution](#CONTRIBUTION)
5 | 3. [Acknowledgement](#ACKNOWLEDGEMENT)
6 | 4. [Prerequisites](#PREREQUISITES)
7 | 5. [Setup](#SETUP)
8 | 6. [Compilation](#COMPILATION)
9 | 7. [Usage](#USAGE)
10 | 8. [Security](#SECURITY)
11 | 9. [Troubleshooting](#TROUBLESHOOTING)
12 |
13 |
14 | ## DESCRIPTION
15 | This program uses Linux Pluggable Authentication Modules (PAM) to authenticate users via the use of Near-Field Communication (NFC). It can be used with traditional NFC smart cards, as long as they are configured correctly, although the intended use of this program is with the OS_auth_application Android App.
16 |
17 | ## CONTRIBUTION
18 | Please see the CONTRIBUTING.md file for information on contributing to the project
19 |
20 | ## ACKNOWLEDGEMENT
21 | Whilst this project is novel work, it takes inspiration from [pam_nfc](https://github.com/nfc-tools/pam_nfc). Thank you to the developers of that project for releasing it under a GNU General Public license so that it could be used to benefit this work.
22 |
23 | ## PREREQUISITES
24 | In order to use this program, you must have:
25 | * A Linux system (preferably Debian based)
26 | * libnfc installed on your system (see setup for details)
27 | * A physical NFC card reader and tags
28 | * Create an empty file called pam_nfc.conf in /etc/
29 | * An Android phone with NFC, and the app installed (in the app folder)
30 |
31 | ## SETUP
32 | ### NFC SETUP
33 | In order to use NFC in Linux with C support, you must use the free libnfc library. This can be installed using
34 | `sudo apt-get install libnfc-bin libnfc-examples libnfc-pn53x-examples`
35 |
36 | in Debian based systems.
37 |
38 | If using an ACR122 reader, as in the project, a few extra steps must be taken in order for it to work properly. Firstly, pcscd must be installed using
39 | `sudo apt-get install pcscd`
40 |
41 | and pcsc which can be installed from [Here](https://pcsclite.apdu.fr/files/) and by following the instructions in the README.
42 |
43 | Following this, the `libccid_Info.plist` file located within `etc` must be modified. Locate `ifdDriverOptions` and turn `0x0000` value into `0x0001`.
44 |
45 | Finally, run
46 |
47 | `sudo vim /etc/modprobe.d/blacklist-libnfc.conf`
48 |
49 | and add the line `blacklist pn533_usb`, before rebooting your machine. libnfc should now be configured correctly, which can be verified by running
50 |
51 | `nfc-list`
52 |
53 |
54 | To use libnfc within C, run on the command line
55 |
56 | `sudo apt-get install libnfc-dev`
57 |
58 | and then at the top of the C file `#include `
59 |
60 | ### LINUX-PAM SETUP
61 | PAM applications must contain certain header files in order to work. These files can be found in
62 | `usr/include/security`
63 |
64 | If they do not yet exist, install them from the command line by using
65 |
66 | `sudo apt-get install libpam0g-dev`
67 |
68 | ### APP SETUP
69 | Download the APK file in the app folder on this repo to your Android smartphone, and install (may need to allow install from unknown sources). Once downloaded, create an account on the app, and use this is sign in. To use the app, simply tap on the reader.
70 |
71 | ## COMPILATION
72 | For ease of compilation, a makefile has been included with this solution. To compile both programs, simply run:
73 |
74 | `cd program`
75 |
76 | `make`
77 |
78 | ## USAGE
79 | Once the program has been compiled, two executable files will be generated in the `program` folder.
80 | ### add_user
81 | The add_user program is used to add new users to the pam_nfc.conf file. To use this program, simply run:
82 |
83 | `sudo ./add_user $USERNAME$`
84 |
85 | where `$USERNAME` is replaced with the username of the user you are adding. The program will establish a connection to the NFC reader where it will wait for the device to be touched to the reader. Once the device has been touched to the reader, it will perform the APDU transaction, and assuming everything is setup correctly, add the new user and their authentication ID to the config file.
86 |
87 | ### authenticate
88 | The authenticate program carrys out the actual user authentication with Linux-PAM, using the entries in the config file. To use this program, simply run:
89 |
90 | `sudo ./authenticate`
91 |
92 | This program takes in no parameters via the command line, but Linux-PAM will prompt you to enter your username once the program is running. Once again, a connection to the NFC reader will be established, and once a device is touched, the APDU transaction is performed. The authentication ID received will then be compared to the configuration file, and Linux-PAM handles the authentication as a result.
93 |
94 | ### APPLICATION ID
95 | The app and program are already configured to use the same AID to work. However, if you do need to know this, the AID used for this project is *A0000002471001*.
96 |
97 | ## SECURITY
98 | In order to make authentication more secure, this project uses application protocol data unit (APDU) for authentication, as opposed to the UID of the device. UIDs are not secure as can be easily read and spoofed. APDU is more secure, although still not perfect, but hopefully this project will be extended in future to use a secure channel for all NFC transactions, making it much more secure. For more information on APDU and how this works, there is plenty of papers and knowledge articles on the Internet.
99 |
100 | ## TROUBLESHOOTING
101 | If you have any problems with setting up, running, or using this program, please use the discussion tab on GitHub.
102 |
103 |
--------------------------------------------------------------------------------
/app/app-debug.apk:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/thomasread99/linux_pam_nfc/212affe3619f160b1c2ca0c48fe75b2aa27a32fd/app/app-debug.apk
--------------------------------------------------------------------------------
/program/include/add_user.h:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | #ifndef ADD_USER
18 | #define ADD_USER
19 |
20 | /*Add the user and tag to the configuration file*/
21 | int addAuth (char *user, char *target);
22 |
23 | #endif
--------------------------------------------------------------------------------
/program/include/apdu_functions.h:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | #ifndef APDU_FUNCTIONS
18 | #define APDU_FUNCTIONS
19 |
20 | #include
21 |
22 | /*Get the user ID from the mobile device*/
23 | char* getID();
24 |
25 | /*Transmit to the card and get the response back*/
26 | char* apduTransmit(nfc_device *pnd, uint8_t * capdu, size_t capdulen, uint8_t * rapdu, size_t * rapdulen);
27 |
28 | #endif
--------------------------------------------------------------------------------
/program/include/authenticate.h:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | #ifndef AUTHENTICATE
18 | #define AUTHENTICATE
19 |
20 | /*Define the PAM configration to use*/
21 | #define CONFIG "login"
22 |
23 | /*Function to authenticate through PAM*/
24 | int pamAuthenticate (int argc, const char **argv);
25 |
26 | #endif
--------------------------------------------------------------------------------
/program/include/nfc_functions.h:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | #ifndef NFC_FUNCTIONS
18 | #define NFC_FUNCTIONS
19 |
20 | /*Path to the config file*/
21 | #define CONFIGFILE "/etc/pam_nfc.conf"
22 |
23 | /*Function to check if the user is authorised with their tag*/
24 | int authorise (const char *user);
25 |
26 | /*Function to get the number of NFC targets*/
27 | int getTargets (char **targets[]);
28 |
29 | /*Function to check if the user and tag are found in the config*/
30 | int checkAuth (const char *user, char *target);
31 |
32 | /*Check that the config file exists and can be read*/
33 | int checkFile (void);
34 |
35 | #endif
--------------------------------------------------------------------------------
/program/makefile:
--------------------------------------------------------------------------------
1 | # Compiler and flags
2 | CC = gcc
3 | CFLAGS = -lnfc -lcrypt -lpam -lpam_misc
4 |
5 | # Directory paths
6 | IDIR = include
7 | ODIR = obj
8 | SDIR = src
9 |
10 | # Compile both programs
11 | all: add_user authenticate
12 |
13 | # Compilation of add_user
14 | _DEPS = add_user.h nfc_functions.h apdu_functions.h
15 | DEPS = $(patsubst %,$(IDIR)/%,$(_DEPS))
16 |
17 | _OBJ = add_user.o nfc_functions.o apdu_functions.o
18 | OBJ = $(patsubst %,$(ODIR)/%,$(_OBJ))
19 |
20 | $(ODIR)/%.o: $(SDIR)/%.c $(DEPS)
21 | $(CC) -c -o $@ $< $(CFLAGS)
22 |
23 | add_user: $(OBJ)
24 | $(CC) -o $@ $^ $(CFLAGS)
25 |
26 | # Compilation of authenticate
27 | _MDEPS = authenticate.h nfc_functions.h apdu_functions.h
28 | MDEPS = $(patsubst %,$(IDIR)/%,$(_MDEPS))
29 |
30 | _MOBJ = authenticate.o nfc_functions.o apdu_functions.o
31 | MOBJ = $(patsubst %,$(ODIR)/%,$(_MOBJ))
32 |
33 | $(ODIR)/%.o: $(SDIR)/%.c $(MDEPS)
34 | $(CC) -c -o $@ $< $(CFLAGS)
35 |
36 | authenticate: $(MOBJ)
37 | $(CC) -o $@ $^ $(CFLAGS)
38 |
39 | # Clean the program by removing the object files
40 | .PHONY: clean
41 |
42 | clean:
43 | rm -f $(ODIR)/*.o *~ core $(INCDIR)/*~
--------------------------------------------------------------------------------
/program/obj/placeholder.txt:
--------------------------------------------------------------------------------
1 | This placeholder is simply for git to recognise the folder. This file can be deleted once the repository has been cloned.
2 |
--------------------------------------------------------------------------------
/program/src/add_user.c:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | /*Headers to include*/
18 | #include
19 | #include
20 | #include
21 | #include
22 | #include
23 |
24 | #include
25 |
26 | #include "../include/add_user.h"
27 | #include "../include/nfc_functions.h"
28 | #include "../include/apdu_functions.h"
29 |
30 | int main (int argc, char *argv[])
31 | {
32 | /*Check that the user has supplied their username as a parameter*/
33 | if (argc != 2)
34 | {
35 | fprintf(stderr, "Add your username as a parameter\n");
36 | exit(EXIT_FAILURE);
37 | }
38 |
39 | /*Variable declarations*/
40 | char *id, *name;
41 |
42 | name = argv[1];
43 | /*Set id to the id received from the device*/
44 | id = getID();
45 |
46 | /*Check that an ID has been received*/
47 | if (id == NULL) {
48 | errx (EXIT_FAILURE, "Error communicating with device\n");
49 | }
50 |
51 | /*Run the function to add the user id to the configuration file and error check*/
52 | if (!(addAuth (name, id))) {
53 | err (EXIT_FAILURE, "Error adding authorization for the user\n");
54 | }
55 |
56 | /*Exit and report success*/
57 | printf("User added\n");
58 | exit(EXIT_SUCCESS);
59 | }
60 |
61 | int addAuth (char *user, char *id)
62 | {
63 | /*Variable declarations*/
64 | int ret;
65 | FILE *config;
66 |
67 | /*If the config file exists, check that it is read-only*/
68 | if ((config = fopen (CONFIGFILE, "r"))) {
69 | fclose (config);
70 | /*Chmod the file so it can be written to*/
71 | chmod (CONFIGFILE, 0600);
72 | }
73 |
74 | /*If no file exists, avoid race condition*/
75 | umask (0077);
76 |
77 | /*If you can't append to the file, return*/
78 | if (!(config = fopen (CONFIGFILE, "a"))) {
79 | return 0;
80 | }
81 |
82 | /*Write to the config file*/
83 | ret = (fprintf (config, "%s %s\n", user, crypt(id, "RC")) > 0);
84 |
85 | /*If you can't close the config file, return*/
86 | if (fclose (config) != 0) {
87 | return 0;
88 | }
89 |
90 | /*Set the file back to read-only*/
91 | chmod (CONFIGFILE, 0400);
92 |
93 | /*Return*/
94 | return ret;
95 | }
--------------------------------------------------------------------------------
/program/src/apdu_functions.c:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | #include
18 | #include
19 | #include
20 |
21 | #include "../include/apdu_functions.h"
22 |
23 | /*Get the user ID from the mobile device*/
24 | char* getID()
25 | {
26 | /*Variable declarations*/
27 | char *id;
28 | nfc_device *initiator;
29 | nfc_target nt;
30 | nfc_context *context;
31 | uint8_t capdu[264];
32 | size_t capdulen;
33 | uint8_t rapdu[264];
34 | size_t rapdulen;
35 |
36 | /*Start the NFC context*/
37 | nfc_init(&context);
38 | if (context == NULL) {
39 | printf("Unable to init libnfc (malloc)\n");
40 | return NULL;
41 | }
42 |
43 | /*Open a connection to the device*/
44 | initiator = nfc_open(context, NULL);
45 |
46 | /*Check the connection has been properly initiated*/
47 | if (initiator == NULL) {
48 | printf("ERROR: %s", "Unable to open NFC device.");
49 | return NULL;
50 | }
51 | if (nfc_initiator_init(initiator) < 0) {
52 | nfc_perror(initiator, "nfc_initiator_init");
53 | return NULL;
54 | }
55 |
56 | /*Define the NFC modulation values*/
57 | const nfc_modulation nmMifare = {
58 | .nmt = NMT_ISO14443A,
59 | .nbr = NBR_106,
60 | };
61 |
62 | /*Wait for the mobile device to be placed on the reader*/
63 | printf("Waiting for device...\n");
64 | while (nfc_initiator_select_passive_target(initiator, nmMifare, NULL, 0, &nt) <= 0);
65 | printf("Device detected\n");
66 |
67 | /*AID of the application*/
68 | memcpy(capdu, "\x00\xA4\x04\x00\x07\xA0\x00\x00\x02\x47\x10\x01\x00", 13);
69 | capdulen = 13;
70 | rapdulen = sizeof(rapdu);
71 | /*Call the apdu transmit function*/
72 | id = apduTransmit(initiator, capdu, capdulen, rapdu, &rapdulen);
73 | if (id == NULL)
74 | return NULL;
75 |
76 | /*Close the device and the context*/
77 | nfc_close(initiator);
78 | nfc_exit(context);
79 |
80 | return id;
81 | }
82 |
83 | /*Transmit to the card and get the response back*/
84 | char* apduTransmit(nfc_device *pnd, uint8_t * capdu, size_t capdulen, uint8_t * rapdu, size_t * rapdulen)
85 | {
86 | /*Variable declarations*/
87 | int res, length = 0;;
88 | size_t szPos;
89 | char *id;
90 |
91 | /*Return null if device doesn't send any data*/
92 | if ((res = nfc_initiator_transceive_bytes(pnd, capdu, capdulen, rapdu, *rapdulen, 500)) < 0) {
93 | return NULL;
94 | }
95 | else {
96 | *rapdulen = (size_t) res;
97 | /*Append each byte received to a string*/
98 | for (szPos = 0; szPos < *rapdulen; szPos++) {
99 | length += sprintf(id + length, "%02x", rapdu[szPos]);
100 | }
101 |
102 | return id;
103 | }
104 | }
--------------------------------------------------------------------------------
/program/src/authenticate.c:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | /*Headers to include*/
18 | #include
19 | #include
20 | #include
21 | #include
22 | #include
23 |
24 | #include
25 | #include
26 | #include
27 | #include
28 |
29 | #include "../include/authenticate.h"
30 | #include "../include/nfc_functions.h"
31 |
32 | static struct pam_conv conv = {
33 | misc_conv,
34 | NULL
35 | };
36 |
37 | int main (int argc, char *argv[])
38 | {
39 | /*Run the function to authenticate the user through PAM*/
40 | int granted = pamAuthenticate (argc, argv);
41 |
42 | if (granted == 0) {
43 | printf("Authorised\n");
44 | exit(EXIT_SUCCESS);
45 | }
46 |
47 | printf("Unauthorised\n");
48 | exit(EXIT_FAILURE);
49 | }
50 |
51 | /*Function to authenticate through PAM*/
52 | PAM_EXTERN
53 | int pamAuthenticate (int argc, const char **argv)
54 | {
55 | /*Variable declarations*/
56 | pam_handle_t *pamh = NULL;
57 | int retval = PAM_AUTH_ERR;
58 | char confline[256];
59 | const char *user = NULL;
60 |
61 | /*Begin the PAM transaction*/
62 | pam_start(CONFIG, NULL, &conv, &pamh);
63 |
64 | /*Get the user name through the command line*/
65 | retval = pam_get_user (pamh, &user, NULL);
66 |
67 | /*Check that the user name has been retrieved*/
68 | if (retval != PAM_SUCCESS)
69 | {
70 | printf ("User not found\n");
71 | return retval;
72 | }
73 | if (user == NULL || *user == '\0')
74 | {
75 | printf("Username not known\n");
76 | return retval;
77 | }
78 |
79 | /*Check that the config file exists and can be opened*/
80 | if (!(checkFile())) {
81 | return PAM_SERVICE_ERR;
82 | }
83 |
84 | /*Check if the user can be authenticated*/
85 | return (authorise (user)) ? PAM_SUCCESS : PAM_AUTH_ERR;
86 | }
--------------------------------------------------------------------------------
/program/src/nfc_functions.c:
--------------------------------------------------------------------------------
1 | /*
2 | * Copyright (C) 2021 Thomas Read
3 | *
4 | * This program is free software; you
5 | * can redistribute it and/or modify
6 | * it as you wish. Please credit the project
7 | * owner in any papers or derived work where
8 | * this has been used.
9 | *
10 | * This project is now open source, and relies
11 | * on contributions from the community for
12 | * further development. Please see the README
13 | * for currently required features
14 | *
15 | */
16 |
17 | /*Headers to include*/
18 | #include
19 | #include
20 | #include
21 | #include
22 | #include
23 |
24 | #include
25 | #include
26 |
27 | #include "../include/add_user.h"
28 | #include "../include/nfc_functions.h"
29 | #include "../include/apdu_functions.h"
30 |
31 | /*Function to check if the user is authorised with their tag*/
32 | int authorise (const char *user)
33 | {
34 | /*Initially set to unauthorised*/
35 | int authorised = 0;
36 |
37 | /*Variable declarations*/
38 | char *id;
39 |
40 | /*Set the id to the id received from the device*/
41 | id = getID();
42 |
43 | /*Check that an ID has been received*/
44 | if (id == NULL) {
45 | errx (EXIT_FAILURE, "Error communicating with device\n");
46 | }
47 |
48 | /*Check if the user is authorized with the id received*/
49 | if (checkAuth(user, id)) {
50 | authorised = 1;
51 | }
52 |
53 | return authorised;
54 | }
55 |
56 | /*Function to check if the user and tag are found in the config*/
57 | int checkAuth (const char *user, char *id)
58 | {
59 | /*Initially set to not found*/
60 | int found = 0;
61 |
62 | /*Variable declarations*/
63 | FILE *config;
64 | char needle[BUFSIZ];
65 |
66 | /*Write to the buffer*/
67 | snprintf (needle, BUFSIZ, "%s %s\n", user, crypt(id, "RC"));
68 |
69 | /*Open the config file for reading*/
70 | if ((config = fopen(CONFIGFILE, "r"))) {
71 | char buffer[BUFSIZ];
72 | /*Look at each line in the file*/
73 | while (!found && fgets (buffer, BUFSIZ, config)) {
74 | /*If the value matches the value placed in the buffer, then user found*/
75 | if (strcmp (buffer, needle) == 0) {
76 | found = 1;
77 | }
78 | }
79 | /*Close the file*/
80 | fclose (config);
81 | }
82 |
83 | /*Return the result*/
84 | return found;
85 | }
86 |
87 | /*Check that the config file exists and can be read*/
88 | int checkFile (void)
89 | {
90 | /*Variable declarations*/
91 | struct stat fileInfo;
92 |
93 | /*Check file exists*/
94 | if (stat (CONFIGFILE, &fileInfo)) {
95 | return 0;
96 | }
97 |
98 | /*Check file can be opened*/
99 | if ((fileInfo.st_mode & S_IWOTH)
100 | || !S_ISREG (fileInfo.st_mode))
101 | {
102 | return 0;
103 | }
104 |
105 | return 1;
106 | }
--------------------------------------------------------------------------------