Grimes Township, Cerro Gordo County, Iowa

Grimes Township is one of sixteen townships in Cerro Gordo County, Iowa, USA. As of the 2000 census, its population was 851.

Grimes Township,
Cerro Gordo County
Township
Coordinates: 42°56′58″N 093°25′55″W
Country United States
State Iowa
CountyCerro Gordo
Area
 • Total36.08 sq mi (93.44 km2)
 • Land36.08 sq mi (93.44 km2)
 • Water0 sq mi (0 km2)
Elevation1,240 ft (378 m)
Population
 (2000)
 • Total851
 • Density23.6/sq mi (9.1/km2)
FIPS code19-91773[2]
GNIS feature ID0467978

Geography

Grimes Township covers an area of 36.08 square miles (93.4 km2) and contains two incorporated settlements: all of Meservey and most of Thornton (which is partly in Pleasant Valley Township to the east). According to the USGS, it contains one cemetery, Pleasant View.

gollark: So this is a mess. PotatOS is actually shipping a mildly different ECC library with a different curve because steamport provided the ECC code ages ago.
gollark: I mean, what do you expect to happen if you do something unsupported and which creates increasingly large problems each time you do it?
gollark: <@151391317740486657> Do you know what "unsupported" means? PotatOS is not designed to be used this way.
gollark: Specifically, 22 bytes for the private key and 21 for the public key on ccecc.py and 25 and 32 on the actual ingame one.
gollark: <@!206233133228490752> Sorry to bother you, but keypairs generated by `ccecc.py` and the ECC library in use in potatOS appear to have different-length private and public keys, which is a problem.EDIT: okay, apparently it's because I've been accidentally using a *different* ECC thing from SMT or something, and it has these parameters instead:```---- Elliptic Curve Arithmetic---- About the Curve Itself-- Field Size: 192 bits-- Field Modulus (p): 65533 * 2^176 + 3-- Equation: x^2 + y^2 = 1 + 108 * x^2 * y^2-- Parameters: Edwards Curve with c = 1, and d = 108-- Curve Order (n): 4 * 1569203598118192102418711808268118358122924911136798015831-- Cofactor (h): 4-- Generator Order (q): 1569203598118192102418711808268118358122924911136798015831---- About the Curve's Security-- Current best attack security: 94.822 bits (Pollard's Rho)-- Rho Security: log2(0.884 * sqrt(q)) = 94.822-- Transfer Security? Yes: p ~= q; k > 20-- Field Discriminant Security? Yes: t = 67602300638727286331433024168; s = 2^2; |D| = 5134296629560551493299993292204775496868940529592107064435 > 2^100-- Rigidity? A little, the parameters are somewhat small.-- XZ/YZ Ladder Security? No: Single coordinate ladders are insecure, so they can't be used.-- Small Subgroup Security? Yes: Secret keys are calculated modulo 4q.-- Invalid Curve Security? Yes: Any point to be multiplied is checked beforehand.-- Invalid Curve Twist Security? No: The curve is not protected against single coordinate ladder attacks, so don't use them.-- Completeness? Yes: The curve is an Edwards Curve with non-square d and square a, so the curve is complete.-- Indistinguishability? No: The curve does not support indistinguishability maps.```so I might just have to ship *two* versions to keep compatibility with old signatures.

References
  1. "US Board on Geographic Names". United States Geological Survey. 2007-10-25. Retrieved 2008-01-31.
  2. "U.S. Census website". United States Census Bureau. Retrieved 2008-01-31.



This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.