[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [tor-browser-spec/master] Bug 18406: Make sure MAR signatures are check before releasing



commit 375032ad951e43c4f6043a9c8120282c0e6b1a6c
Author: Georg Koppen <gk@xxxxxxxxxxxxxx>
Date:   Mon Mar 14 14:28:31 2016 +0000

    Bug 18406: Make sure MAR signatures are check before releasing
---
 processes/ReleaseProcess | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/processes/ReleaseProcess b/processes/ReleaseProcess
index 97d0f28..86172d5 100644
--- a/processes/ReleaseProcess
+++ b/processes/ReleaseProcess
@@ -132,8 +132,14 @@
    # Don't forget to link to Mozilla's security advisories if this is a security
    # update, or Nadim will yell at you.
 
+#. Check whether the MAR files got properly signed
+   # Point SIGNMAR to your signmar binary
+   # Point LD_LIBRARY_PATH to your mar-tools directory
+   cd tor-browser-bundle/gitian/$TORBROWSER_VERSION
+   ../../tools/marsigning_check.sh
+   cd ..
+
 #. Update and upload new update responses for the updater
-   cd tor-browser-bundle/gitian
    # IMPORTANT: Copy the signed MAR files back before creating the update
    # responses!
    make update_responses # (or update_responses-alpha, update_responses-beta)

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits