Lmst

Visited the #NASM Udvar-Hazy Center the other day and had to get a holiday photo with one of my favorite #WW2 aircraft, the F4U Corsair.

Overweight middle-aged man with glasses and a whitening beard, wearing a brown brimmed hat and a dark-gray vest and scarf standing in front of an F4U Corsair aircraft (gull-winged in blue) suspended from the ceiling in a vast hangar, with a bauble-bedecked yuletide tree along the right side of the shot.

@tobyjaffey basically anything at this point. Haskell works just right AFAIK, GHC is quite far from "simple" but MicroHs can do. Prologs generally work. I wish we had a good rv64 equivalent of #nasm .

Парсим XML и JSON на ассемблере

Отобрал для вас несколько крайне интересных, но малоизвестных проектов, реализующих работу с XML и JSON. Кроссплатформенных и без зависимостей. На чистом С и ассемблере.

https://habr.com/ru/articles/964522/

#json #xml #nasm #assembler #c_language #simd #simdjson #freebsd

Today's photo: IJplein (1894).

[EN] SS Schiedam, a ship of the Dutch-American Steamboat Company (NASM, better known as the Holland America Line), in a dock of ADM (Amsterdam Dry Dock Company). It had departed […]

[NL] Het ss Schiedam, een schip van de NASM (Holland Amerika Lijn), in een dok van de Amsterdamse Droogdok Maatschappij (ADM). Het was op 13 april uit New York vertrokken en op 5 […]

Via https://020apps.nl/olie/random/ #Amsterdam #JacobOlie #IJplein #NASM #shipyard #steamship

Exciting news!!!! #smithsonian #museum #aviation #virginia #nasm

https://airandspace.si.edu/newsroom/press-releases/national-air-and-space-museum-expands-its-steven-f-udvar-hazy-center?utm_campaign=airandspace&utm_medium=social&utm_source=facebook&fbclid=IwY2xjawMtL99leHRuA2FlbQIxMABicmlkETFPUXN2UnQwRU4yamtiZmpkAR4WWf2T6R4WL1kdw6oRF1D78HBeJOWkZs7ofjl48xWoO2F_8ZkDAXHxH7Q6Vg_aem_BE8i4BVLXf8pbl_ya8mi3g

32-bit #NASM equivalent:

BITS 32
GLOBAL _start
SECTION .text
_start:
    dec esp
    dec ecx
    dec esp
    dec ecx
    push esp
    dec eax
    pop esp

    mov eax, 4
    mov ebx, 1
    mov ecx, nope
    mov edx, nope_len
    int 0x80

    xor eax, eax
    inc eax
    mov bl, 0
    int 0x80

SECTION .data
    nope: db "Nothing to see here...",10,0
    nope_len: equ $-nope

Make:

nasm -f elf32 -o program.o program.asm && ld -nostdlib -s -n -m elf_i386 -o program program.o

For those wondering what exactly is going on, the screenshot further explains and reveals it.

#steganography #hiddenmessage #assembly #code #asmcode #programming #codegolf #occult

Screenshot of a terminal depicting the output of multiple, sequential commands:

1. `make` invokes `rm program.o || true`, then `rm program || true`, then `nasm -f elf32 -o program.o program.asm && ld -nostdlib -s -n -m elf_1386 -o program program.o`
2. `./program; echo $?` outputs "Nothing to see here..." followed by 0 (success as exit code, so no crash, no segmentation fault, nothing wrong)
3. `objdump -S -F program` shows the disassembly of said program, together with file offsets, as well as its format `elf32-i386`. The main section of machine code, `.text`, which starts at file offset 0x60, shows both the hexadecimal opcodes, as well as the Assembly instructions (which are practically those included in this post, with some differences such as `.nope` disassembling as a literal memory address instead of a label name).
4. Finally, `hexdump -C -s 0x60 -n $((0x82 - 0x60)) program` shows what's really going on: you can see the name "LILITH" at the very beginning of the section `.text` (`4c 49 4c 49 54 48 ...`)
5. `strings program` further confirms it by listing "LILITH" as one of the valid ASCII strings inside the file.

In essence, a(n occult, Goddess/entity's) name was concealed as totally runnable machine instructions.

A vulnerability was identified in NASM Netwide Assember 2.17rc0. This issue affects the function assemble_file of the file nasm.c. The manipulation leads to stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

CVE-2025-8845 (GCVE-0-2025-8845)

#nasm #vulnerability

🔗 https://vulnerability.circl.lu/vuln/CVE-2025-8845

This tool allows to assemble Intel 8080/8085 Assembly code with NASM and is implemented as a NASM macro package.

https://github.com/BinaryMelodies/nasm-i8080

#intel8080 #NASM #assembler

#TIL about rel keyword in #nasm #assembly
> In 64-bit mode, NASM will by default generate absolute addresses. The REL keyword makes it produce RIP-relative addresses. Since this is frequently the normally desired behaviour, see the DEFAULT directive (section 6.2). The keyword ABS overrides REL.

What happened to `nasm.us` ?
This domain was the home of netwide #assembler #nasm, and it's not reachable anymore ... which blocks my build pipelines ... and maybe other foreign build systems.

#dnschecker fails to resolve the domain too.

Is this a temporary problem?
Is all right in the USA 🤔😏 ?

Well, I guess it's time to backup everything and to remove software dependencies ...

Создаем свою ОС (Часть 1)

UNIX-подобная операционная система: пишем ядро на языке C Всем привет недавно я и мой друг решили создать свою операционную систему на ассемблере и C и я решил то что будет неплохо написать об это цикл статей на Хабре! Создаем дальше...

https://habr.com/ru/articles/870000/

#os #nasm #c #linux_dev #unix_system

x64 Assembly & Shellcoding 101

Part 1: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101/

Part 2: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-2/

Part 3: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-3/

Part 4: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-4/

Part 5: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-5/

Part 6: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-6/

#assembly #shellcoding #NASM #debugging

adding stuff up in assembly code: am I right in thinking it's relatively simple with single digits but gets complicated fast if the numbers are double digits or higher?
#Assembly #NASM #ComputerScience

Has anyone got any tips on converting #TASM and #MASM code to a more modern assembler like #NASM? Even just between TASM and MASM would be helpful.

I've got a few old bits of #Psion 8086 assembly that I'd like to use with NASM. My aim is to remove as many proprietary tools as possible.

I guess I'm looking for some sort of Rosetta stone for 8086 Small Memory Model assembly.

Books, web pages and video suggestions welcome.

#x86 #Borland #RetroComputing

Última entrega del primer capítulo del #SolucionarioDelProgramador #GNU_linux . Terminamos con el lenguaje #Ensamblador para echar un ojo a lo que el #procesador realmente hace

#programming #programación #asm #nasm #HelloWorld #HolaMundo #x86_64

https://ibolcode.net/roor/2024-09-hola-mundo-en-ensamblador

Installing NASM and Writing Your First Assembly Program on Linux
#Linux #NASM #C #Coding #Programming #Java #Python
https://linuxtldr.com/installing-nasm/

New #DOS fun with GNU Make, this time using #MASM (ML) 6.11.

Looks like another DPMI runtime conflict - GNU Make is 32-bit, ML is 16-bit, and their respective runtimes won't run the other one.

I can manually run ML for each .ASM file, but it defeats the point of using Make.

I could convert the .ASM files to another DOS assembler. #TASM and #NASM both work with GNU Make.

NASM would make it easy to port the toolchain to other OSes, although it doesn't understand memory models.

Phar Lap err 83: DPMI lock of code/data for HW interrupt handlers failed.

https://wadetregaskis.com/no-platform-load-command-found-in-libxyz-a-assuming-macos/

Is it too late for #ILoveFreeSoftwareDay? Just want to give a shout out to all the #FreeSoftware out there that enables #FreeSoftware: all the compilers (such as #gcc, #llvm, #rust) and assemblers (such as #nasm), the version control (#git) and interpreters (such as #Python and #Perl) and all the build systems. Thanks for enriching my life!

#NASM is claiming this isn't a valid instruction: mov bx, word ss:[sp+04h] , yet I can't see why. Anyone know what I'm doing wrong? (Specific to NASM-syntax) Searching the web doesn't find anything useful... #Assembly #programming #help

#NASM

Client Info