summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-10-06update LICENSEHiltjo Posthuma
2022-10-08bump version to 1.5Hiltjo Posthuma
2022-10-08Makefile: explicit_bzero.c was copied twice (GNU make gives a warning)Hiltjo Posthuma
2022-03-25Delete config.hRafael Marçalo
2021-08-21Delete logo.pngRafael Marçalo
2019-10-06Added Custom Config and Logorafa_99
2017-03-25Properly clear the last entered characterTobias Stoeckmann
When enter is pressed, passwd[len] will be set to '\0'. Pressing backspace is supposed to remove the last entered character. But currently, the clearing has an off-by-one, as in setting passwd[len] to '\0' just like enter would do. You can also verify it by imagining len=1 and that it's impossible to clear passwd[0] by pressing backspace with the current code. Signed-off-by: Tobias Stoeckmann <tobias@stoeckmann.org>
2016-11-23rm trailing whitespace in READMEMarkus Teich
2016-11-23syntax fixMarkus Teich
2016-11-23there can only be one window in the eventMarkus Teich
2016-11-23Fix resize with multiple monitors and portrait modeBob Uhl
When connecting/disconnecting a portrait monitor, the XRRScreenChangeNotifyEvent height & width are reversed due to the XRandR rotation; detect this and DTRT.
2016-11-20bump versionMarkus Teich
2016-11-20add arg.h and util.h to MakefileMarkus Teich
2016-11-20clarify colors in config.def.hMarkus Teich
2016-11-20move config.h inclusion after type declarationsMarkus Teich
2016-10-18Unboolify slock.cLaslo Hunhold
2016-10-10Use explicit strcmp() instead of inlining itFRIGN
Makes it a tad more readable; the previous "optimization" will be done by the compiler anyway.
2016-10-10No need for oldc to be staticFRIGN
2016-10-10Use NUL character constant explicitlyFRIGN
2016-10-10Keep the line-lengths at bayFRIGN
This makes the code more readable and prevents wraparounds in the editor.
2016-09-28Add a section on security considerationsFRIGN
The section on security considerations sheds some light on the problems that we can't solve within slock but which the user has to solve in his X configuration.
2016-09-26remove confusing DPMS commentMarkus Teich
FRIGN on hackers@suckless.org: What has been bugging me for quite a while is this DPMS comment that was added there for no reason. Every sane mind would agree that fiddling with DPMS makes no sense whatsoever. When I slock, my screen turns off after 10 minutes. So, if I don't like that, I disable DPMS. If I do, I just fiddle around with my mouse a bit and get the slock promt.
2016-09-23error out early on crypt() failMarkus Teich
2016-09-23Stop using $USER for shadow entriesFRIGN
This was extremely bad practice, effectively making the program behave different depending on which architecture you are running it on. OpenBSD offers getpwuid_shadow, but there is no getspuid for getspnam, so we resort to using the pw_name entry in the struct passwd we filled earlier. This prevents slock from crashing when $USER is empty (easy to do). If you want to run slock as a different user, don't use $ USER="tom" slock but doas or sudo which were designed for this purpose.
2016-09-23Rename getpw() and pws to gethash() and hashFRIGN
2016-09-23Remove cleanup and deglobalize and rework data structuresFRIGN
The cleanup removal is a joint-venture with Markus. We assume the X server does the cleanup, so we don't need it. The idea is that the fds are closed at exit and thus already indicate to the X server that the client has quit. Analogously the same applies to freeing memory sections previously allocated for the X server. We love XXXXXL burgers and therefore removed XUngrabPointer XUngrabKeyboard XFreeColors XFreePixmap XDestroyWindow Lines of Code. For a project like slock there is no need to carry around global state. By moving the three structures to main() it is now clear which functions modify which state, greatly improving the readability of the code, especially given slock is a suid program.
2016-09-08config.mk: be more explicative about FLAGSQuentin Rameau
Group each *FLAG with its description and add a NetBSD specific.
2016-09-08Ensure Polyphemus-Mitigation and properly drop privilegesFRIGN
Don't hide privilege drops inside readpw() and actually make it configurable what you are dropping to in config.h. The privilege drop comes after opening the Display because the user "nobody" with "nogroup" can't do that. So why do I call this strategy the Polyphemus-Mitigation? """ After the giant returns in the evening and eats two more of the men, Odysseus offers Polyphemus some strong and undiluted wine given to him earlier on his journey. Drunk and unwary, the giant asks Odysseus his name, promising him a guest-gift if he answers. Odysseus tells him "Οὖτις", which means "nobody" and Polyphemus promises to eat this "Nobody" last of all. With that, he falls into a drunken sleep. Odysseus had meanwhile hardened a wooden stake in the fire and now drives it into Polyphemus' eye. When Polyphemus shouts for help from his fellow giants, saying that "Nobody" has hurt him, they think Polyphemus is being afflicted by divine power and recommend prayer as the answer. """ (source: https://en.wikipedia.org/wiki/Polyphemus)
2016-09-07Unify how we check passwords between different OSesQuentin Rameau
2016-09-07make error message prefix consistentMarkus Teich
2016-09-02increasing for loops are idiomaticMarkus Teich
2016-09-02Localize running and failure inside readpw()Quentin Rameau
They are only needed there, so don't make them global.
2016-09-02Move screen unlocking inside cleanup()Quentin Rameau
2016-09-02Re-introduce the waiting loop for input grabbingQuentin Rameau
We actually “need” to wait a little for input to be released before locking for cases where slock is spawned from other graphical applications using keybindings. This undoes the misbehaviour I introduced in c2f9757, sorry for the mess.
2016-09-02Add cleanup() to do free(locks) + XCloseDisplay()Quentin Rameau
2016-08-31Refactor dontkillme()FRIGN
- Use file pointers instead of raw I/O, inspired by Kernel code. - Use OOM_SCORE_ADJ_MIN from linux/oom.h instead of working with magic values. - Stricter error checking and descriptive error messages. The reasoning for using the constant rather than magic values lies in the fact that this ensures people get the message. With "-1000", a code reviewer would question if that is really the lowest possible number or just an arbitrary value. The kernel ABI probably won't change, but even in the case, we wouldn't have to modify the code. The OOM killer only is guaranteed to not kill you if you have OOM_SCORE_ADJ_MIN.
2016-08-31Convert manpage to mandoc and fix usageFRIGN
In all honor, the previous usage was formally more correct, but for the sake of consistency across all the tools having the v-flag, I separated it from the command-string. Also, make use of the mandoc macros for the manpage. This makes it easier to maintain, extend and change in the future.
2016-08-31fix CVE-2016-6866Markus Teich
2016-08-31Update bsd-auth string.Markus Teich
Thanks to Hiltjo for discovering this.
2016-08-30Exit as soon as possible on input grabbing errorQuentin Rameau
We want to know at once if slock failed or not to lock the screen, not seing a black screen for a whole second (or two) and then die. Thanks to ^7heo for reporting this.
2016-08-22Refactor main()FRIGN
- Add arg.h and fix usage Given slock is suid we don't want to have half-measures in place to parse the arguments in case the code is changed in the future with somebody not paying enough attention. Also, fix the usage string output to be more consistent across the suckless toolbase and make it reflect the manpage entry. - Comments Use proper block comments and add/change them where necessary to help in studying the code. - Error messages Consistently prepend them with "slock:" and fix wording and do a proper cleanup before quitting (XCloseDisplay and free the locks), making the die() semantics consistent with st's. - getpwuid() error reporting Properly present an error message if getpwuid() fails. - fork() error reporting Properly present an error message if fork() fails. If we cannot close the connection within the fork context we abort the operation and report an error. - execvp() error handling If execvp fails, we cannot call die() afterwards as this implies calling exit(). We must use _exit() to prevent the libc from doing now "illegal" cleanup-work.
2016-08-13clear passwords with explicit_bzeroHiltjo Posthuma
Make sure to explicitly clear memory that is used for password input. memset is often optimized out by the compiler. Brought to attention by the OpenBSD community, see: https://marc.info/?t=146989502600003&r=1&w=2 Thread subject: x11/slock: clear passwords with explicit_bzero Changes: - explicit_bzero.c import from libressl-portable. - Makefile: add COMPATSRC for compatibility src. - config.mk: add separate *BSD section in config.mk to simply uncomment it on these platforms.
2016-02-15Revert "No need for usage()"Markus Teich
This reverts most of commit a6dc051e3744ce5b14c54d2d246d3e8258207e76 and fixes some related stuff: - keep spelling fixes from original commit - make -h and -v also work when followed by more arguments - any unknown flag prints usage - fix output of -v to display "slock: version 1.3" instead of "slock: slock-1.3"
2016-02-15revert using argv0 and minor fixupMarkus Teich
- use hardcoded "slock" instead of argv[0] - add "slock: " to fprintf calls, where it was missing - revert `argc--, argv++` shifting
2016-02-14Use argv0 instead of passing "slock:" to die every timeFRIGN
2016-02-14No need for usage()FRIGN
There are 2 arguments why -v and -h are broken: 1) if you are running off git, -v will show the last stable release, effectively making this option useless. people running stable versions leave open an attack surface this way in case there are vulnerabilities found. 99% of the people are also using package managers to keep their software up to date, instead of running $TOOL -v to check how old it is. 2) -h is a sad excuse for not just looking at the manual page (man 1 slock). Given we accept a post_lock_command, we can't be as liberal and just intercept certain flags. I changed the manpage to reflect this change.
2016-02-14Clarify config.def.hFRIGN
Clear up the wording a bit and explain what failonclear means.
2016-02-14Simplify the oom-taming-functionFRIGN
There really is no need to source a defined variable from a linux header. The OOM-rank ranges from -1000 to 1000, so we can safely hardcode -1000, which is a sane thing to do given slock is suid and we don't want to play around too much here anyway. On another notice, let's not forget that this still is a shitty heuristic. The OOM-killer still can kill us (thus I also changed the wording in the error-message. We do not disable the OOM-killer, we're just hiding.
2016-02-11add slock.1 man pageMarkus Teich
2016-02-11Update license yearFRIGN
It actually was 2014 and not 2015.
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-16 16:59:49 +0000