!KuQdMHJRAAsvxzaGnf:grapheneos.org

GrapheneOS Infrastructure

1070 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.101 Servers

Load older messages


SenderMessageTime
13 Apr 2024
@dean.undiluted:matrix.orgdean.undiluted joined the room.19:30:29
@nmking:beeper.com@nmking:beeper.com left the room.22:40:32
14 Apr 2024
@sfo19:matrix.org@sfo19:matrix.org left the room.03:06:51
@asjdkfldsdks:matrix.org@asjdkfldsdks:matrix.org joined the room.06:05:39
@asjdkfldsdks:matrix.org@asjdkfldsdks:matrix.org left the room.06:05:43
@superjulian:matrix.org@superjulian:matrix.org joined the room.13:02:10
@superjulian:matrix.org@superjulian:matrix.org left the room.13:02:21
@wonderfall:lysergide.devWonderfall changed their profile picture.14:22:15
@noobineer:matrix.orgnoobineer joined the room.22:15:24
@tioluigi:matrix.org@tioluigi:matrix.org joined the room.23:36:41
@tioluigi:matrix.org@tioluigi:matrix.org left the room.23:37:11
15 Apr 2024
@itzzen:constellatory.netallissa is tired | 🇵🇸 changed their display name from allissa the silly | 🇵🇸 to allissa is tired | 🇵🇸.03:52:21
@aaam:matrix.orgaaam joined the room.07:26:35
@lh:armadix.netlh joined the room.09:28:26
@graticule:matrix.orgArchie changed their display name from Archie (away until 15/4) to Archie.09:33:39
@cavard:matrix.orgcav changed their profile picture.15:29:14
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host mail.grapheneos.org SMTP STARTTLS worldwide : SMTP is down as of Mon Apr 15 2024 17:18:39 GMT+0000:
null
17:18:39
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host mail.grapheneos.org SMTP STARTTLS : SMTP is down as of Mon Apr 15 2024 17:18:45 GMT+0000:
null
17:18:45
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host mail.grapheneos.org SMTP STARTTLS worldwide : SMTP is up after 3 minutes of downtime as of Mon Apr 15 2024 17:21:56 GMT+0000:
STARTTLS connected
17:21:57
@grapheneosbridge:grapheneos.orgGrapheneOS Bridge <NodePing:discord> Host mail.grapheneos.org SMTP STARTTLS : SMTP is up after 3 minutes of downtime as of Mon Apr 15 2024 17:21:59 GMT+0000:
STARTTLS connected
17:22:00
16 Apr 2024
@clxud:matrix.orgClxud changed their profile picture.01:28:15
@clxud:matrix.orgClxud changed their profile picture.01:28:36
@clxud:matrix.orgClxud changed their profile picture.01:28:42
@miaha:matrix.orgMiahaI'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?06:24:34
@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.orgcgpatric 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

There are no newer messages yet.


Back to Room ListRoom Version: 10