# SCORECARD for Amy LePeilbet, reviews for DEMO 2006
#################################################################
# A line that begins with the symbol '#' is considered a
# comment line and is ignored by the software. 
# 
# See the bottom of this file for formatting information, and
# try not to deviate significantly from the specified format.

9: Mixing properties of triangular feedback shift registers
AUTHORS: Bernd Schomburg
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

24: On the Diffie-Hellman problem over $GL_{n}$
AUTHORS: A. A. Kalele and V. R. Sule
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

25: Analysis of Affinely Equivalent Boolean Functions
AUTHORS: Meng Qing-shu and Yang min and Zhang Huan-guo and Liu Yu-zhen
SUBREVIEWER: Some One
SCORE: 5
CONFIDENCE: 3
Technical: 2
Editorial: 2
Suitability: 3
AUTHOR-COMMENTS: 
The paper addresses the question of generating pseudorandom data in a
provably secure way. Essentially, despite well theoretical understanding
of pseudorandomness, practical random generators are not analyzed in a
provably 
secure way, and usually based on some heuristic argument. In contrast, the

point of this paper is to (1) give a clean and formal definition 
what it means to have secure (pseudo)random generation which withstands a

variety of powerful adversarial attacks (such as learning some of the
outpus of the generator, resetting its state, affecting the fresh
randomness used to 
refresh the state, etc.; (2) give a simple and elegant scheme which once
and for all should settle the general paradigm of how to construct such
generators.
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

28: Improved Proxy Re-Encryption Schemes with Applications to Secu...
AUTHORS: Giuseppe Ateniese and Kevin Fu and Matthew Green and Susan Hohenberger
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

39: On the Security of a Group Signature Scheme with Strong Separa...
AUTHORS: Lihua Liu and Zhengjun Cao
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

40: Polyhedrons over Finite Abelian Groups and Their Cryptographic...
AUTHORS: Logachev~O.A. and Salnikov~A.A. and Yaschenko~V.V.
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

42: On the affine classification of cubic bent functions
AUTHORS: Sergey Agievich
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

43: Choosing Parameter Sets for NTRUEncrypt with NAEP and SVES-3
AUTHORS: Nick Howgrave-Graham and Joseph H. Silverman and William Whyte
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

46: Cryptanalysis of two identification schemes based on an ID-bas...
AUTHORS: Qiang Tang and Chris J. Mitchell
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

113: Mitigating Dictionary Attacks on Password-Protected Local Storage
AUTHORS: Ran Canetti and Shai Halevi and Michael Steiner
SUBREVIEWER: 
SCORE: 
CONFIDENCE: 
Technical: 
Editorial: 
Suitability: 
AUTHOR-COMMENTS: 
PC-COMMENTS: 
CHAIR-COMMENTS: 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

#################################################################
# Formatting information
#################################################################
# The reviews should look as follows:
# 
#     num: Title
#     AUTHORS: names (optional)
#     SUBREVIEWER: name (optional)
#     SCORE: num
#     CONFIDENCE: num
#     aux-criteria-1: num
#     aux-criteria-2: num
#     [...]
#     AUTHOR-COMMENTS: anything here is considered comments to the
#       authors
#     PC-COMMENTS: anything here is considered comments to 
#       to program committee
#     CHAIR-COMMENTS: anything here is considered comments
#       to the program chair
#     +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#  
# Different reviews in the same file are separated with a line of '+'
# symbols (at least 20 '+' symbols, with no white-spaces or anything
# else). 
# 
# Each review starts by a line containing the submission number and
# optionally the title. The software ignores the title and only uses
# the submission number to identify the submission that you are
# reviewing. (It will, however, display a warning if you supply a
# title that is "too far from the right one"). You can optionally put
# the authors names in the next line, the software will ignore this.
# 
# Next you can put the name of a sub-reviewer. If this line is
# missing or the name left empty, the software will record no
# sub-reviewer for this review. 
# 
# Next comes lines for the score and confidence. If the num is not
# supplied, the software will record the special symbol 'ignore'.
# Next you can put lines for the other evaluation criteria that the
# chair specified (e.g., Technical, Editorial quality, etc). If the
# software does not recognize a criterion it will ignore that line
# and display a warning. 
#
# Next comes the comments. Anything after the tag "AUTHOR-COMMENTS:"
# (which must be at the beginning of a line) and on the following
# lines is considered comments-to-authors, until the end of the
# review or until a line that begins with "PC-COMMENTS:" or
# "CHAIR-COMMENTS:". Similarly, these two tags denote the beginning
# of the comments-to-committee or comments-to-chair, respectively.