home.social

Search

333 results for “jni”

  1. Two days of national mourning have been declared in Mali after the country's defence minister was killed in an attack by Al-Qaeda linked group JNIM, who have allied with Tuareg rebels. Despite their disagreements, the two sides joined forces to fight against the Malian army, which is supported by Russian mercenaries.
    #Mali #rebels #jihadists #JNIM #ALF #Tuareg #Sahel

    youtube.com/watch?v=qarFabO8S0g

  2. Two days of national mourning have been declared in Mali after the country's defence minister was killed in an attack by Al-Qaeda linked group JNIM, who have allied with Tuareg rebels. Despite their disagreements, the two sides joined forces to fight against the Malian army, which is supported by Russian mercenaries.
    #Mali #rebels #jihadists #JNIM #ALF #Tuareg #Sahel

    youtube.com/watch?v=qarFabO8S0g

  3. Two days of national mourning have been declared in Mali after the country's defence minister was killed in an attack by Al-Qaeda linked group JNIM, who have allied with Tuareg rebels. Despite their disagreements, the two sides joined forces to fight against the Malian army, which is supported by Russian mercenaries.
    #Mali #rebels #jihadists #JNIM #ALF #Tuareg #Sahel

    youtube.com/watch?v=qarFabO8S0g

  4. Two days of national mourning have been declared in Mali after the country's defence minister was killed in an attack by Al-Qaeda linked group JNIM, who have allied with Tuareg rebels. Despite their disagreements, the two sides joined forces to fight against the Malian army, which is supported by Russian mercenaries.
    #Mali #rebels #jihadists #JNIM #ALF #Tuareg #Sahel

    youtube.com/watch?v=qarFabO8S0g

  5. Africa Corps, a paramilitary group controlled by Russia's Defence Ministry, confirmed on Monday that its forces had withdrawn from the northern town of Kidal in Mali after ‌fierce fighting there. Africa Corps has been supporting the Malian junta since deploying to Mali in 2025. But Russia's presence in the country stretches back to 2021.
    #Mali #rebels #jihadists #Russia #JNIM #Tuareg #ALF #Azawad

    youtube.com/watch?v=okim7F1f5-A

  6. Africa Corps, a paramilitary group controlled by Russia's Defence Ministry, confirmed on Monday that its forces had withdrawn from the northern town of Kidal in Mali after ‌fierce fighting there. Africa Corps has been supporting the Malian junta since deploying to Mali in 2025. But Russia's presence in the country stretches back to 2021.
    #Mali #rebels #jihadists #Russia #JNIM #Tuareg #ALF #Azawad

    youtube.com/watch?v=okim7F1f5-A

  7. Africa Corps, a paramilitary group controlled by Russia's Defence Ministry, confirmed on Monday that its forces had withdrawn from the northern town of Kidal in Mali after ‌fierce fighting there. Africa Corps has been supporting the Malian junta since deploying to Mali in 2025. But Russia's presence in the country stretches back to 2021.
    #Mali #rebels #jihadists #Russia #JNIM #Tuareg #ALF #Azawad

    youtube.com/watch?v=okim7F1f5-A

  8. Africa Corps, a paramilitary group controlled by Russia's Defence Ministry, confirmed on Monday that its forces had withdrawn from the northern town of Kidal in Mali after ‌fierce fighting there. Africa Corps has been supporting the Malian junta since deploying to Mali in 2025. But Russia's presence in the country stretches back to 2021.
    #Mali #rebels #jihadists #Russia #JNIM #Tuareg #ALF #Azawad

    youtube.com/watch?v=okim7F1f5-A

  9. Africa Corps, a paramilitary group controlled by Russia's Defence Ministry, confirmed on Monday that its forces had withdrawn from the northern town of Kidal in Mali after ‌fierce fighting there. Africa Corps has been supporting the Malian junta since deploying to Mali in 2025. But Russia's presence in the country stretches back to 2021.
    #Mali #rebels #jihadists #Russia #JNIM #Tuareg #ALF #Azawad

    youtube.com/watch?v=okim7F1f5-A

  10. : Satellite imagery from Friday 25 April show the damage and destruction to parts of the infrastructure inside the former MINUSMA military base in , meanwhile used by and , following the attack by and .

    Coordinates: 18.418225, 1.413964

  11. #Mali: Satellite imagery from Friday 25 April show the damage and destruction to parts of the infrastructure inside the former MINUSMA military base in #Kidal, meanwhile used by #FAMa and #AfricaCorps, following the attack by #FLA and #JNIM.

    Coordinates: 18.418225, 1.413964

  12. Создаем Java обертку для C++ класса в Android приложении, а также реализуем обратные вызовы из нэйтива

    Кратко расскажу о себе и о том, зачем возникла необходимость в подобном. Я более десяти лет пишу приложения под Android, около 5 лет под IOS, и сейчас переношу свои наработки под десктопы. Приложения мои предназначены для сисадминов, это SSH клиент, сетевые сканеры и тд. В общем, самое сложное - не сам интерфейс, а то, что под капотом. Когда я лишь начинал, я думал, что остановлюсь на платформе Android и стал пилить все на Java. Но затем осознал свою ошибку и исправил ее. На данный момент все мои приложения состоят из двух частей: общего для всех систем ядра на С++ и платформозависимого интерфейса, написанного на Java/Swift/C++ в зависимости от системы. Оговорюсь сразу, эта статья будет лишь своего рода вступлением. Я покажу, как работать с объектно-ориентированным кодом на C++ в Java оболочке (в JNI нам доступен экспорт С функций). Инициализировать объект, делать из него вызовы, удалять, при этом имея аналогичный класс в оболочке, будто бы наш код был написан на Java. Задача эта не слишком сложная, но прежде чем опытные прогеры закрыли эту статью, я оговорюсь, что в следующей части мы уже будем работать с каллбэками - вызовами Java листенеров из нашего С++ кода, а вот это уже задача совсем нетривиальная, требующая понимания работы JNI и Dalvik. Но обо всем по порядку. Итак, у нас есть некий CPP класс и Java оболочка. Через JNI мы можем вызывать только С-функции, то есть не объектный код. Так как же нам работать с ООП? Главная проблема - не столько вызовы, сколько хранение адреса объекта нативного класса. Лично для себя я нашел решение - хранить его в Java классе, как long. То есть, у нас получается приблизительно такой код:

    habr.com/ru/articles/1017486/

    #Java #C++ #ООП #Dalvik #JNI #android

  13. Signal vs Wire — binary analysis of both APKs (apktool, strings, ELF inspection).

    The gap is larger than most people think:

    Signal: Rust core (libsignal_jni.so), Kyber-1024 post-quantum hybrid ratchet, SQLCipher for at-rest encryption, SVR with Intel SGX attestation, IME_FLAG_NO_PERSONALIZED_LEARNING (keyboard can't index your messages), zero third-party trackers.

    Wire: Kotlin/Ktor, no hardened native core (more accessible to Frida), no SQLCipher (messages extractable in plaintext on rooted devices), no post-quantum, Segment SDK for behavioural telemetry.

    But the finding that surprised me most:

    Wire APKs from unofficial stores (Uptodown et al.) contain additional tracking workers and ACCESS_SUPERUSER permission requests not present in the official build. Supply chain integrity is not a footnote — it's the threat model.

    Conclusion: Signal is the only one of the two suitable for threat models involving physical or administrative device compromise.

    soon the full paper

    #infosec #AndroidSecurity #Signal #Wire #ReverseEngineering #mobileforensics #supplychain #MASA

  14. Signal vs Wire — binary analysis of both APKs (apktool, strings, ELF inspection).

    The gap is larger than most people think:

    Signal: Rust core (libsignal_jni.so), Kyber-1024 post-quantum hybrid ratchet, SQLCipher for at-rest encryption, SVR with Intel SGX attestation, IME_FLAG_NO_PERSONALIZED_LEARNING (keyboard can't index your messages), zero third-party trackers.

    Wire: Kotlin/Ktor, no hardened native core (more accessible to Frida), no SQLCipher (messages extractable in plaintext on rooted devices), no post-quantum, Segment SDK for behavioural telemetry.

    But the finding that surprised me most:

    Wire APKs from unofficial stores (Uptodown et al.) contain additional tracking workers and ACCESS_SUPERUSER permission requests not present in the official build. Supply chain integrity is not a footnote — it's the threat model.

    Conclusion: Signal is the only one of the two suitable for threat models involving physical or administrative device compromise.

    soon the full paper

    #infosec #AndroidSecurity #Signal #Wire #ReverseEngineering #mobileforensics #supplychain #MASA

  15. Signal vs Wire — binary analysis of both APKs (apktool, strings, ELF inspection).

    The gap is larger than most people think:

    Signal: Rust core (libsignal_jni.so), Kyber-1024 post-quantum hybrid ratchet, SQLCipher for at-rest encryption, SVR with Intel SGX attestation, IME_FLAG_NO_PERSONALIZED_LEARNING (keyboard can't index your messages), zero third-party trackers.

    Wire: Kotlin/Ktor, no hardened native core (more accessible to Frida), no SQLCipher (messages extractable in plaintext on rooted devices), no post-quantum, Segment SDK for behavioural telemetry.

    But the finding that surprised me most:

    Wire APKs from unofficial stores (Uptodown et al.) contain additional tracking workers and ACCESS_SUPERUSER permission requests not present in the official build. Supply chain integrity is not a footnote — it's the threat model.

    Conclusion: Signal is the only one of the two suitable for threat models involving physical or administrative device compromise.

    soon the full paper

    #infosec #AndroidSecurity #Signal #Wire #ReverseEngineering #mobileforensics #supplychain #MASA

  16. Signal vs Wire — binary analysis of both APKs (apktool, strings, ELF inspection).

    The gap is larger than most people think:

    Signal: Rust core (libsignal_jni.so), Kyber-1024 post-quantum hybrid ratchet, SQLCipher for at-rest encryption, SVR with Intel SGX attestation, IME_FLAG_NO_PERSONALIZED_LEARNING (keyboard can't index your messages), zero third-party trackers.

    Wire: Kotlin/Ktor, no hardened native core (more accessible to Frida), no SQLCipher (messages extractable in plaintext on rooted devices), no post-quantum, Segment SDK for behavioural telemetry.

    But the finding that surprised me most:

    Wire APKs from unofficial stores (Uptodown et al.) contain additional tracking workers and ACCESS_SUPERUSER permission requests not present in the official build. Supply chain integrity is not a footnote — it's the threat model.

    Conclusion: Signal is the only one of the two suitable for threat models involving physical or administrative device compromise.

    soon the full paper

    #infosec #AndroidSecurity #Signal #Wire #ReverseEngineering #mobileforensics #supplychain #MASA

  17. Static + dynamic analysis of Signal's APK. The good news first: Signal is genuinely exceptional.

    Rust core (libsignal_jni.so), post-quantum hybrid Double Ratchet (Kyber-1024 + X25519), Direct ByteBuffers with immediate zeroing after PIN/username hashing, Intel SGX attestation for SVR — MREnclave verification means even a compromised Signal server can't extract your PIN hash.

    But two things stood out:

    1. Firebase is always there. Google receives IP + notification timestamps regardless of message content. If you need metadata privacy, Signal still leaks presence data to Google's infrastructure.

    2. Certificate revocation endpoints hit g.symcd.com in plaintext. An ISP or state-level observer can fingerprint Signal usage from DNS queries and HTTP traffic to those CAs — without touching message content.

    Conclusion: strongest crypto engineering in consumer messaging. The attack surface isn't the cryptography. It's the operational dependencies.

    Soon the full analysis

    #infosec #AndroidSecurity #Signal #privacy #ReverseEngineering #postquantum #mobileforensics

  18. Static + dynamic analysis of Signal's APK. The good news first: Signal is genuinely exceptional.

    Rust core (libsignal_jni.so), post-quantum hybrid Double Ratchet (Kyber-1024 + X25519), Direct ByteBuffers with immediate zeroing after PIN/username hashing, Intel SGX attestation for SVR — MREnclave verification means even a compromised Signal server can't extract your PIN hash.

    But two things stood out:

    1. Firebase is always there. Google receives IP + notification timestamps regardless of message content. If you need metadata privacy, Signal still leaks presence data to Google's infrastructure.

    2. Certificate revocation endpoints hit g.symcd.com in plaintext. An ISP or state-level observer can fingerprint Signal usage from DNS queries and HTTP traffic to those CAs — without touching message content.

    Conclusion: strongest crypto engineering in consumer messaging. The attack surface isn't the cryptography. It's the operational dependencies.

    Soon the full analysis

    #infosec #AndroidSecurity #Signal #privacy #ReverseEngineering #postquantum #mobileforensics

  19. Static + dynamic analysis of Signal's APK. The good news first: Signal is genuinely exceptional.

    Rust core (libsignal_jni.so), post-quantum hybrid Double Ratchet (Kyber-1024 + X25519), Direct ByteBuffers with immediate zeroing after PIN/username hashing, Intel SGX attestation for SVR — MREnclave verification means even a compromised Signal server can't extract your PIN hash.

    But two things stood out:

    1. Firebase is always there. Google receives IP + notification timestamps regardless of message content. If you need metadata privacy, Signal still leaks presence data to Google's infrastructure.

    2. Certificate revocation endpoints hit g.symcd.com in plaintext. An ISP or state-level observer can fingerprint Signal usage from DNS queries and HTTP traffic to those CAs — without touching message content.

    Conclusion: strongest crypto engineering in consumer messaging. The attack surface isn't the cryptography. It's the operational dependencies.

    Soon the full analysis

    #infosec #AndroidSecurity #Signal #privacy #ReverseEngineering #postquantum #mobileforensics

  20. Static + dynamic analysis of Signal's APK. The good news first: Signal is genuinely exceptional.

    Rust core (libsignal_jni.so), post-quantum hybrid Double Ratchet (Kyber-1024 + X25519), Direct ByteBuffers with immediate zeroing after PIN/username hashing, Intel SGX attestation for SVR — MREnclave verification means even a compromised Signal server can't extract your PIN hash.

    But two things stood out:

    1. Firebase is always there. Google receives IP + notification timestamps regardless of message content. If you need metadata privacy, Signal still leaks presence data to Google's infrastructure.

    2. Certificate revocation endpoints hit g.symcd.com in plaintext. An ISP or state-level observer can fingerprint Signal usage from DNS queries and HTTP traffic to those CAs — without touching message content.

    Conclusion: strongest crypto engineering in consumer messaging. The attack surface isn't the cryptography. It's the operational dependencies.

    Soon the full analysis

    #infosec #AndroidSecurity #Signal #privacy #ReverseEngineering #postquantum #mobileforensics