-
-
Notifications
You must be signed in to change notification settings - Fork 66
mod_notionflux: fchmod of socket always fails on FreeBSD #350
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.
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
Comments
While this should be fine from a security standpoint since we're wrapping the socket into a secured temporary directory, it still feels suboptimal until now that it's coming back to me that FreeBSD doesn't support permissions on socket files no matter whether per chmod or fchmod. |
This fchmod is weird - it happens right after socket() - so this fd is a completely new socket and isn't associated with a path yet and so it makes perfect sense that the fchmod would fail. Note that the chmod after we bind the socket (a few lines later) succeeds. |
Hello @jeffpc I've just committed notion port to FreeBSD tree: Could you update your ports tree and do a quick run test? Thanks |
On Fri, Mar 07, 2025 at 19:31:35 -0800, Nuno Teixeira wrote:
nunotexbsd left a comment (raboof/notion#350)
Hello @jeffpc
I've just committed notion port to FreeBSD tree:
https://cgit.freebsd.org/ports/commit/?id=b2dddd954285133eade5e1c9673ae9ad69e4bd17
Nice!
Could you update your ports tree and do a quick run test?
I'll try to find a few minutes this weekend to give it a try.
|
Sorry for the delay. I successfully built the port. My quick test of it indicates that it works. |
Nice! Also, If you got any custom key bindings on Thanks! |
On FreeBSD, mod_notionflux fails on start (xmessage opens mentioning an invalid argument error) because of an invalid arg related to the listening socket.
start_listening
tries to fchmod the newly created socket but on FreeBSD this always fails. The manpage for fchmod says:The following (hacky) patch fixes the issue and mod_notionflux seems to start up fine.
The text was updated successfully, but these errors were encountered: