Sunday, April 13, 2025

Sentimental Sundays - 1968 Honeywell Briefcase Computer


 The 1968 Honeywell Briefcase Computer was a visionary concept that foreshadowed the modern laptop. Commissioned by Stanley Kubrick for his film 2001: A Space Odyssey, the briefcase was designed to be a portable computing solution for the character Heywood Floyd. It included a range of advanced features for its time, such as a computer, modem, telephone, TV camera, and microfilmed documents, all integrated into a compact and stylish briefcase. The design was not only a prop for the film but also a forward-looking prediction of future technology, suggesting that such devices would be commercially available within 15 years. While the briefcase was a concept piece and not a functional device, it accurately anticipated the miniaturization and portability of computing technology that would become commonplace in the decades to follow.

One of the most striking aspects of the Honeywell Briefcase Computer was its innovative design. The briefcase featured a CRT screen that was surprisingly thin for its time, though it was still a conceptual representation rather than a functional display. The screen was rounded and fitted into the lid of the briefcase, which was an early attempt to create a portable and user-friendly interface. The device also included a red-handled wand for direct screen input, as touch screens had not yet been developed. This wand was a precursor to modern stylus technology, which is still used in various forms today. The keyboard, while mechanical, was designed with a unique layout, including a dedicated square root key, which was a nod to the mathematical and scientific applications of the device.

The Honeywell Briefcase Computer concept was part of a broader trend in the 1960s to envision a future where technology would be more integrated into daily life. While the briefcase itself was a concept piece, it inspired other futurist visions and technological advancements. For example, researcher Alan Kay, influenced by the learning theories of Jerome Bruner and Seymour Papert, created a mockup of a wirelessly connected tablet-like computer called the Dynabook in 1968. Although the Dynabook was never built, it was a highly influential design that anticipated many of the features of modern tablets and laptops, including a graphical user interface and object-oriented programming. The Honeywell Briefcase Computer and the Dynabook both exemplify the forward-thinking approach of the 1960s, where futurists and technologists were beginning to imagine a world where computing would be portable, accessible, and deeply integrated into everyday activities.

Trivia: The Honeywell Briefcase Computer was not the only futuristic device featured in 2001: A Space Odyssey. The film also included a flat-screen tablet-like device that appeared on the dining table of the Discovery One spacecraft. This device, which was simulated by projecting from under the table, was an early and accurate prediction of modern tablets and entertainment screens, demonstrating that Kubrick and his team had a keen understanding of the direction technology was heading.


Friday, April 11, 2025

Unlocking the Power of Wireshark: Rebuilding SMB-Copied Files


 In the world of network analysis, few tools are as versatile and powerful as Wireshark. Wireshark offers a window into the intricate details of network traffic for IT professionals, cybersecurity enthusiasts, and network administrators. One particularly useful application is its ability to rebuild files transferred over the Server Message Block (SMB) protocol, a common method for copying files across networks. Whether you’re troubleshooting a slow file transfer, investigating suspicious activity, or simply curious about what’s moving through your network, Wireshark can help you reconstruct those files precisely and easily.

The process begins by capturing network packets as the file is copied via SMB, a protocol widely used in Windows environments for sharing files and printers. Once the capture is complete, Wireshark’s robust filtering capabilities allow you to isolate SMB traffic and extract the raw data payloads embedded within the packets. By following the packet stream and exporting the reconstructed data, you can rebuild the original file—be it a document, image, or executable—right from the network traffic. This capability not only aids in diagnosing network issues but also serves as a powerful forensic tool for analyzing potentially malicious file transfers.



Wednesday, April 9, 2025

why not tcping it ?

 


Pouriya Jamshidi’s GitHub profile https://github.com/pouriyajamshidi showcases a variety of open-source projects, primarily focused on networking, security, and system diagnostics. As a hobbyist programmer based in Belgium, Jamshidi has developed 27 repositories, with several standout tools that cater to developers, network administrators, and security enthusiasts. His work emphasizes practical utilities written in languages like Go, Rust, Nim, and Python, reflecting a strong interest in creating efficient, cross-platform solutions for real-world problems. The projects range from network monitoring tools to security-focused applications, demonstrating both technical skill and a commitment to community-driven development.

One of Jamshidi’s most notable projects is tcping, a TCP port-pinging utility inspired by the traditional Linux ping command, written in Go. With over 796 stars and 70 forks, it’s a popular tool for testing TCP connectivity, offering features like customizable timeouts, interval settings, and output formats (CSV, JSON, SQLite). It supports multiple platforms, including Linux, Windows, and macOS, with installation options via Homebrew, Docker, or direct downloads from GitHub releases. The project’s active development, driven by community contributions, includes recent updates like ARM64 support and enhanced DNS resolution, making it versatile for diverse environments, including Android (with some noted limitations).

Another significant contribution is qwatcher, a queue-monitoring tool written in Nim, designed to diagnose TCP connection issues on Linux systems by tracking input and output buffers. It provides flexible logging options (SQLite database or text files) and real-time console output, helping users identify buffer-related connectivity problems. Other projects like oxipot, a Rust-based network honeypot, and nginwho, a Nim-based Nginx log parser with Cloudflare IP resolution, further highlight Jamshidi’s focus on security and network analysis. These tools are lightweight, practical, and aimed at enhancing system visibility and protection.

Jamshidi’s repositories also include specialized utilities like flat, which measures UDP and TCP latency using eBPF and Go, and fwmonitor, a Python script for analyzing iptables and UFW logs. His work is well-documented, often accompanied by clear installation instructions and usage examples, encouraging collaboration through issues and pull requests. With 37 followers and an active presence on X (@pouriyajamshidi), 

Jamshidi fosters a community around his tools, which are licensed under permissive terms like MIT or GPL, ensuring accessibility. Overall, his GitHub profile represents a valuable collection of networking and security tools, blending technical expertise with a passion for open-source innovation. 





Tuesday, April 8, 2025

Monday, April 7, 2025

Why Is My 1 Gb Really 100mb?

 


I’ve seen various themes on the same scenario multiple times;

-          Client upgrades network components and sees no improvement, or gets worse performance and has no idea why.

-          Could be a new access point, new switch, router, firewall, internet package or client computer


There are multiple issues with this scenario that I can highlight with a few questions

-          Do you know what the performance was before?

-          How did you test?

-          Did you monitor?

-          How long did you test for?

-          Was there any business or social events that would impact performance like tax season for an accounting department or Christmas season for a department store?

Let take a simple scenario where the analyst upgraded the internet bandwidth from 100 Mb/s to 1 Gb/s. He performed a simple speedtest from speedtest.net before and after the upgrade, from the same computer, at the same time, multiple times.

Before the upgrade, the analyst recorded an average of 93 Mb/s upload and download.  After the upgrade the numbers were identical. He immediately checked his computer nic speed, which was 1 Gb/FD and same for his switch port.

Spoiler alert:  in this case there was a cable between the firewall and switch that was running at 100 Mbs since the cable was ‘marginal’ at best.

I replicated this scenario in my lab and created this video for your enjoyment and entertainment.

Enjoy



Popular post