Note we need a flag at the tabled config level, to indicate whether or
not SSL should be used.
As of this commit (and related chunkd changes), encryption will be
disabled by default, with no way to enable it in tabled.
I think this makes much more sense anyway, because it is silly (and
unlikely) to use encryption or not, depending on which chunkd you
connect to.
commit e350f3a2b28ce76391f5494ab8d810407cd9a137
Author: Jeff Garzik <j...@garzik.org>
Date: Fri Mar 5 10:10:15 2010 -0500
tabled: chunkd no longer supplies a <Type> clause for encryption
Signed-off-by: Jeff Garzik <jgar...@redhat.com>
diff --git a/server/storparse.c b/server/storparse.c
index 17b913b..5ed15ea 100644
--- a/server/storparse.c
+++ b/server/storparse.c
@@ -266,24 +266,6 @@ static void cfg_elm_end (GMarkupParseContext *context,
cc->text = NULL;
}
- else if (!strcmp(element_name, "Type")) {
- if (!cc->text) {
- applog(LOG_WARNING,
- "%s: Type element empty", cc->fname);
- return;
- }
-
- if (!strcmp(cc->text, "chunk")) {
- ;
- } else if (!strcmp(cc->text, "chunk-ssl")) {
- cc->stor_encrypt = true;
- } else {
- applog(LOG_WARNING, "%s: Type '%s' is invalid",
- cc->fname, cc->text);
- return;
- }
- }
-
else if (!strcmp(element_name, "Port")) {
if (!cc->text) {
applog(LOG_WARNING, "Port element empty");
--
To unsubscribe from this list: send the line "unsubscribe hail-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
