Hacker Newsnew | past | comments | ask | show | jobs | submit | kernc's commentslogin

No.1: Run untrusted code in a sandbox! https://github.com/sandbox-utils/sandbox-venv

Now that everyone is kindly on board, IBM can finally bury this standard. /s

What are the reasons for Snapchat? :.


Ladies


If you're above 25 (if not 20), Snapchat should be the last place to search for ladies...


I(1992) keep it because my younger family members(Gen Z>) refuse to use anything else to communicate.


You have my condolences


What's wrong with dating 20 -25 yr olds? LOL (central europe, millenial)


Honestly above 18-


Does not compute


> alias npm=...

I use sandbox-run: https://github.com/sandbox-utils/sandbox-run

The above simple alias may work for node/npm, but it doesn't generalize to many other programs available on the local system, with resources that would need to be mounted into the container ...


> The above simple alias may work for node/npm, but it doesn't generalize for many other programs that are available on the local system, with resources that would somehow have to get mounted into the container ...

Thanks. You are right, running inside Docker won't always work for local commands. But I am not even using local commands.

Infact, I have removed `yarn`, `npm`, and several similar tools already from my machine.

It is best to run them inside Docker.

> I use sandbox-run: https://github.com/sandbox-utils/sandbox-run

How does this work if my local command is a Mac OS binary? How will it run inside Docker container?


Or use ‘chroot’. Or run it as a restricted owner with ‘chown’. Your grandparents solutions to these problems still work.


That'll still allow access to env vars, and interact with other processes owned by the same user.

At the very least, you really need to add process isolation / namespacing as well - at which point it's going to be easier to just use the sandboxing / containerisation tool of your choice to manage it all for you.


Local-first (on Lunix), POSIX shell: https://github.com/sandbox-utils/sandbox-run


Thanks for sharing, adding it to my list.


A simple zero-config alternative using Linux-native containers seems to be sandbox-venv [1] for Python and sandbox-run [2] for npm ...

[1]: https://github.com/sandbox-utils/sandbox-venv [2]: https://github.com/sandbox-utils/sandbox-run


> This might be a red flag for Persona service itself as it might contain serious flaws and security vulnerabilities that Cyber criminals are relying on

Persona seems to rely solely on NFC with a national passport/ID, so simply stolen documents would work for a certain duration ...


You can use special a Unicode strikethrough glyphs such as available in https://efck-chat-keyboard.github.io


Is exactly why I composed bubblewrap-based sandbox-venv for Python: https://github.com/kernc/sandbox-venv

Dangerous times we live in.


Too personal to share, but maybe too personal and important to share even with the members of the cloudy cartel, i.e. the Providers. Is exactly why I wrote myba that does full contents and paths encryption before syncing with the lapsable remotes ...

https://kernc.github.io/myba/

Some things are better public. Some are not ...


That looks nice!

The moment I started syncing dotfiles between my work and personal computers, I know it was an error because very different reasons. Difficulty of maintaining different OS details (Linux vs MacOS). What if leaked a private key or a sensible path. What if a pushed to the wrong place or somebody made public the wrong repository...

When reading your comment something and idea came to mind about using something like sops to encrypt paths, passwords and keys. But I'll check yours first, so to avoid to construct a bunch of stuff that you've already done :D


I am trying to contextualize git-based dotfiles.

  $ context set universe://work/customer-a/devops --update-dotfiles
will "render" and apply one set of dotfiles

  $ context set unvierse://work/customer-b --update-dotfiles
another set

  $ canvas dot apply user.name@remote.id:workspace-foo
Will apply all dotfiles of a workspace-foo (git clone repo, symlink)

  $ canvas dot apply user.name@remote.id:workspace-bar/shell/bashrc
will apply dotfiles of workspace-bar/shell/bashrc

yes, complicated, probably hard to comprehend/reason about, work in progress


I can no longer edit my original dot manager comment so to add some context: I developed an allergy for the term "vibe-coding" (and made a joke on the selection of OPs words), AI won't turn a lazy unskilled inexperienced person into John Carmack, lazy person + AI still equals to a lazy person. With that being said, most of you may have already experienced a divide between the above empirical truth and management decisions across your favorite corporate environments. So, the race is on, AGI-level agentic frameworks may be here soon enough to mitigate the above, then again, in the end isnt the enduser of most of our economic production directly or indirectly a human? Can a synthetic immortal system really cater for human needs? There is a reason why big deals are always negotiated in-person


this reminds me of public repos of pass [1] i've seen in the wild

same issue of intimacy, the paths aren't encrypted.

[1] https://www.passwordstore.org/


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: