Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file removed content/images/chavezcandanga-web.jpg
Binary file not shown.
Binary file added content/images/chavezcandanga-web.webp
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed content/images/who-is-chavezcandanga-com.jpg
Binary file not shown.
Binary file added content/images/who-is-chavezcandanga-com.webp
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion content/leap-second-chaos-2012.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ sudo /etc/init.d/ntp start
- **Leap Smearing**: Today's `ntpd`, `chronyd`, and cloud providers use "leap smear", slowly adjusting clocks over hours to avoid time jumps entirely.
- **Use Monotonic Clocks**: Time-sensitive logic should rely on `CLOCK_MONOTONIC`, not wall-clock time, to measure durations safely.

![Line chart titled "Leap Second: Wall Clock vs Monotonic Time" plotting reported time against elapsed monotonic time. Both lines rise together from 0 through 4. At the leap-second insertion (annotated 23:59:60), wall-clock time flattens for one second while monotonic time keeps climbing. Wall-clock then resumes its climb one tick behind monotonic for the rest of the chart.]({static}/images/leap_second_monotonic_vs_wall_clock.png)
![Line chart titled "Leap Second: Wall Clock vs Monotonic Time" plotting reported time against elapsed monotonic time. Both lines rise together from 0 through 4. At the leap-second insertion (annotated 23:59:60), wall-clock time flattens for one second while monotonic time keeps climbing. Wall-clock then resumes its climb one tick behind monotonic for the rest of the chart.]({static}/images/leap_second_monotonic_vs_wall_clock.webp)
*Figure: Monotonic time continues uninterrupted while wall-clock time repeats a second, highlighting why monotonic clocks are preferred for duration tracking.*

- **Monitor Clock Drift**: Observability pipelines should expose clock sync state and NTP drift as first-class metrics.
Expand Down
4 changes: 2 additions & 2 deletions content/venezuela-twitter-proxy-osint-final.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ whois chavezcandanga.org.ve

Revealed that the domain was registered to **PSUV** (*Partido Socialista Unido de Venezuela*) and managed through CONATEL, Venezuela's FCC-equivalent telecommunications regulator.

![WHOIS output showing chavezcandanga.org.ve registered to PSUV]({static}/images/who-is-chavezcandanga-com.jpg)
![WHOIS output showing chavezcandanga.org.ve registered to PSUV]({static}/images/who-is-chavezcandanga-com.webp)
*Figure: WHOIS lookup confirms chavezcandanga.org.ve is registered to PSUV, with administrative and technical contacts using @psuv.org.ve emails.*

---
Expand All @@ -71,7 +71,7 @@ The same server IP hosted:
- `mensajes.chavezcandanga.org.ve` - a campaign messaging platform
- A proxy script that mirrored Twitter's login screen

![Screenshot of chavezcandanga.org.ve auto-retweet app]({static}/images/chavezcandanga-web.jpg)
![Screenshot of chavezcandanga.org.ve auto-retweet app]({static}/images/chavezcandanga-web.webp)
*Figure: The official chavezcandanga.org.ve campaign app asks users to authenticate with Twitter to enable automatic retweets of Chávez's posts.*

At the time of discovery, this site **did not contain malicious code**, but the potential for **credential harvesting** during peak election activity was substantial. The authentication flow mimicked Twitter's branding and prompted users to log in, creating a window for silent credential capture, token misuse, or targeted amplification based on follower behavior.
Expand Down
Loading