Chiebot-Mirror
/
c-ares
mirror of https://github.com/c-ares/c-ares.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
A C library for asynchronous DNS requests (grpc依赖)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
651 Commits
14 Branches
96 Tags
22 MiB
Tag: Branch: Tree: 0d1008355a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0d1008355a'
${ noResults }
c-ares/test/ares-test-parse-caa.cc

154 lines
8.3 KiB
Raw Normal View History Unescape

test: fix outdated license headers
11 months ago
/* MIT License
provide SPDX identifiers and a REUSE CI job to verify All files have their licence and copyright information clearly identifiable. If not in the file header, they are set separately in .reuse/dep5. All used license texts are provided in LICENSES/
1 year ago
*
test: fix outdated license headers
11 months ago
* Copyright (c) The c-ares project and its contributors
*
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to deal
* in the Software without restriction, including without limitation the rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice (including the next
* paragraph) shall be included in all copies or substantial portions of the
* Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
* SOFTWARE.
provide SPDX identifiers and a REUSE CI job to verify All files have their licence and copyright information clearly identifiable. If not in the file header, they are set separately in .reuse/dep5. All used license texts are provided in LICENSES/
1 year ago
*
* SPDX-License-Identifier: MIT
*/
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
#include "ares-test.h"
#include "dns-proto.h"
#include <sstream>
#include <vector>
namespace ares {
namespace test {
TEST_F(LibraryTest, ParseCaaReplyMultipleOK) {
std::vector<byte> data = {
0x27, 0x86, 0x81, 0x80, 0x00, 0x01, 0x00, 0x04, 0x00, 0x00, 0x00, 0x00, 0x09, 0x77, 0x69, 0x6B, // '............wik
0x69, 0x70, 0x65, 0x64, 0x69, 0x61, 0x03, 0x6F, 0x72, 0x67, 0x00, 0x01, 0x01, 0x00, 0x01, 0xC0, // ipedia.org......
0x0C, 0x01, 0x01, 0x00, 0x01, 0x00, 0x00, 0x02, 0x23, 0x00, 0x15, 0x00, 0x05, 0x69, 0x73, 0x73, // ........#....iss
0x75, 0x65, 0x67, 0x6C, 0x6F, 0x62, 0x61, 0x6C, 0x73, 0x69, 0x67, 0x6E, 0x2E, 0x63, 0x6F, 0x6D, // ueglobalsign.com
0xC0, 0x0C, 0x01, 0x01, 0x00, 0x01, 0x00, 0x00, 0x02, 0x23, 0x00, 0x13, 0x00, 0x05, 0x69, 0x73, // .........#....is
0x73, 0x75, 0x65, 0x64, 0x69, 0x67, 0x69, 0x63, 0x65, 0x72, 0x74, 0x2E, 0x63, 0x6F, 0x6D, 0xC0, // suedigicert.com.
0x0C, 0x01, 0x01, 0x00, 0x01, 0x00, 0x00, 0x02, 0x23, 0x00, 0x16, 0x00, 0x05, 0x69, 0x73, 0x73, // ........#....iss
0x75, 0x65, 0x6C, 0x65, 0x74, 0x73, 0x65, 0x6E, 0x63, 0x72, 0x79, 0x70, 0x74, 0x2E, 0x6F, 0x72, // ueletsencrypt.or
0x67, 0xC0, 0x0C, 0x01, 0x01, 0x00, 0x01, 0x00, 0x00, 0x02, 0x23, 0x00, 0x25, 0x00, 0x05, 0x69, // g.........#.%..i
0x6F, 0x64, 0x65, 0x66, 0x6D, 0x61, 0x69, 0x6C, 0x74, 0x6F, 0x3A, 0x64, 0x6E, 0x73, 0x2D, 0x61, // odefmailto:dns-a
0x64, 0x6D, 0x69, 0x6E, 0x40, 0x77, 0x69, 0x6B, 0x69, 0x6D, 0x65, 0x64, 0x69, 0x61, 0x2E, 0x6F, // dmin@wikimedia.o
0x72, 0x67 // rg
};
struct ares_caa_reply* caa = nullptr;
cleanup some Windows warnings in test
1 year ago
EXPECT_EQ(ARES_SUCCESS, ares_parse_caa_reply(data.data(), (int)data.size(), &caa));
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
ASSERT_NE(nullptr, caa);
ASSERT_NE(nullptr, caa->next);
ASSERT_NE(nullptr, caa->next->next);
ASSERT_NE(nullptr, caa->next->next->next);
ares_free_data(caa);
}
TEST_F(LibraryTest, ParseCaaReplySingleOK) {
std::vector<byte> data = {
0x27, 0x86, 0x81, 0x80, 0x00, 0x01, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x06, 0x67, 0x6F, 0x6F, // '............goo
0x67, 0x6C, 0x65, 0x03, 0x63, 0x6F, 0x6D, 0x00, 0x01, 0x01, 0x00, 0x01, 0xC0, 0x0C, 0x01, 0x01, // gle.com.........
0x00, 0x01, 0x00, 0x01, 0x43, 0xBE, 0x00, 0x0F, 0x00, 0x05, 0x69, 0x73, 0x73, 0x75, 0x65, 0x70, // ....C.....issuep
0x6B, 0x69, 0x2E, 0x67, 0x6F, 0x6F, 0x67 // ki.goog
};
struct ares_caa_reply* caa = nullptr;
cleanup some Windows warnings in test
1 year ago
EXPECT_EQ(ARES_SUCCESS, ares_parse_caa_reply(data.data(), (int)data.size(), &caa));
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
ASSERT_NE(nullptr, caa);
now that warnings are enabled on test cases, clear a bunch of warnings
1 year ago
EXPECT_EQ(caa->critical, (int)0);
EXPECT_EQ(caa->plength, (size_t)5);
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
EXPECT_STREQ((char *)caa->property, "issue");
now that warnings are enabled on test cases, clear a bunch of warnings
1 year ago
EXPECT_EQ(caa->length, (size_t)8);
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
EXPECT_STREQ((char *)caa->value, "pki.goog");
ares_free_data(caa);
}
TEST_F(LibraryTest, ParseCaaBogusReply1) {
std::vector<byte> data = {
0x27, 0x86, 0x81, 0x80, 0x00, 0x01, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x06, 0x67, 0x6F, 0x6F, // '............goo
0x67, 0x6C, 0x65, 0x03, 0x63, 0x6F, 0x6D, 0x00, 0x01, 0x01, 0x00, 0x01, 0xC0, 0x0C, 0x01, 0x01, // gle.com.........
0x00, 0x01, 0x00, 0x01, 0x43, 0xBE, 0x00, 0x0F, 0x00, 0x00, 0x69, 0x73, 0x73, 0x75, 0x65, 0x70, // ....C.....issuep
0x6B, 0x69, 0x2E, 0x67, 0x6F, 0x6F, 0x67 // ki.goog
};
struct ares_caa_reply* caa = nullptr;
cleanup some Windows warnings in test
1 year ago
EXPECT_EQ(ARES_EBADRESP, ares_parse_caa_reply(data.data(), (int)data.size(), &caa));
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
ASSERT_EQ(nullptr, caa);
}
TEST_F(LibraryTest, ParseCaaBogusReply2) {
std::vector<byte> data = {
0x27, 0x86, 0x81, 0x80, 0x00, 0x01, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x06, 0x67, 0x6F, 0x6F, // '............goo
0x67, 0x6C, 0x65, 0x03, 0x63, 0x6F, 0x6D, 0x00, 0x01, 0x01, 0x00, 0x01, 0xC0, 0x0C, 0x01, 0x01, // gle.com.........
0x00, 0x01, 0x00, 0x01, 0x43, 0xBE, 0x00, 0x0F, 0x00, 0x0e, 0x69, 0x73, 0x73, 0x75, 0x65, 0x70, // ....C.....issuep
0x6B, 0x69, 0x2E, 0x67, 0x6F, 0x6F, 0x67 // ki.goog
};
struct ares_caa_reply* caa = nullptr;
cleanup some Windows warnings in test
1 year ago
EXPECT_EQ(ARES_EBADRESP, ares_parse_caa_reply(data.data(), (int)data.size(), &caa));
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
ASSERT_EQ(nullptr, caa);
}
TEST_F(LibraryTest, ParseCaaBogusReply3) {
std::vector<byte> data = {
0x27, 0x86, 0x81, 0x80, 0x00, 0x01, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x06, 0x67, 0x6F, 0x6F, // '............goo
0x67, 0x6C, 0x65, 0x03, 0x63, 0x6F, 0x6D, 0x00, 0x01, 0x01, 0x00, 0x01, 0xC0, 0x0C, 0x01, 0x01, // gle.com.........
0x00, 0x01, 0x00, 0x01, 0x43, 0xBE, 0x00, 0x10, 0x00, 0x05, 0x69, 0x73, 0x73, 0x75, 0x65, 0x70, // ....C.....issuep
0x6B, 0x69, 0x2E, 0x67, 0x6F, 0x6F, 0x67 // ki.goog
};
struct ares_caa_reply* caa = nullptr;
cleanup some Windows warnings in test
1 year ago
EXPECT_EQ(ARES_EBADRESP, ares_parse_caa_reply(data.data(), (int)data.size(), &caa));
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
ASSERT_EQ(nullptr, caa);
}
TEST_F(LibraryTest, ParseCaaEmptyReply) {
std::vector<byte> data = {
0x27, 0x86, 0x81, 0x80, 0x00, 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x09, 0x77, 0x69, 0x6B, // '............wik
0x69, 0x70, 0x65, 0x64, 0x69, 0x61, 0x02, 0x64, 0x65, 0x00, 0x01, 0x01, 0x00, 0x01, 0xC0, 0x0C, // ipedia.de.......
0x00, 0x06, 0x00, 0x01, 0x00, 0x00, 0x02, 0x58, 0x00, 0x3B, 0x04, 0x6E, 0x73, 0x38, 0x31, 0x0D, // .......X.;.ns81.
0x64, 0x6F, 0x6D, 0x61, 0x69, 0x6E, 0x63, 0x6F, 0x6E, 0x74, 0x72, 0x6F, 0x6C, 0x03, 0x63, 0x6F, // domaincontrol.co
0x6D, 0x00, 0x03, 0x64, 0x6E, 0x73, 0x05, 0x6A, 0x6F, 0x6D, 0x61, 0x78, 0x03, 0x6E, 0x65, 0x74, // m..dns.jomax.net
0x00, 0x78, 0x67, 0xFE, 0x34, 0x00, 0x00, 0x70, 0x80, 0x00, 0x00, 0x1C, 0x20, 0x00, 0x09, 0x3A, // .xg.4..p.... ..:
0x80, 0x00, 0x00, 0x02, 0x58 // ....X
};
struct ares_caa_reply* caa = nullptr;
cleanup some Windows warnings in test
1 year ago
EXPECT_EQ(ARES_ENODATA, ares_parse_caa_reply(data.data(), (int)data.size(), &caa));
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
ASSERT_EQ(nullptr, caa);
}
Coverage code annotations for identification of desirable paths that need testing (#775) Add code annotations for ignoring specific code paths for coverage calculations. The primary purpose of this is to make it easy to see the code paths that we could (and probably should) write test cases for, as these would have the most impact on delivery of a stable product. The annotations used are: `LCOV_EXCL_LINE: <designation>`, `LCOV_EXCL_START: <designation>`, `LCOV_EXCL_STOP` Unfortunately `LCOV_EXCL_BR_LINE` does not appear to be supported by coveralls as it would have been a more elegant solution over START/STOP. We specifically include the `<designation>` not just for future reference but because it makes it easy to identify in case we want to address these conditions in a different way in the future. The main areas designated for exclusion are: 1. `OutOfMemory` - these are hard to test cases, and on modern systems, are likely to never occur due to optimistic memory allocations, which can then later cause the kernel to terminate your application due to memory not actually being available. c-ares does have *some* testing framework for this, if we wish to expand in the future, we can easily use sed to get rid of of these annotations. 2. `DefensiveCoding` - these are impossible to reach paths at the point in time the code was written. They are there for defensive coding in case code is refactored in the future to prevent unexpected behavior. 3. `UntestablePath` - these are code paths that aren't possible to test, such as failure of a system call. 4. `FallbackCode` - This is an entire set of code that is untestable because its not able to simulate a failure of the primary path. This PR also does add some actual coverage in the test cases where it is easy to do. Fix By: Brad House (@bradh352)
5 months ago
TEST_F(LibraryTest, ParseNegativeReply) {
std::vector<byte> data = {
0x27, 0x86, 0x81, 0x80, 0x00, 0x01, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x09, 0x77, 0x69, 0x6B, // '............wik
0x69, 0x70, 0x65, 0x64, 0x69, 0x61, 0x02, 0x64, 0x65, 0x00, 0x01, 0x01, 0x00, 0x01, 0xC0, 0x0C, // ipedia.de.......
0x00, 0x06, 0x00, 0x01, 0x00, 0x00, 0x02, 0x58, 0x00, 0x3B, 0x04, 0x6E, 0x73, 0x38, 0x31, 0x0D, // .......X.;.ns81.
0x64, 0x6F, 0x6D, 0x61, 0x69, 0x6E, 0x63, 0x6F, 0x6E, 0x74, 0x72, 0x6F, 0x6C, 0x03, 0x63, 0x6F, // domaincontrol.co
0x6D, 0x00, 0x03, 0x64, 0x6E, 0x73, 0x05, 0x6A, 0x6F, 0x6D, 0x61, 0x78, 0x03, 0x6E, 0x65, 0x74, // m..dns.jomax.net
0x00, 0x78, 0x67, 0xFE, 0x34, 0x00, 0x00, 0x70, 0x80, 0x00, 0x00, 0x1C, 0x20, 0x00, 0x09, 0x3A, // .xg.4..p.... ..:
0x80, 0x00, 0x00, 0x02, 0x58 // ....X
};
struct ares_caa_reply* caa = nullptr;
EXPECT_EQ(ARES_EBADRESP, ares_parse_caa_reply(data.data(), -1, &caa));
}
Allow parsing of CAA Resource Record (#360) CAA (Certification Authority Authorization) was introduced in RFC 6844. This has been obsoleted by RFC 8659. This commit added the possibility to query CAA resource records with adig and adds a parser for CAA records, that can be used in conjunction with ares_query(3). Closes Bug: #292 Fix By: Daniela Sonnenschein (@lxdicted)
4 years ago
} // namespace test
} // namespace ares