Skip to content

serialization: obfuscate the serialized search paths #40357

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

Merged
merged 1 commit into from
Dec 1, 2021

Conversation

nkcsgexi
Copy link
Contributor

@nkcsgexi nkcsgexi commented Dec 1, 2021

We noticed some Swift clients rely on the serialized search paths in the module to
find dependencies and dropping these paths altogether can lead to build failures like
rdar://85840921.

This change teaches the serialization to obfuscate the search paths and the deserialization
to recover them. This allows clients to keep accessing these paths without exposing
them when shipping the module to other users.

We noticed some Swift clients rely on the serialized search paths in the module to
find dependencies and droping these paths altogether can lead to build failures like
rdar://85840921.

This change teaches the serialization to obfuscate the search paths and the deserialization
to recover them. This allows clients to keep accessing these paths without exposing
them when shipping the module to other users.
@nkcsgexi nkcsgexi requested review from xymus and artemcm December 1, 2021 19:48
@nkcsgexi
Copy link
Contributor Author

nkcsgexi commented Dec 1, 2021

@swift-ci please smoke test

@nkcsgexi nkcsgexi merged commit 03d5a6a into swiftlang:main Dec 1, 2021
@compnerd
Copy link
Member

compnerd commented Dec 2, 2021

This seems to have regressed the Windows build: https://ci-external.swift.org/job/oss-swift-windows-x86_64-vs2019/7280/consoleText

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

Successfully merging this pull request may close these issues.

2 participants