Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1704 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1704.

Report 1704 Actions

    Problem Report Number 1704
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0487
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Window System Application Interface V2
    Certification Program The Open Brand certification program
    Test Suite VSW version 5.0.2
    Test Identification Xproto/noprt 3
    Problem Summary PG4W.00097 This IR claims that a zero request length for the NoOperation request is valid.
    Problem Text

    The NoOperation request does not require any length.

    There is no difference between what the test scripts send
    for the correct NoOperation call and the too small request.
    Test Output
    520|75 3 00004129 1 1|VSW5TESTSUITE PURPOSE 3
    520|75 3 00004129 1 2|Assertion NoOperation-3.(A)
    520|75 3 00004129 1 3|When a client sends an invalid NoOperation protocol request
    520|75 3 00004129 1 4|to the X server, in which the length field of the request is
    520|75 3 00004129 1 5|less than the minimum length required to contain the
    520|75 3 00004129 1 6|request, then the X server sends back a BadLength error to
    520|75 3 00004129 1 7|the client.
    520|75 3 00004129 1 8|METH: Call library function testfunc() to do the following:
    520|75 3 00004129 1 9|METH: Open a connection to the X server using native byte sex.
    520|75 3 00004129 1 10|METH: Send an invalid NoOperation protocol request to the X server with length
    520|75 3 00004129 1 11|METH: one less than the minimum length required to contain the request.
    520|75 3 00004129 1 12|METH: Verify that the X server sends back a BadLength error.
    520|75 3 00004129 1 13|METH: Open a connection to the X server using reversed byte sex.
    520|75 3 00004129 1 14|METH: Send an invalid NoOperation protocol request to the X server with length
    520|75 3 00004129 1 15|METH: one less than the minimum length required to contain the request.
    520|75 3 00004129 1 16|METH: Verify that the X server sends back a BadLength error.
    520|75 3 00004153 1 1|INFO: Processing a big request
    520|75 3 00004153 1 2|REPORT: Expect: wanted ERROR - BadLength , got NOTHING
    520|75 3 00004153 1 3|REPORT: client 0 failed to recv BadLength error
    520|75 3 00004153 1 4|REPORT: Test NoOperation failed with 1 error.
    520|75 3 00004156 1 1|INFO: Processing a big request
    520|75 3 00004156 1 2|REPORT: Expect: wanted ERROR - BadLength , got NOTHING
    520|75 3 00004156 1 3|REPORT: client 0 failed to recv BadLength error
    520|75 3 00004156 1 4|REPORT: Test NoOperation failed with 1 error.
    220|75 3 1 13:30:29|FAIL
    410|75 3 1 13:30:29|IC End


    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We recommend this request be refused.

    We believe the test is correct.

    The NoOperation request does not require any additional information,
    but the request length is not zero. It is specified to be the number
    of four-byte units taken by the request. In this case, the minimum
    size of the NoOperation request is 4 bytes:

    Bytes Description
    1 opcode (127)
    1 unused
    2 request length (1 or greater)

    The successful NoOperation request sends a request length of 1, while
    a bad length is sent as 0.

    The standard states for NoOperation:

    This request has no arguments and no results, but the request
    length field can be nonzero, which allows the request to be
    any multiple of four bytes in lengh. The bytes contained in
    the request are uninterpreted by the server.

    This request can be used in its minimum four-byte form as
    padding where necessary by client libraries that find it
    convenient to force requests to begin on 64-bit boundaries.

    The request can be of any length, and the content can anything, but it
    violates protocol when an invalid length is specified.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority