Review Request 129526: RFE: kwallet-pam should use XDG_RUNTIME_DIR instead of /tmp for the socketPath

David Faure faure at kde.org
Sun Jan 8 16:09:45 UTC 2017


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129526/#review101873
-----------------------------------------------------------



I like the idea. However according to http://standards.freedesktop.org/basedir-spec/latest/, one is supposed to check permissions on XDG_RUNTIME_DIR before using it.
I implemented those checks in QStandardPaths::RuntimeLocation, but this code is C.
Would it be possible to use QStandardPaths in the caller of this code and then pass it with --socketPath= ? (disclaimer I know nothing about PAM)


pam_kwallet.c (line 418)
<https://git.reviewboard.kde.org/r/129526/#comment68149>

    trailing spaces


- David Faure


On Nov. 21, 2016, 11:30 p.m., Damjan Georgievski wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/129526/
> -----------------------------------------------------------
> 
> (Updated Nov. 21, 2016, 11:30 p.m.)
> 
> 
> Review request for KDE Frameworks.
> 
> 
> Bugs: 365722
>     https://bugs.kde.org/show_bug.cgi?id=365722
> 
> 
> Repository: kwallet-pam
> 
> 
> Description
> -------
> 
> Most recent Linux distributions setup a per-user XDG_RUNTIME_DIR as a tmpfs, which is also tied to their session lifecycle. Typically this is in /run/user/1000/.
> 
> My suggestion is to use $XDG_RUNTIME_DIR/kwallet5.socket if XDG_RUNTIME_DIR exists, or fallback to /tmp/kwallet5_${username}.socket if it doesn't.
> 
> Reproducible: Always
> 
> 
> Diffs
> -----
> 
>   pam_kwallet.c 809ab9a 
> 
> Diff: https://git.reviewboard.kde.org/r/129526/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Damjan Georgievski
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20170108/e2c03d85/attachment.html>


More information about the Kde-frameworks-devel mailing list