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

Rename paket.locked file to .processlock to avoid McAfee scanner to evaluate the file as threat #3586

Conversation

mjirous
Copy link

@mjirous mjirous commented May 28, 2019

Files ending with *.locked extension are treated by McAfee as ransomware. It's not always easy to get the file to Whitelist (especially in big companies) and therefore it is much easier to simply rename the file causing troubles.

I renamed the file paket.locked to .processlock as suggested by @forki

The original discussion is here: #3535

@@ -24,7 24,7 @@ let [<Literal>] BootstrapperFileName = "paket.bootstrapper.exe"
let [<Literal>] PaketFileName = "paket.exe"
let [<Literal>] TargetsFileName = "paket.targets"
let [<Literal>] ReferencesFile = "paket.references"
let [<Literal>] AccessLockFileName = "paket.locked"
let [<Literal>] AccessLockFileName = ".processlock"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be paket.processlock - just in case people have gitignore rules like paket.* (even if this file is not really important for git)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't worry. will do that right now

@forki forki merged commit b6eeb4f into fsprojects:master May 28, 2019
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.

None yet

2 participants