Social

How to Install and use ADB, the Android Debug Bridge utility

Step One: Download Platform Tools

Head to the Android SDK Platform Tools download page. Select the link for your operating system from the “Downloads” section. This will download a ZIP file, which you can unzip wherever you want to store the ADB files—they’re portable, so you can put them anywhere you want.

That’s all we have to do for now. Just make sure to remember where you unzipped the files, we will need to access them later. I put mine at “C:\platform-tools” to keep things simple.

Step Two: Enable USB Debugging on your Phone

To use ADB with your Android device, you must enable a feature called “USB Debugging.” Open your phone’s app drawer, tap the Settings icon, and select “About Phone.” Scroll all the way down and tap the “Build Number” item seven times. You should get a message saying you are now a developer.

Head back to the main Settings page, and you should see a new option in the System section called “Developer Options.” Open that and enable “USB Debugging”.

Later on, when you connect your phone to your computer, you’ll see a popup titled “Allow USB Debugging?” on your phone. Check the “Always allow from this computer” box and tap OK.

Step Three: Test ADB and install your Phone’s Drivers

Open the Command Prompt (PowerShell and Terminal will also work) and change the directory to where you unzipped the file earlier. You can do this by entering the command below. Replace the file destination with your own:

cd C:\platform-tools

To test whether ADB is working properly, connect your Android device to your computer using a USB cable and run the following command:

adb devices

If you’re using PowerShell or the Terminal with a PowerShell profile, you’ll need to run ./adb devices instead. You should see a device in the list. If your device is connected but nothing appears in the list, you’ll need to install the appropriate drivers.

In the vast majority of cases, your PC will automatically detect your phone and set it up with the appropriate drivers. If that doesn’t happen, you can usually find the drivers for your device from the XDA Developers forums or your manufacturer’s website. The drivers for Google devices, like Pixel phones, can be found on Google’s website. Google also has a list of USB drivers sorted by manufacturer that will save you a ton of time.

Make sure to carefully follow the instructions for installing your device’s drivers if specific instructions are provided.

If you download the drivers manually, you may have to force Windows to find them on your device. Open the Device Manager (click Start, type Device Manager, and press Enter), locate your device, right-click it, and select “Properties.” You may see a yellow exclamation mark next to the device if its driver isn’t installed properly.

  • On the Driver tab, click “Update Driver”
  • Use the Browse my computer for driver software option.
  • Find the drivers you downloaded for your device.

If you downloaded the drivers from your OEM or Google, look for an executable or INF file in the drivers folder.Once you’ve installed your device’s drivers, plug in your phone and try the adb devices command again:

adb devices

Or:

./adb devices

If all went well, you should see your device in the list, and you are ready to start using ADB! If running adb devices still won’t return any devices, there are a few things you can try:

  • Swap out your USB cable for a higher quality one
  • Plug the USB cable into a different port
  • Plug the USB cable directly into the USB ports on your motherboard (at the back), rather than the ports on the front of your PC or on a USB hub.
  • Change your phone’s USB mode to PTP, MTP (File Transfer/Android Auto), or USB Tethering.

Step Four (Optional): Add ADB to your System PATH

As it stands, you have to navigate to ADB’s folder and open a Command Prompt there whenever you want to use it. However, if you add it to your Windows System PATH, that won’t be necessary—you can just type adb from the Command Prompt to run commands whenever you want, no matter what folder you’re in.

In addition to the variety of tricks that require ADB, ADB offers some useful commands:

Command Function
adb install C:\package.apk Installs the package located at C:\package.apk on your computer on your device.
adb uninstall package.name Uninstalls the package with package.name from your device. For example, you’d use the name com.rovio.angrybirds to uninstall the Angry Birds app.
adb push C:\file /sdcard/file Pushes a file from your computer to your device. For example, the command here pushes the file located at C:\file on your computer to /sdcard/file on your device
adb pull /sdcard/file C:\file Pulls a file from your device to your computer—works like adb push, but in reverse.
adb logcat View your Android device’s log. Can be useful for debugging apps.
adb shell Gives you an interactive Linux command-line shell on your device.
adb shell command Runs the specified shell command on your device.

If you’re looking to get more details about the things you can do with ADB, consult the Android Debug Bridge page on Google’s Android Developers site. It goes through the arguments and syntax in enough detail to get you started.

[mai mult...]

Ce este DSRM (Directory Services Restore Mode) în Active Directory și de ce este important dpdv al securității

Directory Services Restore Mode/Modul de restaurare a serviciilor de director(DSRM) este un mod special de pornire pentru controlerele de domeniu Windows Server, care permite administratorilor să efectueze sarcini de întreținere în baza de date Active Directory.

Acest mod este utilizat în principal pentru restaurarea sau repararea bazei de date atunci când aceasta este coruptă sau întâmpină probleme. DSRM este esențial pentru sarcini precum restaurarea Active Directory, recuperarea parolei, repararea bazei de date, restaurarea autoritară, recuperarea stării sistemului, respectiv depanarea sau diagnosticarea.

Prin utilizarea DSRM, administratorii pot asigura starea de sănătate și integritatea mediului Active Directory, permițând capacități robuste de recuperare în caz de dezastru și întreținere.

[mai mult...]

Retro-Computing in 2025: why old Machines are cool again

Retro-computing isn’t new. Enthusiasts have been restoring and emulating old systems for decades. But 2025 is different: retro machines are gaining serious attention in education, cybersecurity, and even enterprise experiments.

Reasons for the rise:

  • Educational value: Old systems strip computing down to the basics, forcing students to understand how hardware and software truly interact.

  • Security testing: Legacy protocols and systems still exist in industries like healthcare, aviation, and banking. Learning how they work helps modern engineers defend against vulnerabilities.

  • Cultural nostalgia: Just like vinyl records or vintage cameras, classic computers have aesthetic and cultural appeal.

Examples of Retro Systems in use

  • DEC VAX and PDP-11: Being revived in universities for teaching operating system concepts.

  • Commodore 64 & Amiga: Used in creative coding workshops to inspire young developers with pixel art and chiptune music.

  • IBM Mainframes (emulated): Explored by enterprises who still depend on legacy COBOL applications.

Even emulators like SIMH or FPGA recreations allow old hardware to live on in modern labs.

Why It Matters in 2025

  1. Bridging Generations – New engineers learn how computing evolved, while veterans pass on hard-earned knowledge.

  2. Cybersecurity Relevance – Many cyberattacks target outdated protocols. Training on retro systems builds better defenders.

  3. Sustainable Tech – Repurposing and emulating old systems fits into the global push for reducing electronic waste.

  4. Fun Factor – Let’s be honest: there’s something cool about coding on a green monochrome screen.

Some researchers argue retro-computing could play a role in resilient computing. Older machines are simpler, less dependent on cloud infrastructure, and in some cases more robust against modern attacks. In an age of supply chain concerns and AI-driven vulnerabilities, there’s value in “dumb but safe” machines.

[mai mult...]

When the Autopilot Fails: the Hidden Risks of AI in 2025

Artificial intelligence has rapidly become the co-pilot of our digital lives. From autonomous vehicles to automated cybersecurity tools and even AI-assisted air traffic systems, machine learning models are making decisions that directly impact safety, privacy, and trust. But as discussions at FrOSCon 2025 reminded us this August, AI autopilot systems are not foolproof — and their failures can have real consequences.

The concept of “autopilot” AI is appealing: machines that can drive us home, manage data center workloads, or automatically detect and block cyberattacks. Companies market these solutions as time-savers and risk reducers, arguing that automation removes human error from critical processes.

For example:

  • Autonomous vehicles are being tested globally with promises of safer roads.

  • Cybersecurity AI can respond to threats in milliseconds, far faster than human analysts.

  • Airline autopilot systems, already heavily AI-driven, are expanding to manage complex navigation with minimal pilot input.

What experts warn, however, is that AI doesn’t fail in the same way humans do.

  • Black-box logic: Many autopilot algorithms make decisions in ways that are not transparent. When something goes wrong, investigators struggle to explain why.

  • Edge cases: AI systems are trained on data, but rare scenarios — a child running onto the road, or an unusual cyberattack pattern — can confuse the model.

  • Overtrust: Humans tend to trust AI too much, leading to slower reactions when the system misses a critical threat.

In cybersecurity, this can mean that a false sense of security leaves networks open to breaches. In autonomous vehicles, it can literally cost lives.

Recent Incidents Highlight the Risk

While regulators haven’t yet published full reports for 2025, analysts point to multiple cases of autopilot misbehavior this year:

  • A self-driving taxi in San Francisco failed to recognize a construction worker’s hand signals, leading to a near collision.

  • An AI-driven stock trading bot in Asia executed a series of flawed trades after misclassifying a news headline, wiping millions off the market in minutes.

  • A European hospital’s AI monitoring system mistakenly flagged normal patient activity as critical, overwhelming staff with false alerts.

Each case highlights the same issue: AI is only as good as its training data and the safeguards around it.

Building Trustworthy Autopilot Systems

Experts suggest several ways to reduce risk:

  1. Human-in-the-loop – Keep humans actively supervising AI decisions, not just “on standby.”

  2. Explainability – Demand that AI vendors provide clearer reasoning for system outputs.

  3. Rigorous Testing – Test systems in extreme, rare, and adversarial conditions before deployment.

  4. Fail-safe modes – Ensure that when AI systems fail, they revert to safe defaults rather than risky behavior.

The Bottom Line

AI autopilot systems will continue to grow across industries in 2025 and beyond. But as appealing as they sound, they are not replacements for human judgment. The future of safe automation will depend not only on smarter algorithms but also on the humility to recognize AI’s limits.

In other words: the autopilot may be intelligent, but the pilot still matters.

[mai mult...]