official page / data source

info source

as of 2024-12-02

Summary of Certified Individuals

key location

Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Search

add DWORD (32-bit) Value :

• Value name : SearchResultsCap
• value data : [num], in decimal

limitation value adjustment

• current cap in outlook : 250
• suggested : 500

notes on “removing” the limitation

setting a value of 0, ideally, will remove such limit in search results, but out initial findings suggest that it has a cap at the value of 1050, could possibly be owing to a hardcoded limit by outlook, or the local index cache being incomplete;

japan

0.jp.pool.ntp.org
1.jp.pool.ntp.org
2.jp.pool.ntp.org
3.jp.pool.ntp.org

singapore

0.sg.pool.ntp.org
1.sg.pool.ntp.org
2.sg.pool.ntp.org
3.sg.pool.ntp.org

hongkong

1.hk.pool.ntp.org
1.asia.pool.ntp.org
2.asia.pool.ntp.org

• official page by ntppool.org

overview

As endorsed by the Foreign Ministries of Canada, Denmark, Estonia, France, Germany, The Netherlands, Poland, Sweden, United Kingdom and the United States on 20 December 2023, the Tallinn Mechanism officially formalized.

• date : 2023-12-20
• countries / links to announcements
  • Canada / official announcement
  • Denmark
  • Estonia / official announcement
  • France / official announcement
  • Germany
  • The Netherlands / official announcement
  • Poland / official announcement
  • Sweden
  • United Kingdom / official announcement
  • the United States / official announcement

Overview

The Tallinn Manual, formally titled “Tallinn Manual on the International Law Applicable to Cyber Warfare,” is a significant document in the realm of cybersecurity law. Here’s a detailed breakdown of its key aspects:

Origin and Purpose

• Authored by a group of international law experts between 2009 and 2012.
• Commissioned by the NATO Cooperative Cyber Defence Centre of Excellence (CCDCOE) located in Tallinn, Estonia. (Though it’s not an official NATO document.)
• Aims to clarify how existing international law applies to cyber conflicts and cyber warfare.
• Focuses on two key areas of international law:
  • Jus ad bellum: Rules governing the use of force between states.
  • International humanitarian law (jus in bello): Rules applicable during armed conflicts to protect civilians and combatants.

Content and Structure

• Not a binding legal document, but a highly influential academic study.
• Comprises two editions:
  • Tallinn Manual (2013): Examines the most severe cyber operations, including those that could constitute a use of force or occur during armed conflicts.
  • Tallinn Manual 2.0 (2017): Addresses the legal framework for less severe cyber incidents that fall below the thresholds mentioned above.
• Structured around 95 “black letter rules” that interpret how existing international law principles apply to specific cyber scenarios.
• These rules address various topics like:
  • Sovereignty in cyberspace
  • State responsibility for cyberattacks
  • Targeting civilians and civilian infrastructure in cyber operations
  • Proportionality and distinction in cyber warfare

Significance and Impact

• Considered a foundational text in the field of cyber law.
• Provides a framework for states to assess the legality of their cyber operations and those they face.
• Influences legal discussions and policy decisions regarding cyber issues at the international level.
• Serves as a reference point for ongoing efforts to develop new international law norms specifically for cyberspace.

Limitations

• Being non-binding, it cannot definitively resolve legal disputes.
• The evolving nature of cyber technology may necessitate future updates and interpretations.
• Controversial topics, such as cyber espionage or the use of force in cyberspace, may have varying interpretations among states.

Conclusion

Overall, the Tallinn Manual is a crucial resource for understanding how international law applies to cyber conflicts. It has significantly shaped the discourse on cybersecurity law and continues to influence efforts to establish a more robust legal framework for this complex domain.

overview / about

• what is fluent bit
• fluentd vs fluent bit

overview

given a certain role, there are 2 folders to store variables, namely

• [role root]/default
• [role root]/vars

by default there is an empty main.yml there.

storing all vars inside either of them will get messy easily, so it gets natural to group vars by different files.

but, trying to import / include them inside main.yml won’t work.

the trick to load them all

create these folders :

[role root]/default/main/
[role root]/default/vars/

and put relevant files / folder(s) of files inside accordingly.

have to enable push -f in gitlab first.

git reset --hard [hash]
git push -f origin master

1. add url to repo ( according to .git/config ) and local destination file path

• target file : set-facts-repo.yaml
• file path : [ansible-repo-root]/etc/playbooks/roles/maintenance/tasks/git/tasks

2. add the above facts to the git pull loop

• target file : git-pull.yaml
• file path : [ansible-repo-root]/etc/playbooks/roles/maintenance/tasks/git

usage

via curl :

curl -sS https://jimz.cc/s/deno.sh | bash

via deno :

deno run -Ar https://jimz.cc/s/deno.ts

clone via ssh

git@github.com:dallmo/deno-app-template.git

link to github repo

deno-app-template

deno run -Ar https://deno.land/x/lume/init.ts

ref :

deno run main.ts
deno run https://mydomain.com/main.ts
cat main.ts | deno run -

source 1

/<*>	

• target: /index.html
• type: 404 rewrite`

source 2

</^[^.]+$|\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|ttf|map|json)$)([^.]+$)/>	

• target: index.html
• type: 200 rewrite

files modified in 2011, list them

find . -maxdepth 1 -newermt 20110101 -not -newermt 20120101 -type f -exec ls -lt “{}” ;

files modified in 2011, move them

find . -maxdepth 1 -newermt 20110101 -not -newermt 20120101 -type f -exec mv “{}” move-to-folder/ ;

1. in shell / deno deploy / runtime

1a. define them

• in shell, define and export them like

  export AWS_REGION="ap-southeast-1"
  

• in deno deploy, define them in :

  project settings > environment variables
  

• in run time : with the deno runtime API

  Deno.env.set(key: string, value: string): void
  

  official reference

1b. access them

with the deno runtime API

Deno.env.get(key: string): string | undefined

official reference

2. in .env file

1a. define them

put the file / symlink it to project root :

suggested by the SD Association

link to the download page

official notes on npmjs semver

syntax

• version Must match version exactly
• >version Must be greater than version
• >=version etc
• <version
• <=version
• ~version “Approximately equivalent to version” See semver ( via the external link above )
• ^version “Compatible with version” See semver
• 1.2.x 1.2.0, 1.2.1, etc., but not 1.3.0
• http://... See ‘URLs as Dependencies’ in the original page
• * Matches any version
• "" (just an empty string) Same as *
• version1 - version2 Same as >=version1 <=version2.
• range1 || range2 Passes if either range1 or range2 are satisfied.

valid examples

{ "dependencies" :
  { "foo" : "1.0.0 - 2.9999.9999"
  , "bar" : ">=1.0.2 <2.1.2"
  , "baz" : ">1.0.2 <=2.3.4"
  , "boo" : "2.0.1"
  , "qux" : "<1.0.0 || >=2.3.1 <2.4.5 || >=2.5.2 <3.0.0"
  , "asd" : "http://asdf.com/asdf.tar.gz"
  , "til" : "~1.2"
  , "elf" : "~1.2.3"
  , "two" : "2.x"
  , "thr" : "3.3.x"
  , "lat" : "latest"
  , "dyl" : "file:../dyl"
  }
}

cloudflare

1.1.1.1
1.0.0.1

cloudflare, with malware blocking

1.1.1.2
1.0.0.2

google

8.8.8.8
8.4.4.8

quad9

9.9.9.9
149.112.112.112

openDNS

208.67.222.222
208.67.220.220