This repository has been archived by the owner on Jul 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
/
doc_test.go
49 lines (41 loc) · 1.64 KB
/
doc_test.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
// Copyright © 2015 Nik Unger
//
// This file is part of ringsig.
//
// Ringsig is free software: you can redistribute it and/or modify it under the
// terms of the GNU Lesser General Public License as published by the Free
// Software Foundation, either version 3 of the License, or (at your option)
// any later version.
//
// Ringsig is distributed in the hope that it will be useful, but WITHOUT ANY
// WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
// FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
// details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with ringsig. If not, see <http://www.gnu.org/licenses/>.
package ringsig_test
import (
"github.com/Nik-U/ringsig"
"github.com/Nik-U/ringsig/shacham"
)
func Example() {
// Generate new scheme parameters
scheme, _ := shacham.New(2)
// In the real world, these parameters would be saved using scheme.WriteTo
// and then loaded by the clients using shacham.Load.
// Two clients generate key pairs
alice := scheme.KeyGen()
bob := scheme.KeyGen()
// We will sign over the ring of the two users. In general, higher level
// communication protocols will somehow specify the ring used to sign the
// message (either explicitly or implicitly).
ring := []ringsig.PublicKey{alice.Public, bob.Public}
// Alice signs a message intended for Bob
sig, _ := scheme.Sign("message", ring, alice)
// Bob verifies the signature
if scheme.Verify("message", sig, ring) {
// Both Alice and Bob are now convinced that Alice signed the message.
// However, nobody else can be convinced of this cryptographically.
}
}