mirror of
https://github.com/tytydraco/LADB.git
synced 2026-04-27 00:15:59 +03:00
[GH-ISSUE #78] Why not using an ADB implementation like Dadb? #60
Labels
No labels
bug
documentation
enhancement
enhancement
good first issue
help wanted
pull-request
question
question
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LADB#60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sharpordie on GitHub (Jul 25, 2022).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/78
I wanted to ask you why you don't use an ADB implementation for LADB? Is it really better to use a binary compiled by "a guy" and that is only compatible with some ARM processors?
I am concerned about the security aspect and I would like to know if there are real benefits over libraries like Dadb?
@teou1 commented on GitHub (Oct 14, 2022):
https://github.com/mobile-dev-inc/dadb - it looks very interesting indeed.
2 notes however: at the time ladb started, dadb was still not born, so there wasn't really a choice back then. And the guy that compiled the adb binary back then 2 years ago is a more than respectable developer with a reputation, he is not "some guy", he is working on the things and roms at low level so i wouldn't worry about virus in the binary. I had the same concerns and i did my own little research.
@tytydraco commented on GitHub (Oct 15, 2022):
DADB is cool but for now sadly, it does not support Android 11's pairing mechanism yet. Let's reopen this issue when that functionality gets added. But it is very promising!