[HN Gopher] Show HN: Visualenv: store env variables in image
___________________________________________________________________
Show HN: Visualenv: store env variables in image
Store env variables securely in images using steganography
Author : ersinesen
Score : 11 points
Date : 2024-09-30 09:13 UTC (2 days ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| nixosbestos wrote:
| I've read _all_ of the code in this repo, including the README,
| and have no idea what it does or why it needs to be communicating
| to a third party server. EDIT: And Octomim, the "secure" server
| that is somehow essential to this stego app, is written in C. :/
|
| AFAICT this looks like "secure storing data on a third party
| server, with a username and password, with a tiny identifier
| token stored in an image". Which, like, why?
| theamk wrote:
| I am not sure what server does, but for that repo to work,
| server does not even need any steganography, as the it has a
| database.
|
| On "create", it picks a random image, hashes it and stores
| (user-id, secret, text) in database
|
| On "extract", it's opposite - accept image, hash, fetch from
| db.
|
| All the API calls would work just the same, no cryptography of
| any kind needed.
| dumpsterdiver wrote:
| It's not even clear if images are involved at all since the
| only knowledge of such to the client is a filename returned
| from the create endpoint.
|
| If the only knowledge of that image by the client is the
| filename, why would:
|
| A) The client care about images at all? At that point you could
| send the name of your grandma and conceivably get back the same
| data.
|
| B) The host spend more compute performing steganographic
| operations when they already have the unique identifier they
| require?
| mdni007 wrote:
| Why is this on the front page of HN?
| throwaway314155 wrote:
| Because people upvote titles not content.
___________________________________________________________________
(page generated 2024-10-02 23:01 UTC)