home.social

#checksum — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #checksum, aggregated by home.social.

  1. А что не так с вашими миграциями? Liquibase, rollback и первые тревожные признаки

    Миграции базы данных вроде бы есть, Liquibase подключен, changelog лежит в репозитории, CI зелёный, релизы проходят регулярно. Значит, процесс под контролем? Не всегда…

    habr.com/ru/articles/1036052/

    #миграции_базы_данных #Liquibase #Flyway #changelog #rollback_миграций #checksum #database_schema #SQL_миграции #безопасный_релиз #ревью_миграций

  2. А что не так с вашими миграциями? Liquibase, rollback и первые тревожные признаки

    Миграции базы данных вроде бы есть, Liquibase подключен, changelog лежит в репозитории, CI зелёный, релизы проходят регулярно. Значит, процесс под контролем? Не всегда…

    habr.com/ru/articles/1036052/

    #миграции_базы_данных #Liquibase #Flyway #changelog #rollback_миграций #checksum #database_schema #SQL_миграции #безопасный_релиз #ревью_миграций

  3. А что не так с вашими миграциями? Liquibase, rollback и первые тревожные признаки

    Миграции базы данных вроде бы есть, Liquibase подключен, changelog лежит в репозитории, CI зелёный, релизы проходят регулярно. Значит, процесс под контролем? Не всегда…

    habr.com/ru/articles/1036052/

    #миграции_базы_данных #Liquibase #Flyway #changelog #rollback_миграций #checksum #database_schema #SQL_миграции #безопасный_релиз #ревью_миграций

  4. А что не так с вашими миграциями? Liquibase, rollback и первые тревожные признаки

    Миграции базы данных вроде бы есть, Liquibase подключен, changelog лежит в репозитории, CI зелёный, релизы проходят регулярно. Значит, процесс под контролем? Не всегда…

    habr.com/ru/articles/1036052/

    #миграции_базы_данных #Liquibase #Flyway #changelog #rollback_миграций #checksum #database_schema #SQL_миграции #безопасный_релиз #ревью_миграций

  5. Tenia pensado crear un proyecto de #preservacion especialmente #musica
    Básicamente recopilar y archivar todas las canciones de un álbum junto con todos los datos relacionados a él incluyendo hasta el nombre del oboista. Y usar #checksum #torrents y #par2 para que no se corrompan y que sean fáciles de compartir. Porque hay #artistas cuya música es genial, pero fue lanzada hace mucho y no está disponible en las plataformas de #Streaming . Planeo subirlos a #internearchive o algo así.

  6. Tenia pensado crear un proyecto de #preservacion especialmente #musica
    Básicamente recopilar y archivar todas las canciones de un álbum junto con todos los datos relacionados a él incluyendo hasta el nombre del oboista. Y usar #checksum #torrents y #par2 para que no se corrompan y que sean fáciles de compartir. Porque hay #artistas cuya música es genial, pero fue lanzada hace mucho y no está disponible en las plataformas de #Streaming . Planeo subirlos a #internearchive o algo así.

  7. Tenia pensado crear un proyecto de #preservacion especialmente #musica
    Básicamente recopilar y archivar todas las canciones de un álbum junto con todos los datos relacionados a él incluyendo hasta el nombre del oboista. Y usar #checksum #torrents y #par2 para que no se corrompan y que sean fáciles de compartir. Porque hay #artistas cuya música es genial, pero fue lanzada hace mucho y no está disponible en las plataformas de #Streaming . Planeo subirlos a #internearchive o algo así.

  8. I was working on the new BashCore build when the process suddenly failed because the Metasploit #APT #repository returned a “file has unexpected size” error... 😳😩🤔

    Seems like a temporary #checksum #mismatch during #mirror #sync, hopefully nothing serious. Rebuilding now to see if it’s fixed.

    #BashCore #Debian #Metasploit #LiveBuild #LinuxDev #FOSS

  9. I was working on the new BashCore build when the process suddenly failed because the Metasploit #APT #repository returned a “file has unexpected size” error... 😳😩🤔

    Seems like a temporary #checksum #mismatch during #mirror #sync, hopefully nothing serious. Rebuilding now to see if it’s fixed.

    #BashCore #Debian #Metasploit #LiveBuild #LinuxDev #FOSS

  10. I was working on the new BashCore build when the process suddenly failed because the Metasploit #APT #repository returned a “file has unexpected size” error... 😳😩🤔

    Seems like a temporary #checksum #mismatch during #mirror #sync, hopefully nothing serious. Rebuilding now to see if it’s fixed.

    #BashCore #Debian #Metasploit #LiveBuild #LinuxDev #FOSS

  11. I was working on the new BashCore build when the process suddenly failed because the Metasploit #APT #repository returned a “file has unexpected size” error... 😳😩🤔

    Seems like a temporary #checksum #mismatch during #mirror #sync, hopefully nothing serious. Rebuilding now to see if it’s fixed.

    #BashCore #Debian #Metasploit #LiveBuild #LinuxDev #FOSS

  12. I was working on the new BashCore build when the process suddenly failed because the Metasploit #APT #repository returned a “file has unexpected size” error... 😳😩🤔

    Seems like a temporary #checksum #mismatch during #mirror #sync, hopefully nothing serious. Rebuilding now to see if it’s fixed.

    #BashCore #Debian #Metasploit #LiveBuild #LinuxDev #FOSS

  13. /* Calculate the boot block checksum on an ADFS drive. Note that this will appear to be correct if the sector contains all zeros, so also check that the disk size is non-zero!!! */

    elixir.bootlin.com/linux/v6.15

    #linux #kernel #adfs #checksum

  14. /* Calculate the boot block checksum on an ADFS drive. Note that this will appear to be correct if the sector contains all zeros, so also check that the disk size is non-zero!!! */

    elixir.bootlin.com/linux/v6.15

    #linux #kernel #adfs #checksum

  15. /* Calculate the boot block checksum on an ADFS drive. Note that this will appear to be correct if the sector contains all zeros, so also check that the disk size is non-zero!!! */

    elixir.bootlin.com/linux/v6.15

    #linux #kernel #adfs #checksum

  16. Bei meinen letzten Downloads von Xubuntu, NixOS und Raspberry Pi OS stimmen nie die Checksum mit der auf der angezeigten Checksum auf der Website überein! 🤔
    sudo sha256sum file
    Kann das jemand nachvollziehen?
    #Linux #iso #Checksum
  17. @eternaltyro @kde

    I remember being pretty excited when I found out #Dolphin has a built in #checksum verification tool.

    But in all fairness, if there's a mundane terminal task, there's probably a desktop tool with GUI that can be used like #GtkHash.

    Of course, it's not as convenient as going "right click > properties". But it's nice to know that there are options for situations where we have to use a different desktop environment.

  18. Jan: Fixity - property of being unchanged Checksum - it's like digital fingerprint ( #Fixity ✅ and #Checksum ✅ - #DigiPresBingo)

  19. AFAIK, there's only one existing Vim plugin for buffer checksums, and it's quite old, relying heavily on terminal tools. I've developed a newer version using Vim9Script and the V language. Contributions and ideas are welcome.
    github.com/sevehub/vchecksum.v

  20. Quick question for my fellow Mac users: Is it true that there's no built-in CLI command to check a SHA256 checksum, and you need to install the entire GNU coreutils for that? 🤔

  21. Why is it so damn hard to do a checksum thing on linux mint? FFS. Is it just me? I tried following the instructions and it's like a bunch of steps and I can't even find the right place to get GnuPg.
    I feel like I must be missing something.
    #linux #linuxmint #checksum #ugh

  22. CW: data loss

    me: okay, this saturday, before adding any more documents into my personal Paperless-ngx installation that I've built two weeks ago and start to use seriously, let's set up automated backups first

    me, clicking through the frontend: huh, that thumbnail looks garbled …

    me, clicking on the document: uhm, the PDF looks broken, too

    Paperless's sanity checker: what if i told you that the SD card I'm running on is already dying?

    #Paperless #PaperlessNGX #backup #dataloss #checksum

  23. #random: I'm obviously 69-times checking my files on the archive if ever it has been modified by sheer accident (by checksums and signing) so I couldn't be messed with extracting them again.

    #tech #checksum #fileintegrity

  24. For the freaks out there, I also implemented a signature system just to be extra sure about the origin of the files. I also redid my pubkeys again (as I forgot my old one and couldn't revoke it).

    You can check my PGP pubkey fingerprint on my bio.

    #checksum #hash #Microsoft #windows #windowsphone #archive #tech #technology #mobile #phone #smartphone #openpgp

  25. Doing some checksum work to ensure the integrity of the files in the Windows Phone Emulator Images Archives (something I didn't do in the previous one with Windows Mobile).

    Checksums for VHDs and BINs are available, in MD5, SHA-1, SHA-256 and CRC32 to verify the integrity of these large files (ranging from 77MB to 2.9GB).

    #checksum #hash #Microsoft #windows #windowsphone #archive #tech #technology #mobile #phone #smartphone

  26. I updated the sendmeshfile.sh script to include md5 checksums for the previous base64 line sent. This should allow "error detection" if a receiver misses a line (much notes in the bash comments):

    pastebin.com/V35zc6Tb

    #bash #meshtastic #base64 #checksum #errordetection

  27. #CDFriday with #Checksum a short-lived project out of San Francisco from Greg Freeman (recording engineer, owner of Lowdown Studios, also was in bands like Pell Mell, S.F. Seals, and Virginia Dare) and Jeff Palmer. Lethargic cross between downtempo, dub, and math rock.

  28. The whole point to a #qubit is we don’t measure it until the end of the computation which, like Schrödinger’s cat, seals its fate.

    So if you were to “read” a bunch of qubits to form a #checksum or a #CRC, you’d destroy their quantum nature in the process making your computer not very useful.

    You can’t even copy a bit to use something like #triple #redundancy, either. There seems to be no way to practically duplicate a qubit.

    #Peter #Schor came up with an answer. Instead of copying a qubit directly, the computer can spread a logical qubit across nine actual qubits. It is then possible to determine if there has been a single physical qubit error using a complicated algorithm.

    Later research has dropped the number of qubits required down to five which appears to be the theoretical limit.

    hackaday.com/2021/11/11/scient

  29. The whole point to a #qubit is we don’t measure it until the end of the computation which, like Schrödinger’s cat, seals its fate.

    So if you were to “read” a bunch of qubits to form a #checksum or a #CRC, you’d destroy their quantum nature in the process making your computer not very useful.

    You can’t even copy a bit to use something like #triple #redundancy, either. There seems to be no way to practically duplicate a qubit.

    #Peter #Schor came up with an answer. Instead of copying a qubit directly, the computer can spread a logical qubit across nine actual qubits. It is then possible to determine if there has been a single physical qubit error using a complicated algorithm.

    Later research has dropped the number of qubits required down to five which appears to be the theoretical limit.

    hackaday.com/2021/11/11/scient

  30. The whole point to a #qubit is we don’t measure it until the end of the computation which, like Schrödinger’s cat, seals its fate.

    So if you were to “read” a bunch of qubits to form a #checksum or a #CRC, you’d destroy their quantum nature in the process making your computer not very useful.

    You can’t even copy a bit to use something like #triple #redundancy, either. There seems to be no way to practically duplicate a qubit.

    #Peter #Schor came up with an answer. Instead of copying a qubit directly, the computer can spread a logical qubit across nine actual qubits. It is then possible to determine if there has been a single physical qubit error using a complicated algorithm.

    Later research has dropped the number of qubits required down to five which appears to be the theoretical limit.

    hackaday.com/2021/11/11/scient

  31. The whole point to a #qubit is we don’t measure it until the end of the computation which, like Schrödinger’s cat, seals its fate.

    So if you were to “read” a bunch of qubits to form a #checksum or a #CRC, you’d destroy their quantum nature in the process making your computer not very useful.

    You can’t even copy a bit to use something like #triple #redundancy, either. There seems to be no way to practically duplicate a qubit.

    #Peter #Schor came up with an answer. Instead of copying a qubit directly, the computer can spread a logical qubit across nine actual qubits. It is then possible to determine if there has been a single physical qubit error using a complicated algorithm.

    Later research has dropped the number of qubits required down to five which appears to be the theoretical limit.

    hackaday.com/2021/11/11/scient

  32. The whole point to a #qubit is we don’t measure it until the end of the computation which, like Schrödinger’s cat, seals its fate.

    So if you were to “read” a bunch of qubits to form a #checksum or a #CRC, you’d destroy their quantum nature in the process making your computer not very useful.

    You can’t even copy a bit to use something like #triple #redundancy, either. There seems to be no way to practically duplicate a qubit.

    #Peter #Schor came up with an answer. Instead of copying a qubit directly, the computer can spread a logical qubit across nine actual qubits. It is then possible to determine if there has been a single physical qubit error using a complicated algorithm.

    Later research has dropped the number of qubits required down to five which appears to be the theoretical limit.

    hackaday.com/2021/11/11/scient

  33. Persistence Pays in TI-99/4A Cassette Tape Data Recovery - In the three or four decades since storing programs on audio cassettes has been re... - hackaday.com/2023/06/16/persis #retrocomputing #audacity #cassette #checksum #recovery #ti-99/4a #audio #tape #fsk

  34. Hacking on #checksum support for the alpm-types crate today, as I have forgotten to add one for sha256 before the 0.2.0 release (which I actually need for .BUILDINFO 🤦 ).

    Once the #traits fun is out of the way, the addition for generic checksum support is surprisingly small.

    #archlinux #rustlang #alpm