You are not logged in.

#1 2016-03-10 10:18:51

MrPeacock
Member
Registered: 2016-03-10
Posts: 17

How to implement a virusscan as a prepairing step in makepkg?

As AUR is potentialy dangerous in flavor of viruses it would be nice if sources are scanned as a preparing step of makepkg.

Any ideas how to implement such a feature?

Offline

#2 2016-03-10 10:27:07

null
Member
Registered: 2009-05-06
Posts: 398

Re: How to implement a virusscan as a prepairing step in makepkg?

Search for "on-access file scanning" with your favourite virus scanner. Most should support it (e.g. ClamAV or Sophos). They will scan your files when you access them.

Offline

#3 2016-03-10 11:04:20

MrPeacock
Member
Registered: 2016-03-10
Posts: 17

Re: How to implement a virusscan as a prepairing step in makepkg?

i dont want to run a on access scanner. For security reason it is better to scan files before installing an infected package.

Offline

#4 2016-03-10 11:24:44

TheChickenMan
Member
From: United States
Registered: 2015-07-25
Posts: 354

Re: How to implement a virusscan as a prepairing step in makepkg?

The AUR is [mostly] just source code with scripts to build it into packages. Read the PKGBUILDs and either read the source too or trust the developers.


If quantum mechanics hasn't profoundly shocked you, you haven't understood it yet.
Niels Bohr

Offline

#5 2016-03-10 11:59:36

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: How to implement a virusscan as a prepairing step in makepkg?

One option is to write a script which first downloads the sources, then scan the files and finally build the package.

$ makepkg -o
$ antivirus-scan
$ makepkg -ei

Moving to "Creating & Modifying Packages".

Offline

Board footer

Powered by FluxBB