reSee.it Video Transcript AI Summary
Speaker 0, Speaker 1, and Speaker 2 discuss Dominion’s access to election systems during the 2020 election period in Georgia, with Gwinnett County cited as a specific example. The dialogue confirms that the questioning period was during the 2020 election, and the focus is on whether Dominion remotely accessed election systems and whether such access occurred in Georgia.
Speaker 2 asks if there is any indication of nonelection personnel remotely accessing a Dominion system. Speaker 3 responds that they have reviewed a series of emails produced by Dominion in which they’re discussing remoting into Gwinnett County, Georgia. Speaker 1 then notes that Speaker 0 had mentioned Dominion remote collection or connection to election systems but lacks evidence that it occurred in Georgia. Speaker 0 asserts that there was one county and that they have seen many Dominion emails, requiring translation from Serbian to English to verify technical questions and translations.
Speaker 1 asks specifically: “So it's your testimony that there is evidence of dominion remotely accessing Georgia election equipment?” Speaker 0 answers: “Yes, on the one county. It was included with stuff that I was researching and reading through considering Colorado. Michigan was also involved and there were other ones.”
Speaker 2 inquires about Dominion’s ability to remotely connect to these election systems and whether they could do so without detection. Speaker 0 responds: “Yes.” Speaker 2 then asks if the interviewee is aware of any instances in which that has occurred, and Speaker 0 confirms: “One would be the Denver, Colorado server was granted or requested to grant Belgrave, Only Belgrade. Did search. There is a Belgrade Montana.” The speaker questions why Montana would need to connect to a Colorado file transfer server as part of the election system, noting there are other components and things done in the background concerning the database and the configuration of the database server that still do not have an engineering change order.
Speaker 0 explains that in operational environments, things sometimes break and need fixing, leading to the submission of a change request or, in this case, an engineering change order that is retroactive. The goal is to record the process to ensure change management and integrity of the system. If changes are not recorded, it leads to a bad situation, according to Speaker 0.