s3-registry: support REG_DWORD_BIG_ENDIAN.

Just treat it as a REG_DWORD for now. Long term all these checks will need to
pass away, once we get a real registry...

Guenther

diff --git a/source3/lib/util_reg_api.c b/source3/lib/util_reg_api.c
index 4347e5d6ed76574bd581f56a0762c9745c3ebc98..347c5d6d890ef0da03cc47f73fa043e068ea5ce3 100644 (file)
--- a/source3/lib/util_reg_api.c
+++ b/source3/lib/util_reg_api.c
@@ -39,6 +39,7 @@ WERROR registry_pull_value(TALLOC_CTX *mem_ctx,
 
        switch (type) {
        case REG_DWORD:
+       case REG_DWORD_BIG_ENDIAN:
                if ((size != 4) || (length != 4)) {
                        err = WERR_INVALID_PARAM;
                        goto error;
@@ -151,7 +152,8 @@ WERROR registry_push_value(TALLOC_CTX *mem_ctx,
                           DATA_BLOB *presult)
 {
        switch (value->type) {
-       case REG_DWORD: {
+       case REG_DWORD:
+       case REG_DWORD_BIG_ENDIAN: {
                char buf[4];
                SIVAL(buf, 0, value->v.dword);
                *presult = data_blob_talloc(mem_ctx, (void *)buf, 4);