Re:Show HN: Obsidian Canvas – An infinite space for your ideas
by jcul on Wednesday December 21, 2022 @07:34AM
(#34079854)
Small nit: I'd guess it is not that easy to verify this in wireshark.
I'm not an obsidian user or familiar with the code base, so could be wrong here.
The data is probably encrypted with AES before being sent (the E2E bit), though probably there is some metadata unencrypted.
When the data is actually sent, the entire thing would likely be encrypted again with TLS while it is in transit.
This means, for example, your ISP cannot see the unencrypted metadata or the encrypted data.
So if you open a capture in wireshark then you would likely see this. Of course it is possible to decrypt the TLS to check the underlying data is encrypted, but it is not trivial for most people.
An easier way to see what it is doing may be to run strace on it and check what it is writing to the sockets.
Though it would just tell you if the data looks encrypted, not much else.
For example they could use a super secure key, or the "1234" for everyone, just looking at the data probably wouldn't tell you this.
Re:Show HN: Obsidian Canvas – An infinite space for your ideas
by s0ulphire on Wednesday December 21, 2022 @06:18PM
(#34087685)
Sorry that's my bad, I meant *Fiddler not wireshark. Fiddler makes it a piece of cake to decrypt the extra tls, leaving you with just the encrypted data you were sending.
I'm not an obsidian user or familiar with the code base, so could be wrong here.
The data is probably encrypted with AES before being sent (the E2E bit), though probably there is some metadata unencrypted.
When the data is actually sent, the entire thing would likely be encrypted again with TLS while it is in transit. This means, for example, your ISP cannot see the unencrypted metadata or the encrypted data.
So if you open a capture in wireshark then you would likely see this. Of course it is possible to decrypt the TLS to check the underlying data is encrypted, but it is not trivial for most people.
An easier way to see what it is doing may be to run strace on it and check what it is writing to the sockets. Though it would just tell you if the data looks encrypted, not much else.
For example they could use a super secure key, or the "1234" for everyone, just looking at the data probably wouldn't tell you this.