I'm working on setting up an OPKG repository to be used by embedded linux devices. We'd like to secure the server so that only our devices have access to the packages. I couldn't find any information on how to do this other than some references to http proxy username and passwords. Is there a way this can be achieved? I believe opkg repositories use the same system as ipkg.
You can download packages from a local or a remote Opkg repository. To c reate a new local repository that supports Opkg, in the Administration module, go to Repositories | Repositories | Local and set the Package Type to Opkg. Artifactory supports the common Opkg index scheme which indexes each feed location according to all ipk packages in it.
As a fully-fledged Opkg repository, Artifactory generates index files that are fully compliant with the Opkg client. The ability to provision ipk packages from Artifactory to an Opkg client from local and remote repositories.
The opkg utility is the lightweight package manager used for this job. Opkg is a fork of ipkg, the package manager used in NSLU2's Optware, which is designed to add software to stock firmware of embedded devices. Opkg is a full package manager for the root file system, including kernel modules and drivers, while ipkg is just a way ...
Informational commands Options Examples Configuration Adjust repositories Change architectures Proxy support Troubleshooting Verbose opkg update Out of space Local repository Non-standard installation destinations Opkg package manager
You don't really need to modify the sources - compiling OPKG with libcurl
will enable http basic auth: ./configure --enable-curl
before running make
In opkg.conf just add option http_auth user:pass
and it works.
I remember seeing this change was added some time ago - don't recall when or which version but it works with the latest.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With