Custom Agenda Commands #135
Labels
core-feature
Feature is in orgmode core
Comments
|
Just an update; I am rather busy over the holidays, but plan to work on this when back. |
|
@kristijanhusak I have some iterations of this locally, e.g. filtering items in a scope similar to
A decent amount of the functionality here would either be something that is part of Curious on your thoughts. |
|
@levouh looks interesting. Can you make a draft PR? Ideally most of the functionality would be "internal", and we would expose only certain functionality through the API. I don't want to put too many things in the API because I consider that for public usage, which should not introduce any breaking changes ever. We can elaborate more on the draft PR. |
|
@levouh any news on this? Your progress so far looks very enticing :) |
lyz-code
added a commit
to lyz-code/blue-book
that referenced
this issue
Nov 27, 2024
As they have introduced pricing, which makes no sense, and we had a discussion that using that badge it's a nice way to tell the AI which content to use and which not to feat(android_sdk): introduce android_sdk [Android SDK Platform tools](https://developer.android.com/tools/releases/platform-tools) is a component for the Android SDK. It includes tools that interface with the Android platform, primarily adb and fastboot. **[Installation](https://developer.android.com/tools/releases/platform-tools)** While many Linux distributions already package Android Platform Tools (for example `android-platform-tools-base` on Debian), it is preferable to install the most recent version from the official website. Packaged versions might be outdated and incompatible with most recent Android handsets. - Download [the latest toolset](https://dl.google.com/android/repository/platform-tools-latest-linux.zip) - Extract it somewhere in your filesystem - Create links to the programs you want to use in your `$PATH` Next you will need to enable debugging on the Android device you are testing. [Please follow the official instructions on how to do so.](https://developer.android.com/studio/command-line/adb) **Usage** **Connecting over USB** To use `adb` with a device connected over USB, you must enable USB debugging in the device system settings, under Developer options. On Android 4.2 (API level 17) and higher, the Developer options screen is hidden by default. *Enable the Developer options* To make it visible, [enable Developer options](https://developer.android.com/studio/debug/dev-options#enable). On Android 4.1 and lower, the Developer options screen is available by default. On Android 4.2 and higher, you must enable this screen. - On your device, find the Build number option (Settings > About phone > Build number) - Tap the Build Number option seven times until you see the message You are now a developer! This enables developer options on your device. - Return to the previous screen to find Developer options at the bottom. *Enable USB debugging* Before you can use the debugger and other tools, you need to enable USB debugging, which allows Android Studio and other SDK tools to recognize your device when connected via USB. Enable USB debugging in the device system settings under Developer options. You can find this option in one of the following locations, depending on your Android version: - Android 9 (API level 28) and higher: Settings > System > Advanced > Developer Options > USB debugging - Android 8.0.0 (API level 26) and Android 8.1.0 (API level 27): Settings > System > Developer Options > USB debugging - Android 7.1 (API level 25) and lower: Settings > Developer Options > USB debugging *Test it works* If everything is configured appropriately you should see your device when launching the command `adb devices`. *Create udev rules if it fails* If you see the next error: ``` failed to open device: Access denied (insufficient permissions) * failed to start daemon adb: failed to check server version: cannot connect to daemon ``` It indicates an issue with permissions when `adb` tries to communicate with the device via USB. Here are some steps you can take to resolve this issue: - Check USB permissions - Ensure that you have the necessary permissions to access the USB device. If you're running on Linux, check if the device has appropriate udev rules. - You can try adding your user to the `plugdev` group: ```bash sudo usermod -aG plugdev $USER ``` - Make sure you have a `udev` rule for Android devices in `/etc/udev/rules.d/`. If not, you can create one by adding a file like `51-android.rules`: ```bash sudo touch /etc/udev/rules.d/51-android.rules ``` - Add this line to the file to grant access to Android devices: ```bash SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev" ``` - Reload the `udev` rules: ```bash sudo udevadm control --reload-rules sudo service udev restart ``` - Unplug and reconnect the USB device. **References** - [Home](https://developer.android.com/tools/releases/platform-tools) feat(antitourism#artículos): Nuevo artículo contra el turismo - [Abolir el turismo - Escuela de las periferias](https://www.elsaltodiario.com/turismo/abolir-turismo): Lleguemos a donde lleguemos, no puede ser que sea más fácil imaginar el fin del capitalismo que el fin del turismo. feat(himalaya#Configure navigation bindings): Configure navigation bindings The default bindings conflict with my git bindings, and to make them similar to orgmode agenda I'm changing the next and previous page: ```lua return { { "pimalaya/himalaya-vim", keys = { { "b", "<plug>(himalaya-folder-select-previous-page)", desc = "Go to the previous email page" }, { "f", "<plug>(himalaya-folder-select-next-page)", desc = "Go to the next email page" }, }, }, } ``` fix(himalaya#Configure the account bindings): Configure the account bindings ### Configure the account bindings - In the email write view: - `q` or `<c-s>`: Save and send the email If you want them too set the next config: ```lua -- get the current buffer's full file path local filepath = vim.api.nvim_buf_get_name(0) -- bind `q` and `<c-s>` to close the window if string.match(filepath, "write") then vim.api.nvim_buf_set_keymap(0, "n", "<c-s>", ":w<cr>:bd<cr>", { noremap = true, silent = true }) vim.api.nvim_buf_set_keymap(0, "n", "q", ":w<cr>:bd<cr>", { noremap = true, silent = true }) else -- in read mode you can't save the buffer vim.api.nvim_buf_set_keymap(0, "n", "q", ":bd<cr>", { noremap = true, silent = true }) end ``` fix(himalaya): Refresh the active account ```lua keys = { -- Email refreshing bindings { "<leader>r", ":lua FetchEmails()<CR>", desc = "Fetch emails" }, }, config = function() function FetchEmails() local account = vim.api.nvim_eval("himalaya#domain#account#current()") vim.notify("Fetching emails for " .. account .. ", please wait...", vim.log.levels.INFO) vim.cmd("redraw") -- Start the mbsync job vim.fn.jobstart("mbsync " .. account, { on_exit = function(_, exit_code, _) if exit_code == 0 then vim.notify("Emails for " .. account .. " fetched successfully!", vim.log.levels.INFO) -- Reload Himalaya only after successful mbsync vim.cmd("Himalaya " .. account) else vim.notify("Failed to fetch emails for " .. account .. ". Check the logs.", vim.log.levels.ERROR) end ``` fix(himalaya#Emails are shown with different timezones): Emails are shown with different timezones Set the account configuration `envelope.list.datetime-local-tz = true` fix(himalaya#Emails are not being copied to Sent ): Emails are not being copied to Sent Set the account configuration `message.send.save-copy = true` feat(linux_snippets#How to debug a CPU Throttling high alert): How to debug a CPU Throttling high alert It may be because it has hit a limit set by kubernetes or docker. If the metrics don't show that it may be because the machine has run out of CPU credits. feat(mobile_verification_toolkit): Introduce mobile verification toolkit [Mobile Verification Toolkit](https://github.com/mvt-project/mvt) (MVT) is a collection of utilities to simplify and automate the process of gathering forensic traces helpful to identify a potential compromise of Android and iOS devices. MVT's capabilities are continuously evolving, but some of its key features include: - Decrypt encrypted iOS backups. - Process and parse records from numerous iOS system and apps databases, logs and system analytics. - Extract installed applications from Android devices. - Extract diagnostic information from Android devices through the adb protocol. - Compare extracted records to a provided list of malicious indicators in STIX2 format. - Generate JSON logs of extracted records, and separate JSON logs of all detected malicious traces. - Generate a unified chronological timeline of extracted records, along with a timeline all detected malicious traces. MVT is a forensic research tool intended for technologists and investigators. Using it requires understanding the basics of forensic analysis and using command-line tools. MVT is not intended for end-user self-assessment. If you are concerned with the security of your device please seek expert assistance. It has been developed and released by the Amnesty International Security Lab in July 2021 in the context of the Pegasus Project along with a technical forensic methodology. It continues to be maintained by Amnesty International and other contributors. MVT supports using public indicators of compromise (IOCs) to scan mobile devices for potential traces of targeting or infection by known spyware campaigns. **Warning** Public indicators of compromise are insufficient to determine that a device is "clean", and not targeted with a particular spyware tool. Reliance on public indicators alone can miss recent forensic traces and give a false sense of security. Reliable and comprehensive digital forensic support and triage requires access to non-public indicators, research and threat intelligence. Such support is available to civil society through [Amnesty International's Security Lab](https://securitylab.amnesty.org/get-help/?c=mvt_docs) or through their forensic partnership with [Access Now’s Digital Security Helpline](https://www.accessnow.org/help/). **How it works** *[Indicators of compromise](https://docs.mvt.re/en/latest/iocs/)* MVT uses [Structured Threat Information Expression (STIX)](https://oasis-open.github.io/cti-documentation/stix/intro.html) files to identify potential traces of compromise. These indicators of compromise are contained in a file with a particular structure of [JSON](https://en.wikipedia.org/wiki/JSON) with the `.stix2` or `.json` extensions. *STIX2 Support* So far MVT implements only a subset of [STIX2 specifications](https://docs.oasis-open.org/cti/stix/v2.1/csprd01/stix-v2.1-csprd01.html): * It only supports checks for one value (such as `[domain-name:value='DOMAIN']`) and not boolean expressions over multiple comparisons * It only supports the following types: `domain-name:value`, `process:name`, `email-addr:value`, `file:name`, `file:path`, `file:hashes.md5`, `file:hashes.sha1`, `file:hashes.sha256`, `app:id`, `configuration-profile:id`, `android-property:name`, `url:value` (but each type will only be checked by a module if it is relevant to the type of data obtained) *Known repositories of STIX2 IOCs* - The [Amnesty International investigations repository](https://github.com/AmnestyTech/investigations) contains STIX-formatted IOCs for: - [Pegasus](https://en.wikipedia.org/wiki/Pegasus_(spyware)) ([STIX2](https://raw.githubusercontent.com/AmnestyTech/investigations/master/2021-07-18_nso/pegasus.stix2)) - [Predator from Cytrox](https://citizenlab.ca/2021/12/pegasus-vs-predator-dissidents-doubly-infected-iphone-reveals-cytrox-mercenary-spyware/) ([STIX2](https://raw.githubusercontent.com/AmnestyTech/investigations/master/2021-12-16_cytrox/cytrox.stix2)) - [An Android Spyware Campaign Linked to a Mercenary Company](https://github.com/AmnestyTech/investigations/tree/master/2023-03-29_android_campaign) ([STIX2](https://github.com/AmnestyTech/investigations/blob/master/2023-03-29_android_campaign/malware.stix2)) - [This repository](https://github.com/Te-k/stalkerware-indicators) contains IOCs for Android stalkerware including [a STIX MVT-compatible file](https://raw.githubusercontent.com/Te-k/stalkerware-indicators/master/generated/stalkerware.stix2). - They are also maintaining [a list of IOCs](https://github.com/mvt-project/mvt-indicators) in STIX format from public spyware campaigns. You can automatically download the latest public indicator files with the command `mvt-ios download-iocs` or `mvt-android download-iocs`. These commands download the list of indicators from the [mvt-indicators](https://github.com/mvt-project/mvt-indicators/blob/main/indicators.yaml) repository and store them in the [appdir](https://pypi.org/project/appdirs/) folder. They are then loaded automatically by MVT. Please [open an issue](https://github.com/mvt-project/mvt/issues/) to suggest new sources of STIX-formatted IOCs. **[Consensual Forensics](https://docs.mvt.re/en/latest/introduction/)** While MVT is capable of extracting and processing various types of very personal records typically found on a mobile phone (such as calls history, SMS and WhatsApp messages, etc.), this is intended to help identify potential attack vectors such as malicious SMS messages leading to exploitation. MVT's purpose is not to facilitate adversarial forensics of non-consenting individuals' devices. The use of MVT and derivative products to extract and/or analyse data originating from devices used by individuals not consenting to the procedure is explicitly prohibited in the [license](license.md). **[Installation](https://docs.mvt.re/en/latest/install/)** **[Using docker](https://docs.mvt.re/en/latest/docker/)** **Not using docker** Before proceeding, please note that MVT requires Python 3.6+ to run. While it should be available on most operating systems, please make sure of that before proceeding. *Dependencies on Linux* First install some basic dependencies that will be necessary to build all required tools: ```bash sudo apt install python3 python3-venv python3-pip sqlite3 libusb-1.0-0 ``` `libusb-1.0-0` is not required if you intend to only use `mvt-ios` and not `mvt-android`. (Recommended) Set up `pipx` For Ubuntu 23.04 or above: ```bash sudo apt install pipx pipx ensurepath ``` For Ubuntu 22.04 or below: ``` python3 -m pip install --user pipx python3 -m pipx ensurepath ``` Other distributions: check for a `pipx` or `python-pipx` via your package manager. When working with Android devices you should additionally install [Android SDK Platform Tools](https://developer.android.com/studio/releases/platform-tools). If you prefer to install a package made available by your distribution of choice, please make sure the version is recent to ensure compatibility with modern Android devices. *Installing ADB* Follow the steps of [android_sdk.md#installation]. *Installing MVT* 1. Install `pipx` following the instructions above for your OS/distribution. Make sure to run `pipx ensurepath` and open a new terminal window. 2. ```bash pipx install mvt ``` You now should have the `mvt-ios` and `mvt-android` utilities installed. If you run into problems with these commands not being found, ensure you have run `pipx ensurepath` and opened a new terminal window. **Usage** **Download the indicators** If you want to check android: ```bash mvt-android download-iocs ``` If you want to check ios: ```bash mvt-ios download-iocs ``` **[Checking an Android mobile](https://docs.mvt.re/en/latest/android/methodology/)** Unfortunately Android devices provide much less observability than their iOS cousins. Android stores very little diagnostic information useful to triage potential compromises, and because of this `mvt-android` capabilities are limited as well. However, not all is lost. First [make sure `adb` works fine](android_sdk.md#connecting-over-usb). Then you can run: ```bash mvt-android check-adb --output . ``` **Check installed Apps** Because malware attacks over Android typically take the form of malicious or backdoored apps, the very first thing you might want to do is to extract and verify all installed Android packages and triage quickly if there are any which stand out as malicious or which might be atypical. While it is out of the scope of this documentation to dwell into details on how to analyze Android apps, MVT does allow to easily and automatically extract information about installed apps, download copies of them, and quickly look them up on services such as [VirusTotal](https://www.virustotal.com). You can [download all the apks](https://docs.mvt.re/en/latest/android/download_apks/) with the next command: ```bash mvt-android download-apks --output /path/to/folder ``` MVT will likely warn you it was unable to download certain installed packages. There is no reason to be alarmed: this is typically expected behavior when MVT attempts to download a system package it has no privileges to access. *Upload apks to VirusTotal* Be warned thought that each apk you upload to VirusTotal can be downloaded by any VirusTotal user, so if you have private apps that may have confidential information stored in the apk you should not use the upload to VirusTotal feature. !!! info "Using VirusTotal" Please note that in order to use VirusTotal lookups you are required to provide your own API key through the `MVT_VT_API_KEY` environment variable. You should also note that VirusTotal enforces strict API usage. Be mindful that MVT might consume your hourly search quota. *Register in VirusTotal* You can register a new account [here](https://www.virustotal.com/gui/join-us). Then get your key from [here](https://www.virustotal.com/gui/my-apikey). The standard free end-user account. It is not tied to any corporate group and so it does not have access to Premium services. You are subjected to the following limitations: - Request rate: 4 lookups / min - Daily quota:500 lookups / day - Monthly quota: 15.5 K lookups / month I've tried to find the [pricing](https://docs.virustotal.com/docs/difference-public-private#price) but got nowhere. Maybe the default limits are enough **Check the device over Android Debug Bridge** Some additional diagnostic information can be extracted from the phone using the [Android Debug Bridge (adb)](https://developer.android.com/studio/command-line/adb). `mvt-android` allows to automatically extract information including [dumpsys](https://developer.android.com/studio/command-line/dumpsys) results, details on installed packages (without download), running processes, presence of root binaries and packages, and more. **[Work with the indicators of compromise](https://docs.mvt.re/en/latest/iocs/)** You can indicate a path to a STIX2 indicators file when checking iPhone backups or filesystem dumps. For example: ```bash mvt-ios check-backup --iocs ~/ios/malware.stix2 --output /path/to/iphone/output /path/to/backup ``` Or, with data from an Android backup: ```bash mvt-android check-backup --iocs ~/iocs/malware.stix2 /path/to/android/backup/ ``` After extracting forensics data from a device, you are also able to compare it with any STIX2 file you indicate: ```bash mvt-ios check-iocs --iocs ~/iocs/malware.stix2 /path/to/iphone/output/ ``` The `--iocs` option can be invoked multiple times to let MVT import multiple STIX2 files at once. For example: ```bash mvt-ios check-backup --iocs ~/iocs/malware1.stix --iocs ~/iocs/malware2.stix2 /path/to/backup ``` It is also possible to load STIX2 files automatically from the environment variable `MVT_STIX2`: ```bash export MVT_STIX2="/home/user/IOC1.stix2:/home/user/IOC2.stix2" ``` **Troubleshooting** **Suspicious org.thoughtcrime.securesms in trace logs** It's the signal app. **Seeing applications of other profiles** `adb` is able to extract the applications of other profiles, so it's able to analyse them. That's why you may see receivers (monitoring telephony state/incoming calls or to intercept incoming SMS messages) in the logs, as the program checks signatures on those apps. **References** - [Source](https://github.com/mvt-project/mvt) - [Docs](https://docs.mvt.re/en/latest/) feat(orgmode#Custom agendas): Custom agendas There is still no easy way to define your [custom agenda views](https://orgmode.org/manual/Custom-Agenda-Views.html), but it looks possible [1](nvim-orgmode/orgmode#478) and [2](nvim-orgmode/orgmode#135). I've made an [ugly fix](nvim-orgmode/orgmode#831) to be able to use it with the `tags` agenda. Until it's solved you can use [my fork](https://github.com/lyz-code/orgmode). To define your custom agenda you can set for example: ```Lua keys = { { "<leader>gt", function() require("orgmode.api.agenda").tags({ query = "+today/-INACTIVE-DONE-REJECTED", todo_only = true, }) end, desc = "Open orgmode agenda for today", }, } ``` feat(orgmode): Trigger capture outside vim If you're outside vim you can trigger the capture (if you're using i3) by adding this config: ```bash for_window [title="Capture"] floating enable, resize set 50 ppt 30 ppt bindsym $mod+c exec PATH="$PATH:/home/lyz/.local/bin" kitty --title Capture nvim +"lua require('orgmode').action('capture.prompt')" ``` By pressing `alt+c` a floating terminal will open with the capture template. feat(orgmode#Clocking): Clocking There is partial support for [Clocking work time](https://orgmode.org/manual/Clocking-Work-Time.html). I've changed the default bindings to make them more comfortable: ```lua mappings = { org = { org_clock_in = "<leader>ci", org_clock_out = "<leader>co", org_clock_cancel = "<leader>cx", org_clock_goto = "<leader>cj", }, agenda = { org_agenda_clock_in = "i", org_agenda_clock_out = "o", org_agenda_clock_cancel = "x", org_agenda_clock_goto = "<leader>cj", }, ``` In theory you can use the key `R` in any agenda to report the time, although I still find it kind of buggy. feat(orgzly#All files give conflicts when nothing has changed): All files give conflicts when nothing has changed Thinks broke bad, so I exported and sent the files I knew had changed since it broke and then I cleared the orgzly by: - Removing the repositories connection (Settings / Sync / Repositories): Hard press (copy the path) and then remove - Removing the database (Settings / Application / Clean local database) - Restarting the app - Adding again the repository - Do a sync feat(rabbitmq): Introduce Rabbitmq [Rabbitmq](https://www.rabbitmq.com/) is a reliable and mature messaging and streaming broker, which is easy to deploy on cloud environments, on-premises, and on your local machine. **Check that it's working** If RabbitMQ's Management Plugin is enabled, you can use a browser or curl to check the status of the server: ```bash curl -i http://<rabbitmq-host>:15672/api/overview ``` Replace `<rabbitmq-host>` with your RabbitMQ server’s hostname or IP address. The default port for the management interface is 15672. You might need to provide credentials if the management plugin requires authentication: ```bash curl -i -u guest:guest http://<rabbitmq-host>:15672/api/overview ``` If successful, you will get a JSON response with information about the server. **References** - [Home](https://www.rabbitmq.com/) fix(vim_plugin_development#Neovim plugin debug): Neovim plugin debug If you use `lazy` your plugins will be installed in `~/.local/share/nvim/lazy/pack/packer/start/`. You can manually edit those files to develop new feature or fix issues on the plugins. fix(vim_plugin_development#Debugging using Snacks): Debugging using Snacks Utility functions you can use in your code. Personally, I have the code below at the top of my `init.lua`: ```lua _G.dd = function(...) Snacks.debug.inspect(...) end _G.bt = function() Snacks.debug.backtrace() end vim.print = _G.dd ``` What this does: - Add a global `dd(...)` you can use anywhere to quickly show a notification with a pretty printed dump of the object(s) with lua treesitter highlighting - Add a global `bt()` to show a notification with a pretty backtrace. - Override Neovim's `vim.print`, which is also used by `:= {something = 123}` 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does this feature exist in Emacs orgmode core?
Yes
Orgmode link
https://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.html
Feature value
General customization of the agenda view & supporting more features from Emacs Orgmode
Additional context
See #128, additional context will be added here and in an associated PR when we get there 😉
The text was updated successfully, but these errors were encountered: