WARNING: The following packages cannot be authenticated!
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
WARNING: The following packages cannot be authenticated!
Using Mint 17.3, I use k3b for burning. I needed to noralize the files. When I checked the box, I got a message that said it can't do that unless I install "normalize audio."
It showed I can get it by opening up a terminal and running,"sudo apt-get install normalize-audio". I did and got this,
Code:
sudo apt-get install normalize-audio
[sudo] password for xxxx:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libaudiofile1
Suggested packages:
mpg321
Recommended packages:
vorbis-tools flac
The following NEW packages will be installed:
libaudiofile1 normalize-audio
0 upgraded, 2 newly installed, 0 to remove and 9 not upgraded.
Need to get 148 kB of archives.
After this operation, 470 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
WARNING: The following packages cannot be authenticated!
libaudiofile1
Install these packages without verification? [y/N]
Should I be worried about the "WARNING: The following packages cannot be authenticated!"?
linux mint.
hmmm. (*)
i think you should use the graphical software updater (or whatever it's called) to update & upgrade your system.
does the error persist after that?
(*) it is not recommend to update your system with command line apt-get, because linux mint has its own secure updates mechanism...
You should stop and check the distro's support forums.
All of the packages produced by a distro should be digitally signed by the publisher of that distro. You should not install a package that comes from their site if it does not pass digital-signature verification.
However, you do need to make sure that your updater is up-to-date: that is to say, that it contains the most-recent set of digital public keys. (Perhaps the package has been legitimately signed using an authorized key that you do not yet have?)
If this is the case, then I suggest that you stop and open a support-ticket with the distro publisher, asking that the signature problem be checked. All packages ought to be properly signed, of course, but there are thousands of them . . .
Last edited by sundialsvcs; 10-03-2016 at 12:29 PM.
sundialcvs gave you a detailed answer with about 3 seperate things that should be done, and that is all?
it makes me wonder if you did any of these things at all, but call me misanthropic if you like.
anyhow, why don't you describe the process in much more detail, so that other people that have the same or similar problems can find this thread and apply the solutions?
sundialcvs gave you a detailed answer with about 3 seperate things that should be done, and that is all?
it makes me wonder if you did any of these things at all, but call me misanthropic if you like.
anyhow, why don't you describe the process in much more detail, so that other people that have the same or similar problems can find this thread and apply the solutions?
If you where misanthropic, I wouldn't call you that. I don't want to.
I got slammed with stuff, best friend is in the hospital, car problems, one of the three 3 things suggested take time, and has to rely on others. No control over that. Home now, going through emails.
Wish you where that supportive, of me, when I got no answers to other way bigger problems.
Thank you for backing up a fellow Linux user by getting me into gear.
linux mint.
hmmm. (*)
i think you should use the graphical software updater (or whatever it's called) to update & upgrade your system.
does the error persist after that?
(*) it is not recommend to update your system with command line apt-get, because linux mint has its own secure updates mechanism...
You're very welcome Chris. Here's what I see: extraneous ppa/sources.
Since libaudiofile1 is already installed it is interesting that
Code:
sudo apt-get install normalize-audio
identifies libaudiofile1 as both "NEW" and "extra".
Here's my estimate of the problem.
You have mixed repos, or a FrankenMint. No harm no foul. Stuff happens.
I'd run
Code:
mintsources
in terminal and it will prompt you for privilege escalation
I would then navigate to the PPAs tab and disable all foreign repos (They can remain, just disable them)
and lastly, hit the "update the cache" button/function.
During the "update the cache" routine, you get a new window and if it errors, it may be shown.
No worries.
the "update the cache" button is pretty much the same as
Code:
sudo apt-get update
Close Mintsources and in terminal you may see (ignore these...)
Code:
(gksu:16517): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",
(synaptic:16551): Gtk-CRITICAL **: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
It's a non-issue.
Now run in your terminal:
Code:
sudo apt-get install normalize-audio
If after the install is successful, don't be too hasty to re-enable those disabled repos.
This time enable one at a time and hit the "update the cache" button each time a new one is enabled and the problem
child should make itself known.
Please let us know.
Last edited by Habitual; 10-11-2016 at 08:26 AM.
Reason: emphasis on repo enable
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.