rikka0w0

The Digilent JTag uses FT2232, but its configuration EEPROM contains secrete data needed to be recoginzed by Xilinx ISE/Vivado. The following method only works on linux (tested on Ubuntu16.04), but the patched FT2232 doggle also works on Windows. Since WSL1 does not provide USB device access, the following method will not work for WSL1.

DONT use FT_Prog on offical Digilent cable, as it can trash the firmware! The offical eeprom contains secrete data that cannot be handled correctly by FT_Prog.

Here are steps to create a Digilent-like Jtag that can be used in Xilinx ISE and Vivado

1. Install softwares: sudo apt-get install libftdi1 ftdi-eeprom
2. Create a file "flash_digilent.conf" with the following content:

vimtaai

Comparison of syntax extensions in Markdown flavors

I created a crude comparison of the syntax of the various common Markdown extensions to have a better view on what are the most common extensions and what is the most widely accepted syntax for them. The list of Markdown flavors that I looked at was based on the list found on CommonMark's GitHub Wiki.

Flavor	Superscript	Subscript	Deletion* Strikethrough	Insertion*	Highlight*	Footnote	Task list	Table	Abbr	Deflist	Smart typo	TOC	Math	Math Block	Mermaid
GFM

markasoftware

############ If you are using DOCKER all-in-one image, create Dockerfile like:         ################
############ FROM openproject/openproject:16                                           ################
############ COPY ./enterprise_token.rb app/models/enterprise_token.rb                 ################

############ If you are runing a manual installation:                                  ################
############ REPLACE app/models/enterprise_token.rb in the source code with this file! ################
############ also be sure to RESTART OpenProject after replacing the file.             ################

############ If using some other set up (eg docker-compose), read the comments on      ################
############ https://gist.github.com/markasoftware/f5b2e55a2c2e3abb1f9eefcdf0bfff45    ################

thesamesam

FAQ on the xz-utils backdoor (CVE-2024-3094)

This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.

Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.

Background