From 414adb237bc51e0e1b7321364dd73d9b3e635733 Mon Sep 17 00:00:00 2001
From: Nick Mathewson <nickm@torproject.org>
Date: Mon, 17 Sep 2012 10:24:52 -0400
Subject: Parse votes with >31 flags correctly

We were doing (1<<p) to generate a flag at position p, but we should
have been doing (U64_LITERAL(1)<<p).

Fixes bug 6861; bugfix on 0.2.0.3-alpha; reported pseudonymously.
---
 src/or/routerparse.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/or/routerparse.c')

diff --git a/src/or/routerparse.c b/src/or/routerparse.c
index 2bf072b3cf..022add393f 100644
--- a/src/or/routerparse.c
+++ b/src/or/routerparse.c
@@ -2067,7 +2067,7 @@ routerstatus_parse_entry_from_string(memarea_t *area,
     for (i=0; i < tok->n_args; ++i) {
       int p = smartlist_string_pos(vote->known_flags, tok->args[i]);
       if (p >= 0) {
-        vote_rs->flags |= (1<<p);
+        vote_rs->flags |= (U64_LITERAL(1)<<p);
       } else {
         log_warn(LD_DIR, "Flags line had a flag %s not listed in known_flags.",
                  escaped(tok->args[i]));
-- 
cgit v1.2.3-54-g00ecf