adulau

If you're looking for a Redis-compatible key-value store, kvrocks[1][2] is an excellent choice. We've used it in many projects, and it's proven to be very stable. Since it's based on RocksDB, it doesn't have the memory limitations of Redis and the license delirium ;-)

[1] https://kvrocks.apache.org/ [2] https://github.com/apache/kvrocks

onion-lookup is a service for checking the existence of Tor hidden services and retrieving their associated metadata.

The most important part is "The people who did not use a phone before bed had the highest quality of sleep."

I recall Gitorious, which isn't mentioned in this article. It was acquired by GitLab, which subsequently discontinued it in 2015. The standout feature has always been the social aspect and the ability to attract a large user base to a git forge. If platforms like Codeberg or similar forges enhance their social integration and capabilities, they could eventually become strong competitors to GitHub.

That's great for analyzing or reviewing the code. However, beyond that, there's not much else you can do with this code.

   This repository is not provided with a licence, and there is intentionally no LICENSE file provided.

   According to GitHub's licensing documentation, this means that "the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work".

The ransomware group posted some evidences -> https://www.ransomlook.io/screenshots/rhysida/British%20Libr...

and the ransomware group details -> https://www.ransomlook.io/group/rhysida

Good point, I never tried the Clairefontaine notebook. Do you use the Clairefontaine My.Essential model or another one? I'll need to give a try and add it in the list.

Indeed, specific files such as empty files but also many one or two bytes files are very recurring in many software sources. In the next version, we will include the MISP-warninglists such as the empty-hashes lists https://github.com/MISP/misp-warninglists/blob/main/lists/em... to warn about potential common files.

The tool can also work with the Bloom filter provided by hashlookup when the request to the API are not possible.

The license of Dark Lang is a non-free proprietary license -> https://github.com/darklang/dark/blob/main/LICENSE.md.

Indeed, good point. I'll add a set of regular expressions for bugs related to overflow, double-free or alike. Don't hesitate to make a pull-request or open an issue if you see anything missing.

The raw text of the article: https://pastebin.com/SLkqQXfb

The tool mentioned is released as open source at the following location: https://github.com/Vincent-CIRCL/visjs_classificator

The "open" challenge is quite restrictive as it only applies to the following countries: "Argentina, Australia, Brazil, Canada, China, Colombia, France, Germany, India, Japan, Mexico, Netherlands, Peru, South Africa, Spain, United Kingdom United States of America"

Sorry, I wanted to change it after I push the submit button... it was too late.

Is RequestMap Open Source?

We tried from three European mobile numbers (France, Luxembourg, Belgium) but it doesn't work.

Talking about FAX machines, Hack.lu 2018: What The Fax?! - Eyal Itkin and Yaniv Balmas

https://www.youtube.com/watch?v=aahHbliwfm0

OpenBGPD is missing from the list. It's a great piece of software.

Indeed, it's a common confusion for French-speakers. Nevertheless for AIL, we came with the acronym first...

and by the way, we organise a free and open training (25 March 2019) session in Luxembourg on how to use and extend AIL. The registration link -> https://en.xing-events.com/SHKMYKL.html

Good point... The origin of the acronym is a bad joke at the office (AIL) because in French AIL means garlic and we had another project called Potiron https://github.com/CIRCL/potiron which means pumpkin and then AIL was used as ingredient to make a pumpkin soup. Sorry, we are bad at naming projects.

At least, this one is in Python. My dream would be to have a transactional graph database written in Python which is used as back-end for NetworkX (https://networkx.github.io/).

It's not immune to explicit consent. You have to clearly state it why you (or your data processor) does email tracking. This can be included and described when the user subscribe to your blog post.

Tracking emails for marketing purposes can be seen as a legitimate interest. As long, it's describe to the data-subject and they give their consent, it's allowed.

Recital 48 is giving some explanation:

"The processing of personal data for direct marketing purposes may be regarded as carried out for a legitimate interest."

https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...

I think it's more easy. When they subscribe to your blog, you should include the aspect that the data processor (handling the email) do some additional tracking in order to pursue a specific service. Regarding the consent (article 7 of the GDPR), provide a clear description why you do tracking and the objective. The transparency aspect is very important.

PS: It's usually better to have a look at the GDPR on the official website of EUR-Lex. https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...

If a data-subject subscribes to a mailing-list by giving your email and you have a "request for consent shall be presented in a manner which is clearly distinguishable from the other matters" which can be clearly describe in your privacy policy, you are totally inline with the article 7 for the condition of consents.

Why don't you put a privacy policy explaining this in your blog? As long as you ensure 'lawfulness, fairness and transparency', you can easily be "GDPR-compliant". Keep a record of your processing activities (e.g. MailChimp is data processor and your are the data controller) and a quick note about the risk associated.

If you are interested to run your own pastebin (or alike) analysis, AIL is a "modular framework to analyse potential information leaks from unstructured data sources like pastes from pastebin or similar services or unstructured data streams." https://github.com/CIRCL/AIL-framework

The interesting part in your comment is the triggering of the old aesthetic discussion about photography and beauty.

Beauty in Photography by Robert Adams might be an interesting starting point to expand your comment:

http://aransomephoto.com/wp-content/uploads/2016/10/Robert-A...

Regarding the photography of Wouter Rietberg, there is probably a certain beauty which can touch and can be related to a specific cultural background (maybe an heritage from the Bauhaus design). Everyone is influenced and maybe your perspective of beauty is composed from your own cultural heritage.

On a personal level, I find the work of Wouter Rietberg very dense but towards this too perfect or describing too-polished structure of the world. I'm missing a bit the human imprint or decision to make the photography more natural. It doesn't mean it's ugly or not beautiful, it's just I don't feel my sense of beauty being touched by this photographic approach which looks a bit systematic to my eyes. I'm sure many photographer or viewer might be touched by this systematic approach.

Maybe we're just all blind due to our own perceptions.

The MISP project[1] which is an open source project around threat intelligence sharing is actively looking for contributions and supports to write documentation. There is already a git book[2] which needs some love and support especially on the aspect of using the platform for analysts or security operators.

[1] https://github.com/MISP/ [2] https://github.com/MISP/misp-book