[telepathy-spec/master] Credentials access control: the byte sent is not garanteed to be NUL
Guillaume Desmottes
guillaume.desmottes at collabora.co.uk
Thu May 14 02:40:21 PDT 2009
---
spec/Channel_Type_Tubes.xml | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/spec/Channel_Type_Tubes.xml b/spec/Channel_Type_Tubes.xml
index 2cc0131..e7d3e59 100644
--- a/spec/Channel_Type_Tubes.xml
+++ b/spec/Channel_Type_Tubes.xml
@@ -175,7 +175,8 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
</tp:enumvalue>
<tp:enumvalue suffix="Credentials" value="3">
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
- <p>The connecting process must send a single zero (NUL) byte when
+ <p>May only be used on UNIX sockets.
+ The connecting process must send a byte when
it first connects, which is not considered to be part of the data
stream. If the operating system uses sendmsg() with SCM_CREDS or
SCM_CREDENTIALS to pass credentials over sockets, the connecting
--
1.5.6.5
More information about the telepathy-commits
mailing list