Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Profile B #701

Open
FatimaaIsmail27 opened this issue Apr 16, 2024 · 4 comments
Open

Profile B #701

FatimaaIsmail27 opened this issue Apr 16, 2024 · 4 comments

Comments

@FatimaaIsmail27
Copy link

Hello,
while I was trying to implement profile A and profile B schemes, I changed the configuration in free5gc-ue.yaml in UERANSIM and chose protection scheme 1 and profile A was implemented successfully.. when I tried profile B, I got the following error:
image
So profile B is not implemented in UERANSIM?

Thank you in advance..

@random1337-infosec
Copy link

Hi.

I am also facing the same problem as you, specifically with Profile A. I am not sure if there has been any recent code modification in UERANSIM because some people have previously got it to work (?).

Can you share what OpenSSL version you use for key generation? openssl verison

Based on what I can see, the SUCI feature in UERANSIM has not been modified. I am tagging @Stg22, who merged the profile A feature to UERANSIM if he can provide some insight.

@FatimaaIsmail27
Copy link
Author

Hi @random1337-infosec , are you using open5gs or free5gc?
I actually tried profile A with open5gs but I got "Sementically Incorrect Message" error and I couldn't fix it.. So I used free5gc and it worked fine..
As for free5gc, I didn't generate any new keys, they are already stored in udm. I just changed the protection scheme.

@priyanshs
Copy link

@FatimaaIsmail27 @random1337-infosec You may want to checkout the configuration method here: https://github.com/s5uishida/note_5g_suci_profile_ab

Hope this helps, I was able to get open5gs-UERANSIM with Profile A.

@Stg22
Copy link
Contributor

Stg22 commented Apr 18, 2024

Profile B is not implemented, only Profile A is available.
Keys set in the configuration file was not generated by OpenSSL. It was taken from the 3GPP document TS.33.501 in the section C.4.3 (Implementers’ test data).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants