diff options
| author | kotontrion <[email protected]> | 2024-08-16 19:00:30 +0200 |
|---|---|---|
| committer | GitHub <[email protected]> | 2024-08-16 19:00:30 +0200 |
| commit | 43e6bd47863c45b9232f0f74e973b83b8354bd3a (patch) | |
| tree | 6eef5762d99955b029af69b63841f0fc381ab17f | |
| parent | 0722cfa509b73c23dbff658b3555cea820997477 (diff) | |
removed old license from readme
| -rw-r--r-- | README.md | 4 |
1 files changed, 0 insertions, 4 deletions
@@ -63,8 +63,4 @@ Generally it can be used like this: Not connecting those signals, is equivalent to calling `pam.supply_secret(NULL)` immediately after the signal is emitted. 4. start authentication process using `Pam.start_authentication()`. This function will return whether the authentication was started or not. 5. it is possible to reuse the same Pam object for multiple sequential authentication attempts. Just call `pam.start_authentication()` again after the `success` or `fail` signal was emitted. - -## License - -This project is licensed under the GPL-3 License - see the LICENSE file for details. |