skip to content

LinRT · Knowledge base · LinRT 5.x

LinRT Technical Wiki

Real-Time Linux Yocto BSP documentation for engineers and integrators.

REAL-TIME EXECUTION CHOICES
OXYGEN Linux · PREEMPT_RT COBALT Xenomai 3 · RTDM TUNGSTEN Xenomai 4 · EVL
YOCTO LTS   •   NXP i.MX   •   CRA EVIDENCE
LinRT WikiLinRT 5.xen:source-access
Documentation

Accessing LinRT BSP source repositories

Public guide — subscriber onboarding, SSH key registration and Git/Repo access to LinRT Yocto BSP sources.

Source access: overview

Source access: overview

Figure: account activation and SSH access workflow. Every step requires the corresponding subscription authorization.

Who can request access?

After subscription approval, the customer-designated users (one to three maximum, depending on the subscribed support plan) are invited individually by LinRT HelpDesk. Access is nominative and limited to the repositories and branches authorized for that subscription. A HelpDesk account alone does not grant Git repository access.

1. Activate your LinRT HelpDesk account

Each designated user receives an invitation email from LinRT Support/HelpDesk. Follow its account activation link, set a personal password and complete your profile. If the email is missing, check your spam folder and contact LinRT Support using the official portal. Do not share your HelpDesk password.

LinRT HelpDesk ↗

2. Prepare your workstation

The examples below apply to Linux or macOS terminals and Git Bash on Windows when OpenSSH is available. Install Git, OpenSSH and (for multi-repository Yocto checkouts) the Google Repo tool. Check that Git and SSH are installed:

ssh -V
git --version

3. Create a dedicated SSH key pair

Use one personal key pair per authorized user and preferably per workstation. The current LinRT HelpDesk ticket is named “RSA Key soumission”; this example uses RSA 4096 bits. Bitbucket Cloud also supports Ed25519, but request LinRT approval before choosing a different key type. Set a strong passphrase when prompted. Do not overwrite an existing key.

mkdir -p "$HOME/.ssh"
chmod 700 "$HOME/.ssh"
ssh-keygen -t rsa -b 4096 -C "user@company.example" -f "$HOME/.ssh/linrt_bitbucket"

This creates a private key linrt_bitbucket (keep it secret) and a public key linrt_bitbucket.pub (shareable). Load the private key into the SSH agent for your local session:

eval "$(ssh-agent -s)"
ssh-add "$HOME/.ssh/linrt_bitbucket"

4. Open a HelpDesk ticket: RSA Key soumission

Sign in to the LinRT HelpDesk and create a ticket under the topic RSA Key soumission. Supply the subscribing company, the authorized user’s registered email address and the entire single line from the .pub file. Optionally include its SHA256 fingerprint. Never send the private key, passphrase, password or a complete .ssh directory.

cat "$HOME/.ssh/linrt_bitbucket.pub"
ssh-keygen -lf "$HOME/.ssh/linrt_bitbucket.pub"

5. Wait for LinRT Support confirmation

LinRT Support reviews the request, installs/registers the submitted public key on the LinRT Bitbucket service and confirms when the key and relevant repository permissions have been enabled. The ticket response is the signal to start testing; key registration and repository authorization are separate checks.

6. Test the SSH connection

Connect to Bitbucket using the private key that matches the submitted .pub file. On first connection, check the server host-key fingerprint against Atlassian’s official reference before accepting it.

ssh -T -i "$HOME/.ssh/linrt_bitbucket" -o IdentitiesOnly=yes git@bitbucket.org

A successful Bitbucket Cloud response normally includes:

authenticated via ssh key. You can use git to connect to Bitbucket.
Shell access is disabled

“Shell access is disabled” is expected: Bitbucket provides Git over SSH, not an interactive shell. Successful SSH authentication does not by itself prove access to every private LinRT repository. Verify access to your authorized manifest repository:

git ls-remote git@bitbucket.org:linrt/linrt-multifb-oxygen-manifest.git

7. Retrieve the manifest repository

For example, the LinRT Oxygen manifest repository can be cloned over HTTPS. Important: HTTPS Git authentication is separate from SSH key authentication. This command retrieves the manifest Git repository only, not the complete Yocto source tree:

git clone https://bitbucket.org/linrt/linrt-multifb-oxygen-manifest.git

If SSH access is the approved method, use the SSH URL for this repository instead:

git clone git@bitbucket.org:linrt/linrt-multifb-oxygen-manifest.git

8. Initialize and synchronize Yocto sources with Repo

The Repo tool reads the manifest and retrieves the listed Git projects. Run the following in a new empty working directory. The example uses the manifest default branch; for a specific LinRT Oxygen 5.x/6.x release, use the manifest branch and XML file explicitly supplied by LinRT Support. Do not guess a branch name.

mkdir -p "$HOME/linrt/oxygen-sources"
cd "$HOME/linrt/oxygen-sources"
repo init -u git@bitbucket.org:linrt/linrt-multifb-oxygen-manifest.git
repo sync -j4

The manifest can point to multiple remotes, each of which must be accessible using its configured protocol and the user’s permissions. An HTTPS manifest clone does not configure SSH access to these remotes automatically.

Quick verification checklist

  • HelpDesk user activated
  • Public key submitted via RSA Key soumission ticket
  • Support has confirmed key registration
  • SSH test succeeds
  • Authorized manifest repository is readable
  • Repo synchronization uses the approved manifest branch

Troubleshooting

  • Permission denied (publickey): verify that LinRT confirmed key registration; inspect loaded identities and retry with the designated private key. If necessary open a HelpDesk ticket.
  • SSH succeeds, but Git says repository not found / access denied: verify the exact repository URL and that Support granted access to this repository/branch.
  • HTTPS clone requests a username or token: the SSH key is not used for HTTPS. Use the SSH clone URL or follow the approved HTTPS authentication procedure.
  • Host key verification failed: stop and check the official Bitbucket host fingerprints. Do not bypass verification.
  • repo sync fails on one project: check that the manifest and branch are supported and that you have permission for every referenced private repository; attach sanitized errors to your HelpDesk ticket.

Security and account lifecycle

Only public keys are submitted. Protect private keys with a passphrase, avoid shared user accounts, remove old workstation keys and notify HelpDesk when an authorized user leaves the project or access must be revoked. The HelpDesk password and the Bitbucket SSH key serve different purposes.

Official references


Published as a public onboarding guide. Actual repository/branch availability depends on the customer subscription and LinRT Support authorization.

LinRT HelpDesk ↗ · Wiki

en/source-access.txt · Last modified: by 127.0.0.1