| creation date | tags | |
|---|---|---|
<% tp.file.creation_date() %> |
|
<%* const supportedFileTypes = ["jpeg", "jpg", "png"]; const images = this.app.vault.getFiles().filter((item) => supportedFileTypes.indexOf(item.extension) >= 0); const target = await tp.system.suggester((item) => item.path, images, true); const out = await tp.user.ocr({ocr_input: target.path});
| # set ruby/rails version | |
| export DOCKER_RAILS_VERSION="7.0.1" | |
| export DOCKER_RUBY_VERSION="3.1.0" | |
| export RAILS_PROJECT_NAME="rails7" | |
| # create folder for the project and add Gemfile with necessary rails version | |
| mkdir "$RAILS_PROJECT_NAME" | |
| cd "$RAILS_PROJECT_NAME" | |
| echo "ruby '$DOCKER_RUBY_VERSION' | |
| source 'https://rubygems.org' | |
| gem 'rails', '$DOCKER_RAILS_VERSION'" > Gemfile |
MS Office docx files may contain external OLE Object references as HTML files. There is an HTML sceme "ms-msdt:" which invokes the msdt diagnostic tool, what is capable of executing arbitrary code (specified in parameters).
The result is a terrifying attack vector for getting RCE through opening malicious docx files (without using macros).
Here are the steps to build a Proof-of-Concept docx:
| set -g TMUX_PLUGIN_MANAGER_PATH "$GITHUB_REPO_ROOT" | |
| set -g @plugin 'tmux-plugins/tpm' | |
| set -g @plugin 'wenijinew/glamour.tmux' |
