Mad Bugs: Vim vs. Emacs vs. Claude
blog.calif.io
Mad Bugs: Vim vs. Emacs vs. Claude
1–10 of 51 posts
Re: Mad Bugs: Vim vs. Emacs vs. Claude
#2Re: Mad Bugs: Vim vs. Emacs vs. Claude
#3What does RCE mean?
Basically the worst possible thing.
Re: Mad Bugs: Vim vs. Emacs vs. Claude
#4Lack of accountability.
With other industries, when people aren't happy with their products, they ask for money back, they sue, they switch to the competition.
There are no EULA that assert removal of customer rights if the product is acquired.
Re: Mad Bugs: Vim vs. Emacs vs. Claude
#5> How do we professional bug hunters make sense of this? This feels like the early 2000s. Back then a kid could hack anything, with SQL Injection. Now with Claude. Lack of accountability. With other industries, when people aren't happy with their products, they ask for money back, they sue, they switch to the competition. There are no EULA that assert removal of customer rights if the product is acquired.
Re: Mad Bugs: Vim vs. Emacs vs. Claude
#6Re: Mad Bugs: Vim vs. Emacs vs. Claude
#7What does RCE mean?
It is code execution.
Re: Mad Bugs: Vim vs. Emacs vs. Claude
#8What does RCE mean?
This, however, is mislabelled: it’s not remote code execution at all, only local. It would only become RCE if there was some path to remotely triggering Vim to open the attack file, or Emacs the attack repository, or if a normal way of fetching a repository automatically set up and executed the hook.
Re: Mad Bugs: Vim vs. Emacs vs. Claude
#9I'd be interested to understand what modelines are for, and if this is a class of bug that can be disabled via vim settings. Also, are there editors which could not be affected by this class of bug?
Re: Mad Bugs: Vim vs. Emacs vs. Claude
#10 /* vim: set showtabpanel=2 tabpanel=%{%autocmd_add([{'event'\:'SafeStateAgain','pattern'\:'*','cmd'\:'!id>/tmp/calif-vim-rce-poc','once'\:1}])%}: */