!KuQdMHJRAAsvxzaGnf:grapheneos.org

GrapheneOS Infrastructure

1067 Members
GrapheneOS infrastructure monitoring and discussion. Production status: https://nodeping.com/reports/statusevents/3FL97F6RRQHJIOWL. Join the #community:grapheneos.org space for a list of all the rooms. Formerly known as CopperheadOS. Please avoid discussing CalyxOS in these rooms.100 Servers

Load older messages


SenderMessageTime
16 Apr 2024
@mynacol:mynacol.xyzmynacol
In reply to @miaha:matrix.org
I'm quite familiar with all of the hardening and defense in depth that has been implemented into GrapheneOS, but I haven't found much information on the infrastructure. If I may, what does the GrapheneOS team do to ensure the servers being used by the project are secured and aren't compromised? Is there extensive hardening done on the servers?
The configuration for the servers is also public on GitHub. But the need for trust in the update servers is low, as releases and updates are signed on the developer's machines and validated before install/update. That's also described here: https://grapheneos.org/usage#updates-security
07:14:23
@miaha:matrix.orgMiaha
In reply to @mynacol:mynacol.xyz
The configuration for the servers is also public on GitHub. But the need for trust in the update servers is low, as releases and updates are signed on the developer's machines and validated before install/update. That's also described here: https://grapheneos.org/usage#updates-security
Thanks for the link! I've read almost all of the GrapheneOS documentation and GitHub repos at this point but I somehow missed that detail in the usage section. I was curious how GrapheneOS mitigated potentially malicious code from being built and pushed to all devices, so it's nice knowing that it was already thought of.
07:20:28
@conesnail9321:matrix.orgconesnail9321 joined the room.09:55:56
@cgpatric:matrix.org@cgpatric:matrix.org joined the room.10:54:58
@shadowband:matrix.orgshadowband joined the room.15:47:59
@walfryoff:matrix.orgAnonym M-Trix joined the room.17:21:19
17 Apr 2024
@grapheneosbridge:grapheneos.orgGrapheneOS BridgeRedacted or Malformed Event01:53:33
@alex3829:matrix.orgreal_z2 changed their display name from alex3829 to real_z22.04:36:15
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 3.releases.grapheneos.org HTTPS TLS : SSL is down as of Wed Apr 17 2024 04:59:56 GMT+0000:
Timeout
05:00:00
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 3.releases.grapheneos.org HTTPS TLS : SSL is up after 1 minutes of downtime as of Wed Apr 17 2024 05:01:01 GMT+0000:
Valid cert
05:01:02
@alex3829:matrix.orgreal_z2 changed their display name from real_z22 to real_z2.05:33:45
@grapheneosbridge:grapheneos.orgGrapheneOS BridgeRedacted or Malformed Event18:13:11
@matrix858:matrix.org@matrix858:matrix.org left the room.21:35:58
18 Apr 2024
@tundratoes:matrix.orgtundratos joined the room.04:35:53
17 Apr 2024
@matchboxbananasynergy:arcticfoxes.netmatchboxbananasynergy!! changed their display name from matchboxbananasynergy to matchboxbananasynergy!!.22:15:34
18 Apr 2024
@thedisruptivecollective:matrix.org@thedisruptivecollective:matrix.org changed their profile picture.09:45:59
@thedisruptivecollective:matrix.org@thedisruptivecollective:matrix.org left the room.15:11:15
@itzzen:constellatory.net@itzzen:constellatory.net left the room.12:13:16
@mjolnir:grapheneos.orgGrapheneOS Moderation Bot banned @cgpatric:matrix.org@cgpatric:matrix.org (<no reason supplied>).18:47:50
@tundratoes:matrix.orgtundratos changed their display name from tundratoes to tundratos.21:58:51
19 Apr 2024
@heehee:envs.netheehee (alt) set a profile picture.02:06:56
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 0.ns2.grapheneos.org DNS UDP : DNS is down as of Fri Apr 19 2024 05:37:38 GMT+0000:
Timeout
05:37:42
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 0.ns2.grapheneos.org DNS UDP : DNS is up after 1 minutes of downtime as of Fri Apr 19 2024 05:38:42 GMT+0000:
DNSSEC Authenticated Data
05:38:47
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 0.ns2.grapheneos.org PING IPv4 : PING is down as of Fri Apr 19 2024 05:44:55 GMT+0000:
198.98.53.141
05:44:56
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 0.ns2.grapheneos.org DNS over TLS : DOHDOT is down as of Fri Apr 19 2024 05:44:56 GMT+0000:
Timeout
05:44:56
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 0.ns2.grapheneos.org PING IPv4 : PING is up after 2 minutes of downtime as of Fri Apr 19 2024 05:47:00 GMT+0000:
PING response received
05:47:01
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host 0.ns2.grapheneos.org DNS over TLS : DOHDOT is up after 2 minutes of downtime as of Fri Apr 19 2024 05:47:01 GMT+0000:
DNS response matched
05:47:02
@admin:grapheneos.orgadmin0.ns2.grapheneos.org was likely impacted by a DDoS attack against the provider based on the symptoms05:48:40
@admin:grapheneos.orgadminseems to be over05:48:44
@grapheneosbridge:grapheneos.orgGrapheneOS BridgeRedacted or Malformed Event15:11:14

There are no newer messages yet.


Back to Room ListRoom Version: 10