reSee.it - Related Video Feed

I found Brian in the server logs, showing him the database. Christy Francois let him in, which could be a problem later on.

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.

At some point, there is a correlation between the purging of the database and the date of the audit. They both happen almost at the same time, the day before the audit. This connection requires an explanation.

We're facing north, over here. Are you the team in the broken window, left floor? We're on the left floor, but we don't have a broken window. Okay, copy that. There appears to be movement in another room with a broken window, also on the left floor of the north end. Unsure if the movement is just the curtains; working on getting a clearer view.

I found a video where the speaker goes through some server logs and discovers a database issue. They mention finding different forensics related to it. They also mention a person named Christy, who seems to be active in the GMC community.

Speaker 0 recounts discovering a secret SCIF on campus, a secure facility with files nobody knew existed. An employee walked by a door, inquiries were made, the room was entered, and individuals were found working there with secret files on controversial topics. Those files have been turned over to attorneys and the speaker is pursuing what happened. The speaker notes that Customs and Border Protection (CBP) knows every traveler entering the country and every good that comes in, and they assess and collect tariffs. They highlight that information about travelers during COVID was with national labs under the speaker’s jurisdiction, and that scientists at those labs participated with the Wuhan lab. The speaker claims these scientists traveled back and forth between each other and worked on those experiments, describing this as eye-opening. Addressing Elon and his team, the speaker says they were extremely helpful since the speaker’s arrival in office, assisting in identifying a troubling issue: some of the speaker’s own department employees had downloaded software on the speaker’s phone and laptop to spy on them and record meetings. The speaker states that this had happened to several politicians and notes that bringing in technology experts helped reveal this software; without examining laptops and phones, the activity would still be ongoing. The speaker emphasizes a need to continue partnering with technology companies and experts to bring them in for assistance, as government work—especially within the department under the speaker’s jurisdiction—has been neglected and lagging behind what it should be. The speaker recalls that in the first four months, they couldn’t even email a PowerPoint from Department of Homeland Security servers if it was longer than six pages, illustrating what they view as backwards thinking that hindered national security. The speaker reflects on the concept of a deep state, admitting that they previously believed it existed but didn’t realize how severe it was. They describe daily efforts to uncover individuals who do not love America and who work within the Department and across the federal government. The overall message conveys uncovering secrecy, internal surveillance concerns, cross-agency connections involving CBP and national labs, collaboration with tech experts, and a strong critique of past departmental conduct and systemic protection failures.

The speaker discusses the issue of Windows security logs being purged right before two audits were set to begin. They highlight the difficulty in determining who had access to the RTR admin account, which is shared among all accounts. The speaker questions why someone would delete all the results and records from the Dominion software, which is used for tallying and reporting election results, just before an audit. They mention that the deletion was successful and affected files on the NAS directory where election images and details were stored. Overall, the speaker emphasizes the lack of accountability and the need to understand the motives behind this action.

On 2/11, 462 log entries were overwritten by a script. On 3rd March, 37,686 log entries were overwritten by the same script. The day before we received the system, 330 log entries were overwritten by that script. The EMS admin account was responsible for this. The challenge is that this occurred before an audit, and it deleted all the records and files related to the election. Someone deliberately ran a program to clear all the records in the system used for generating the official results.

On various dates, an individual ran a script to find blank passwords for the accounts on the system. The script was executed multiple times, overwriting a significant number of log entries. The EMS admin account was responsible for this, but due to the lack of accountability in assigning the username, it is difficult to prove who exactly did it. Fortunately, historical data from MTech video feeds helped identify the individuals at the keyboards during those times. However, their names will not be released to protect them from scrutiny and potential impacts.

Dominion can remotely connect to election systems without detection. This has occurred in instances such as the Denver, Colorado server, which was requested to grant access to Belgrade. It is unclear why Belgrade, possibly Belgrade, Montana, would need to connect to a Colorado file transfer server for an election system. There were also background activities concerning the database and its configuration that lack an engineering change order.

On February 11, 462 log entries were overwritten by a script, and on March 3, 37,680 log entries were also overwritten. The day before we received the system, 330 log entries were overwritten. The EMS admin account was responsible for these actions. It raises concerns about the audit's integrity, as one would expect to have complete election context for auditing. The log file from the Dominion software indicates that someone executed a command to purge all election results, successfully deleting all records and images stored in the NAS directory. This action was taken just before the audit began, which is troubling.

Christy accesses the server room and introduces Brian, a new forensics expert. She shows him the server logs and points out the deletion of certain logs. They discuss the importance of investigating further and mention the presence of other individuals. The video ends with a mention of someone named Matt.

The speaker reviewed server logs and identified "Brian." The speaker found a database in the next vendor and new forensics. Christy is mentioned in connection to a server. The speaker shows access and a deletion on the log from the database. A previous tweet shows Christy letting Brian into the server. The speaker repeats "Here he is" multiple times. The speaker mentions another law proposal and altering.

The speakers assert that there is evidence of direct access to the Antrim County election management system (EMS). In the forensic images, they note that on November 5 an anonymous user logged onto the EMS remotely and performed actions with escalated privileges, making changes to the database during attempts to retabulate the election. They describe this as a major development, because it demonstrates that the machines were accessed remotely, and crucially, that the remote access was by an anonymous user who possessed elevated privileges within the system. They present this as a significant point for those who oppose forensic auditing or who are against non-forensic reviews. They also reference visible features on ballots, specifically the black boxes along the side of the ballot. The ballots reportedly contain 59 of these black boxes. In the forensic images, they indicate that certain blocks—numbers 15, 18, 28, 41, and 44—were intentionally modified. The described modifications concerned the height, width, and overall shape of these blocks, with the stated purpose of generating errors. Regarding the consequences of these modifications, the narrative claims that by altering these specific blocks, errors were created that led to rejections of Republican ballots. In other words, ballots cast for Donald Trump that were processed through the machine allegedly faced a higher likelihood of being rejected due to these block modifications. The asserted outcome is that such ballots were rejected at a rate of 20% more than ballots cast for Joe Biden.

The speaker reviewed server logs and identified "Brian." The speaker found forensics in a database. The speaker shows access and a deletion on the log from the database. The speaker claims Christy previously tweeted about letting Brian into the server. The speaker repeats "Here he is" multiple times. The speaker mentions a law proposal.

The speaker mentions server logs and their own logs, and then reveals that someone named Christie is involved. They state that Christie is not the right driver for the medical situation and imply that it is being discussed online.

The speaker discovered strange documents in a database at work. One document praised Satan and was traced back to a Satanic book. The speaker found it suspicious that only higher-ranking employees could add documents to the database. They also found a document about depopulation, but couldn't determine if it supported or opposed it. The speaker then stumbled upon an address related to the Wuhan lab in China, which had the number 666. They verified this information on Google and took a screenshot. The speaker got in trouble for sharing the screenshot at work.

Internal IBM Slack messages obtained by the speaker reveal discontent towards their reporting. The messages highlight the significance of the story within IBM and its subsidiary, Red Hat. One individual, Brenton Conaboy, suggests that opposition from certain people indicates they are on the right track. Another person, Jay Ryan, blames the speaker for initiating the conversation and expresses a desire to harm individuals online. Chris Galahue, a technical marketing content writer, acknowledges the purpose of the speaker's work and questions whether it should be allowed. The speaker also mentions Matthew Solis, an IT support engineer, who doubts the speaker's credibility but is contradicted by his CEO's confirmation of the events. The speaker claims to possess unedited footage and documents from numerous IBM and Red Hat employees.

The Windows security logs were purged right before two audits were scheduled to begin. This makes it difficult to determine who had access to the RTR admin account, which is shared among all accounts. It is unclear why someone would delete all the records and files from the Dominion software, which is used for tallying and reporting election results, the day before an audit started.

On 2/11, 462 log entries were overwritten by a script. On 3rd March, 37,686 log entries were overwritten by the same script. On 12th, 330 log entries were overwritten. The EMS admin account is responsible for this. The challenge is that this occurred before an audit, which means the full context of the election is not available. The log file shows that someone purged all the results for the election, deleting all records and files. This happened right before the audit started.

On the left is the image before the Dominion employee arrived at the election management server, and on the right is the image after the employee left. The logs folder on the left is missing on the right, indicating that it disappeared after the employee left. Additionally, in the Inetpub log folder, there are multiple log files that contain evidence of connections to the web server. The number of log files is not mentioned.

On various dates, an individual ran a script to search for blank passwords on the system. This script overwrote a significant number of log entries. The EMS admin account was responsible, but it's difficult to prove who specifically executed the script due to the lack of accountability in assigning usernames. Fortunately, historical data from MTech video feeds allowed us to identify individuals at the keyboards during those times. However, we won't disclose their names due to the potential scrutiny and impact on them.

Here's the video everyone is talking about. We’re examining the server logs, and it turns out it’s Brian. We’ll look at a database that enhances our findings. Forensics play a crucial role here, especially with AT&T and the server. I’ll demonstrate the app access and the log deletion process. You all know the history behind this. This is another log we’re reviewing, likely related to daily activities, such as purchasing a truck.

There is a discussion about log files on two screens. One screen shows hundreds of log files from 2019 until May 22, 2021. The other screen only has three years of log files, which have mysteriously disappeared. It is mentioned that when a Dominion employee came in, the log files vanished. These files record all access to a specific machine. It is also mentioned that Dominion sent people around the country for software updates during that time. Some participants confirm this information.

In this video, the speaker talks about checking the server logs and finding something interesting. They discovered a database in their extended logs, which they believe is related to forensics. They mention someone named Christy, who is an active member of the GMC community.