Such access tokens are best placed into files which can be accessed only by processes that need them, same as private ssh keys. What executable is using it, specifically and with which protocol?
Alex On Thu, 13 Apr 2023 at 21:54, Philippe Lafontaine via lists.yoctoproject.org <[email protected]> wrote: > > Greeting, > > I have a recipe that fetch a pre-built binary from a build machine using an > access token. Every developer will have different access token, for obvious > reason. Therefore, the token cannot be hard coded in the recipe. > > > > Our current build setup uses a docker container (crops/poky). Our current > solution looks like this: > > > > The host OS has an environment variable containing the access token. This > token is then shared with the docker container. > > > > Once the yocto environment is source we: > > export ="$BB_ENV_PASSTHROUGH_ADDITIONS PRIVATE_TOKEN_GIT" > > where PRIVATE_TOKEN_GIT is the access token > > While this strategy does work. We were wondering if there was a better way of > doing this. > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59710): https://lists.yoctoproject.org/g/yocto/message/59710 Mute This Topic: https://lists.yoctoproject.org/mt/98248615/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
