14 Jan 2021 08:25:36 GMT Breakage in RX Connection ID calculation

This morning at 14 Jan 2021 08:25:36 GMT all restarted or newly started
OpenAFS 1.8 clients and servers began to experience RX communication
failures.  The RX Connection ID of all calls initiated by the peer are
the same:

  0x80000002

Patches to correct the flaw are available from OpenAFS Gerrit

  https://gerrit.openafs.org/14491
  rx: rx_InitHost do not overwrite RAND_bytes rx_nextCid

  https://gerrit.openafs.org/14492
  rx: update_nextCid overflow handling is broken

IBM AFS 3.x and OpenAFS clients and servers prior to 1.8 performing
unauthenticated will suffer from a lack of randomness when selecting
the initial CID value.  As a result, communication failures might
occur depending upon the selected CID value.   Further research to
determine the impact is required.

Please note that all versions of AuriStor RX and Linux rxrpc as used by
clients, servers and administrative tooling are unaffected.

Jeffrey Altman
AuriStor, Inc.

begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:AuriStor, Inc.
adr:;;255 W 94TH ST STE 6B;New York;NY;10025-6985;United States
email;internet:[email protected]
title:CEO
tel;work:+1-212-769-9018
url:https://www.linkedin.com/in/jeffreyaltman/
version:2.1
end:vcard