[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PKCS#7 signature not signed with a trusted key





On Mon, Mar 18, 2019 at 8:52 AM Miguel A. Vallejo <ea4eoz@gmail.com> wrote:
Yesterday the kernel was upgraded to 4.19.0-4 (4.19.28-2) and the
problem disappeared.



Miguel, thanks for the heads-up!  Kernel 4.19.0-4 (4.19.28-2) does seem to work okay. 

However, I must note that if I hadn't seen the post from Miguel I would not have known that the new kernel version was there. I was actually thinking it would be 4.19.0-5 (4.19.28-2), or even 5.0.2-1. 

Updating as normal didn't let me know:
doofus@doofus:~$ sudo aptitude -Pvvv update
Hit http://ftp.us.debian.org/debian unstable InRelease
                                         
Current status: 0 (+0) broken, 0 (+0) upgradable, 58940 (+0) new.

(Perhaps because I did: 

sudo aptitude purge linux-image-4.19.0-4-amd64

as soon as I saw the original problem?)       

As of now, I still get:

doofus@doofus:~$ sudo aptitude search linux-image
i A linux-image-4.19.0-2-amd64                  - Linux 4.19 for 64-bit PCs (signed)                    
i A linux-image-4.19.0-3-amd64                  - Linux 4.19 for 64-bit PCs (signed)                    
i   linux-image-4.19.0-4-amd64                  - Linux 4.19 for 64-bit PCs (signed)                    
p   linux-image-4.19.0-4-amd64-dbg              - Debug symbols for linux-image-4.19.0-4-amd64          
p   linux-image-4.19.0-4-amd64-unsigned         - Linux 4.19 for 64-bit PCs                             
p   linux-image-4.19.0-4-cloud-amd64            - Linux 4.19 for x86-64 cloud (signed)                  
p   linux-image-4.19.0-4-cloud-amd64-dbg        - Debug symbols for linux-image-4.19.0-4-cloud-amd64    
p   linux-image-4.19.0-4-cloud-amd64-unsigned   - Linux 4.19 for x86-64 cloud                           
p   linux-image-4.19.0-4-rt-amd64               - Linux 4.19 for 64-bit PCs, PREEMPT_RT (signed)        
p   linux-image-4.19.0-4-rt-amd64-dbg           - Debug symbols for linux-image-4.19.0-4-rt-amd64       
p   linux-image-4.19.0-4-rt-amd64-unsigned      - Linux 4.19 for 64-bit PCs, PREEMPT_RT                 
p   linux-image-amd64                           - Linux for 64-bit PCs (meta-package)                   
p   linux-image-amd64-dbg                       - Debugging symbols for Linux amd64 configuration (meta-
p   linux-image-amd64-signed-template           - Template for signed linux-image packages for amd64    
p   linux-image-cloud-amd64                     - Linux for x86-64 cloud (meta-package)                 
p   linux-image-cloud-amd64-dbg                 - Debugging symbols for Linux cloud-amd64 configuration 
p   linux-image-rt-amd64                        - Linux for 64-bit PCs (meta-package), PREEMPT_RT       
p   linux-image-rt-amd64-dbg                    - Debugging symbols for Linux rt-amd64 configuration (me


And:

doofus@doofus:~$ sudo aptitude search linux-image-4.19.0-4-amd64
i   linux-image-4.19.0-4-amd64                  - Linux 4.19 for 64-bit PCs (signed)                    
p   linux-image-4.19.0-4-amd64-dbg              - Debug symbols for linux-image-4.19.0-4-amd64          
p   linux-image-4.19.0-4-amd64-unsigned         - Linux 4.19 for 64-bit PCs  

It might have been better to name the new version 4.19.0-5?

But, checking further, synaptic did show 4.19.28-2 (upstream version number?) if you look closely.  And The Debian packages page shows the new version also.  

So, I think it would really be nice if the apt system would be more helpful in situations like this.

End of complaint.


Reply to: