Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
suggestings for new py mixmaster
4 views
Skip to first unread message
Anonymous
May 22, 2013, 3:40:02 AM5/22/13
to
hello,
I have seen some discussion in regards to new mixmaster specifications
versus mixminion.
I think Zax, you should just modify the part of mixmaster that deals
with the key legnths, and get that fixed. That should take priority
over back wards compatibility. Everyone should just upgrade to the new
version.
You could just make a code commit for changing the keyside layout, we
could look at that, update our relays to use 4096 bit keys with room
for up to 16k bit keys.
Again, forget about backwards compat.
??
I have seen some discussion in regards to new mixmaster specifications
versus mixminion.
I think Zax, you should just modify the part of mixmaster that deals
with the key legnths, and get that fixed. That should take priority
over back wards compatibility. Everyone should just upgrade to the new
version.
You could just make a code commit for changing the keyside layout, we
could look at that, update our relays to use 4096 bit keys with room
for up to 16k bit keys.
Again, forget about backwards compat.
??
Zax
May 22, 2013, 4:23:19 AM5/22/13
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Wed, 22 May 2013 07:40:02 +0000 (UTC), Anonymous wrote in
Message-Id: <326ca480f967bf6c...@remailer.paranoici.org>:
Backwards compatibility really isn't a problem. If you look at the
header line on each remailer's public key, you'll notice that the
version string always starts with a '2'. Even Mixmaster v3 remailers
have the version string prefixed with'2:'. This dictates the format of
the messages the remailer handles.
The problem is one of forward compatibility. Mixmaster has no
understanding of anything other than the format it currently supports.
Throw something new at it and Mixmaster will just spit it out as an
invalid message. This isn't the end of the world though, we'd just need
stats sources that contain only Mixmaster type remailers and stats
sources that contain both.
The reason I opted to develop a Mixmaster compatible version first was
to ensure it actually worked. Knowing the code is compatible with
existing Mixmaster remailers is the best starting point for anything
new.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBCAAGBQJRnIB3AAoJEIBmv8lxNqHo/KgP/22N0oSjoqgaumrn7zt7pYr+
9YROhHxFIYxRVoIt/Z0deobnsCwBYEEUELFXerq47VvvopOkq4al6d8ztTGWtGCD
S8brW3sbmYZF/Fbcg2Ujgo6ryu2F/hgS8VO/kLGK0UWBpypXKqkxWkW4dMgNe5Nb
F/NLveaezmM/IxnYQJlgpz5gwDEtUDyhuj6PpxN1fa29XofPC6toHTGcjymM/SXb
83ihORWwpjK2yBzICXm08wrAoQYNDjzWg6AAeeLHoSWckPdLE8oMlChIGR6bdQ/J
xbS9nwZ3i2HHfoXSLyOMGc9d+kmQV5di/V/e2+5RrolFAkTm9YJRY4oNu8W742IH
TOVLzBES+WQSCxbkBr2A6nVqWsS1cArkCFofeDb9Bl8xQpBT8yTEiE9xQO7TNZsb
8cYV2Gw5S7xjA7hHuU97FTokqyGZvAQPUqAkOwrc14d33XvfCgPhYsJQiiu89d6D
CV1q+2rAcUlbfHOTDuIQnuxgnZammfwzYL3NteR9CaQoVlx0dHHq66e1kFEtz7cK
1hQ/hZiPRVC0rhtScKplx868AnjdEt+aqccHVDnMZPgXyGX5vJH2NovKipwTO6JX
l70KYVoYN84uRUBSahvBO4vkjFUG7SwHV4a3n8p+dURsaEeLvpbq1EKuna4CncRg
35EfunP5XsNKhyQo+8c2
=NwWF
-----END PGP SIGNATURE-----
--
pub 1024D/228761E7 2003-06-04 Steven Crook <st...@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
sub 4096R/4ABF07E3 2012-02-11 [expires: 2013-02-10]
Hash: SHA256
On Wed, 22 May 2013 07:40:02 +0000 (UTC), Anonymous wrote in
Message-Id: <326ca480f967bf6c...@remailer.paranoici.org>:
header line on each remailer's public key, you'll notice that the
version string always starts with a '2'. Even Mixmaster v3 remailers
have the version string prefixed with'2:'. This dictates the format of
the messages the remailer handles.
The problem is one of forward compatibility. Mixmaster has no
understanding of anything other than the format it currently supports.
Throw something new at it and Mixmaster will just spit it out as an
invalid message. This isn't the end of the world though, we'd just need
stats sources that contain only Mixmaster type remailers and stats
sources that contain both.
The reason I opted to develop a Mixmaster compatible version first was
to ensure it actually worked. Knowing the code is compatible with
existing Mixmaster remailers is the best starting point for anything
new.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBCAAGBQJRnIB3AAoJEIBmv8lxNqHo/KgP/22N0oSjoqgaumrn7zt7pYr+
9YROhHxFIYxRVoIt/Z0deobnsCwBYEEUELFXerq47VvvopOkq4al6d8ztTGWtGCD
S8brW3sbmYZF/Fbcg2Ujgo6ryu2F/hgS8VO/kLGK0UWBpypXKqkxWkW4dMgNe5Nb
F/NLveaezmM/IxnYQJlgpz5gwDEtUDyhuj6PpxN1fa29XofPC6toHTGcjymM/SXb
83ihORWwpjK2yBzICXm08wrAoQYNDjzWg6AAeeLHoSWckPdLE8oMlChIGR6bdQ/J
xbS9nwZ3i2HHfoXSLyOMGc9d+kmQV5di/V/e2+5RrolFAkTm9YJRY4oNu8W742IH
TOVLzBES+WQSCxbkBr2A6nVqWsS1cArkCFofeDb9Bl8xQpBT8yTEiE9xQO7TNZsb
8cYV2Gw5S7xjA7hHuU97FTokqyGZvAQPUqAkOwrc14d33XvfCgPhYsJQiiu89d6D
CV1q+2rAcUlbfHOTDuIQnuxgnZammfwzYL3NteR9CaQoVlx0dHHq66e1kFEtz7cK
1hQ/hZiPRVC0rhtScKplx868AnjdEt+aqccHVDnMZPgXyGX5vJH2NovKipwTO6JX
l70KYVoYN84uRUBSahvBO4vkjFUG7SwHV4a3n8p+dURsaEeLvpbq1EKuna4CncRg
35EfunP5XsNKhyQo+8c2
=NwWF
-----END PGP SIGNATURE-----
--
pub 1024D/228761E7 2003-06-04 Steven Crook <st...@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
sub 4096R/4ABF07E3 2012-02-11 [expires: 2013-02-10]
0 new messages