4 ms·

I wonder what would happen if you searched for .svn, too. I'm sure you'd run into the same problem in many places. But would it be more or less likely to occur?

kijin 11y ago
In svn's heyday, the standard way to install or update a popular app like WordPress was to download and extract a tarball. Only people who actually participated in the development of the app itself used svn. Nowadays, lots of open-source projects encourage ordinary webmasters to clone a Github repo and run `git pull` to update. So I suspect that public .svn folders will be less common.
- ams6110 11y ago
  That's problematic in itself. "git" has no business being installed on your public-facing web server. Nor should there be any compilers installed, nor any scripting languages not explicitly needed, etc. etc.
viraptor 11y ago
I think less likely. Svn actually had an `export` command, which allowed you to do a checkout of a specific commit with no svn metadata. If someone was actually using svn for deployment, they likely knew about it. (http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.export.html http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.export.html)
- matt_kantor 11y ago
  git has `archive`, which is essentially the same thing. [1]: http://git-scm.com/docs/git-archive http://git-scm.com/docs/git-archive
  - viraptor 11y ago
    No, archive is very different. `svn export` could be used at the target side. Basically you can export from remote repository to the chosen directory without any extra operations, so .svn is never created. `git archive` requires you to have a clone of the repo from which you can create an archive. That means people are more likely to just do a local checkout than play with archive on top of it. Deploy with svn export: svn export url.of.repo destination/path Deploy with git archive: git clone url.of.repo cd repo_name git archive --format=tar some_commit_or_branch | (cd destination/path && tar -xf -)
    - nraynaud 11y ago
      I completely agree, every time I do a new deployment script for git, I miss the old svn export command, I hate the idea of cloning on the deployment machine, having to git sync in the script etc. Whereas 'svn export' feels stateless, and is clean by construction.
kilotaras 11y ago
https://news.ycombinator.com/item?id=838981 https://news.ycombinator.com/item?id=838981 - similar breach was reported in 2009. It focused on .ru part of internet and got a bunch of big names.

kijin 11y ago

In svn's heyday, the standard way to install or update a popular app like WordPress was to download and extract a tarball. Only people who actually participated in the development of the app itself used svn. Nowadays, lots of open-source projects encourage ordinary webmasters to clone a Github repo and run `git pull` to update. So I suspect that public .svn folders will be less common.

ams6110 11y ago
That's problematic in itself. "git" has no business being installed on your public-facing web server. Nor should there be any compilers installed, nor any scripting languages not explicitly needed, etc. etc.

viraptor 11y ago

I think less likely. Svn actually had an `export` command, which allowed you to do a checkout of a specific commit with no svn metadata. If someone was actually using svn for deployment, they likely knew about it. (http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.export.html http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.export.html)

matt_kantor 11y ago
git has `archive`, which is essentially the same thing. [1]: http://git-scm.com/docs/git-archive http://git-scm.com/docs/git-archive
- viraptor 11y ago
  No, archive is very different. `svn export` could be used at the target side. Basically you can export from remote repository to the chosen directory without any extra operations, so .svn is never created. `git archive` requires you to have a clone of the repo from which you can create an archive. That means people are more likely to just do a local checkout than play with archive on top of it. Deploy with svn export: svn export url.of.repo destination/path Deploy with git archive: git clone url.of.repo cd repo_name git archive --format=tar some_commit_or_branch | (cd destination/path && tar -xf -)
  - nraynaud 11y ago
    I completely agree, every time I do a new deployment script for git, I miss the old svn export command, I hate the idea of cloning on the deployment machine, having to git sync in the script etc. Whereas 'svn export' feels stateless, and is clean by construction.

kilotaras 11y ago

https://news.ycombinator.com/item?id=838981 https://news.ycombinator.com/item?id=838981 - similar breach was reported in 2009. It focused on .ru part of internet and got a bunch of big names.