Server Administration

  Home arrow Server Administration arrow Page 4 - Authentication in Client/Server Commun...
SERVER ADMINISTRATION

Authentication in Client/Server Communication
By: O'Reilly Media
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 1
    2010-08-11

    Table of Contents:
  • Authentication in Client/Server Communication
  • Command Packet
  • Command Packet: Server Responses
  • OK Packet

  •  
     

    SEARCH CODEWALKERS

    TOOLS YOU CAN USE

    advertisement

    Authentication in Client/Server Communication - OK Packet


    (Page 4 of 4 )

    An OK packet is sent to indicate that the server successfully completed the command. It is sent in response to the following commands:

    • COM_PING 
    • COM_QUERYif the query does not need to return a result set; for example,INSERT,UPDATE, orALTER TABLE
    • COM_REFRESH
    • COM_REGISTER_SLAVE

    This type of packet is appropriate for commands that do not return a result set. Its format, however, permits sending some extra status information, such as the number of modified records, the value of the automatically generated primary key, or a custom status message in a string format. The structure of the packet body is documented in Table 4-8 .

    Table 4-8. Format of server’s OK packet

     

     

     

    Offset in the body

    Length

    Description

    0

    1

    A byte with the value of 0, indicating that the packet has no fields.

    1

    rows_len

    The number of records that the query has changed in the field length format described in the "Data Field" section, earlier in this chapter. Its length varies depending on the value. I will refer to its length as rows_lento express the subsequent offsets.

     

     

    Please check back next week for the conclusion to this series.


    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.
    blog comments powered by Disqus

    SERVER ADMINISTRATION ARTICLES

    - SSH Case Studies 3/19
    - SSH Case Studies
    - Server Responses to Client Communication
    - Authentication in Client/Server Communication
    - Client/Server Communication
    - Understanding Awk in the UNIX Shell
    - Stream Editor in the UNIX Shell
    - Processes in the UNIX Shell
    - Migrating from Windows to Wine
    - Wine: Not Another Emulator
    - Preventive Measures to Block SSH Attacks
    - Monitoring Temperatures with Cacti
    - Cacti: RRDTool-based Graphing Solution
    - Network Magic 5.0 Review
    - Netfilter and Iptables Overview


    © 2003-2012 by Developer Shed. All rights reserved. DS Cluster 2 - Follow our Sitemap