[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] IRC, freenode, #hurd, 2011-03-28 [[!tag open_issue_hurd]] basically, i'm trying to implement socket credentials for local sockets, and i guessed doing it in pflocal would be the appropriate place what i thought was filling the cmsg data for MSG_CRED at S_socket_recv() call in case i missed it, would there be a way to "identify" the other side of the port associated to the sock_user of that call? pinotree: that's needed by dbus right? cool! (and I don't know) (yes, and gamin) pinotree: you have them already, they're just not stored see S_io_reauthenticate Throw away the ids we went through all that trouble to get... (comment) * pinotree looks hm, and who calls that rpc? everybody since that's how ext2fs knows the permission to apply, for instance ah, i was referring to the reauthenticate of pflocal, not auth_server_authenticate() that's what I'm saying see __hurd_file_name_lookup_retry, which is the very internal part of open() it calls io_reauthenticate() to authenticate itself to the underlying translator of the opened node youpi: so, hm, could be an option make the result of pflocal's S_io_reauthenticate cached in the sock_user struct? yes nice thanks, i will try that change first --- See also [[pflocal_reauth]] and [[sendmsg_scm_creds]].