Commit Graph

9 Commits

Author SHA1 Message Date
5a40bf47f4 Convert print statements to print functions, even when commented. Fixes #3408. 2020-09-11 14:50:44 -04:00
55f8408718 use print function over print statement in ./misc/ directory 2019-03-22 11:41:16 +01:00
3719978215 misc/simulators/hashbasedsig.py: revert last patch; the original code was correct.
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
2014-02-25 16:57:57 +00:00
40c12fc736 misc/simulators/hashbasedsig.py: fix minor miscalculation bug.
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
2014-02-25 16:55:19 +00:00
b262f656f4 misc/simulators/hashbasedsig.py: the cost of labels was being double-counted.
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
2014-02-25 01:04:03 +00:00
946a9f9ddd misc/simulators/hashbasedsig.py: fix an incorrect comment.
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
2014-02-25 00:58:54 +00:00
bbb6e5d25e misc/simulators/hashbasedsig.py: simplify by removing unnecessary local function that captured a variable declared in a for loop (this was not a bug, but the code was unclear). Also fix a pyflakes warning about an import. refs #1556 2011-10-06 19:30:01 -07:00
1c449db88f setup: remove separate licensing declaration
Whenever Free Software/Open Source legal folks are examining the Tahoe-LAFS source code, it seems like there has to be a discussion and documentation about every single licensing declaration. Since this one is (was) permissive, then you would think it could be avoided, but I'm not betting on it. We would probably have to install a copy of the MIT licence into every one of the "copyright" files under the debian/ subdirectory, for example. So: let's just let hashbasedsig.py be licensed the same way as the rest of Tahoe-LAFS.
2010-11-10 20:45:30 -08:00
8beb5ea799 add simulator to explore the trade-offs for hashed-based digital signatures 2010-08-18 20:06:30 -07:00