[tor-commits] [flashproxy/master] Update smtp-gmail-in.l.google.com public key pin.

[dcf at torproject.org]

commit f8221f15c7f8baf32a60e547381a7fb2a743b108
Author: David Fifield <david at bamsoftware.com>
Date:   Mon Oct 1 21:37:53 2012 -0700

    Update smtp-gmail-in.l.google.com public key pin.
    
    The key appears to have changed sometime between the hours
    Mon Oct  1 21:13:00 MDT 2012
    Mon Oct  1 22:13:00 MDT 2012
    
    This is the new certificate that I see.
    
    Subject: commonName=mx.google.com/organizationName=Google Inc/stateOrProvinceName=California/countryName=US/localityName=Mountain View
    Issuer: commonName=Google Internet Authority/organizationName=Google Inc/countryName=US
    Public Key type: rsa
    Public Key bits: 1024
    Not valid before: 2012-09-12 11:56:56
    Not valid after:  2013-06-07 19:43:27
    MD5:   f1f3 f722 d0a4 3a61 7b80 6165 ce0f fb82
    SHA-1: 386f 5189 f29a d7b2 4daa 2841 a037 65b6 7ab3 bf0b
    -----BEGIN CERTIFICATE-----
    MIIDfjCCAuegAwIBAgIKO3Qp5QAAAABopjANBgkqhkiG9w0BAQUFADBGMQswCQYD
    VQQGEwJVUzETMBEGA1UEChMKR29vZ2xlIEluYzEiMCAGA1UEAxMZR29vZ2xlIElu
    dGVybmV0IEF1dGhvcml0eTAeFw0xMjA5MTIxMTU2NTZaFw0xMzA2MDcxOTQzMjda
    MGcxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRYwFAYDVQQHEw1N
    b3VudGFpbiBWaWV3MRMwEQYDVQQKEwpHb29nbGUgSW5jMRYwFAYDVQQDEw1teC5n
    b29nbGUuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCwL/RgYdUfQSsc
    05cQbty4oLV9sY8tmL6bv94vpTFobhoK5HHWAuwlQERdiyLRVfI2zatH2pFuD6Iq
    s9E7x1LvTuNw/G/6yBKidB52fax7unMKG9aVOhKLZ2BmZhMFpRcRMMUefbV0Ry82
    K2t+Sw1jzMlnupTfQ6kLw+kCX583wwIDAQABo4IBUDCCAUwwHQYDVR0lBBYwFAYI
    KwYBBQUHAwEGCCsGAQUFBwMCMB0GA1UdDgQWBBRps2dcBH8W78GF++gt5Pwh6X2T
    rzAfBgNVHSMEGDAWgBS/wDDr9UMRPme6npH7/Gra42sSJDBbBgNVHR8EVDBSMFCg
    TqBMhkpodHRwOi8vd3d3LmdzdGF0aWMuY29tL0dvb2dsZUludGVybmV0QXV0aG9y
    aXR5L0dvb2dsZUludGVybmV0QXV0aG9yaXR5LmNybDBmBggrBgEFBQcBAQRaMFgw
    VgYIKwYBBQUHMAKGSmh0dHA6Ly93d3cuZ3N0YXRpYy5jb20vR29vZ2xlSW50ZXJu
    ZXRBdXRob3JpdHkvR29vZ2xlSW50ZXJuZXRBdXRob3JpdHkuY3J0MAwGA1UdEwEB
    /wQCMAAwGAYDVR0RBBEwD4INbXguZ29vZ2xlLmNvbTANBgkqhkiG9w0BAQUFAAOB
    gQCFcplxu13XO6hGzWJr+vMPyAFMlor9st8KLAwUmG/H1ulMjEbCJmNn03eNOUUD
    kiJX+Fh9VNOi059XJ44mD4za/YOQXvtWav5xui3UPJXJmEKOzuNGgFjEJUms3Tu2
    wKCxvBVcL94AvA9vMVllmP8bxKQzDzf5FXn3FQ5nG9sYww==
---
 flashproxy-reg-email |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/flashproxy-reg-email b/flashproxy-reg-email
index cdac964..7ac913a 100755
--- a/flashproxy-reg-email
+++ b/flashproxy-reg-email
@@ -59,7 +59,7 @@ A4GBAFjOKer89961zgK5F7WF0bnj4JXMJTENAKaSbn+2kmOeUJXRmm/kEd5jhW6Y
 # SHA-1 digest of expected public key. See
 # http://www.imperialviolet.org/2011/05/04/pinning.html for the reason behind
 # hashing the public key, not the entire certificate.
-PUBKEY_SHA1 = "e341556ff3fd18e155ce30971fc93e740aa4b185".decode("hex")
+PUBKEY_SHA1 = "1926a5cb3fd7e48328188946e73ade84f55787dc".decode("hex")
 
 # Registrations are encrypted with this public key before being emailed. Only
 # the facilitator operators should have the corresponding private key. Given a