Updates for Proxmox VE 3.1 - including Comodo signed Java VNC applet

martin

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
754
1,740
223
We just uploaded some packages, containing bug fixes and small improvements. Most important, we signed our Java VNC applet with a Comodo code sign cert. This means, you do not get the annoying Java security warning anymore when you run the Java VNC applet - Make sure you run latest Oracle Java 7u45 (or latest icedtea7-plugin if you are on a Linux Desktop).

A big Thank-you to our active community for all feedback, testing, bug reporting and patch submissions.

Release Notes

- vncterm (1.1-6)

  • use Comodo code sign cert for applet signature
  • set Caller-Allowable-Codebase and remove Trusted-Library. This avoids security popups with latest Java 7u45. Also see: http://stackoverflow.com/questions/19393826/java-applet-manifest-allow-all-caller-allowable-codebase
- pve-manager (3.1-24)

  • fix IP address parser for OpenVZ containers
  • fix UPID parser for long uptimes (> 497 days)
  • subscription updates: set UserAgent header on proxy connect request
  • correctly set content type for GUI index page
  • allow to add ipv6 address to OpenVZ containers
  • spice: ignore the case of the characters in hostname match
- libpve-access-control (3.0-8)

  • spice: use lowercase hostname in ticktet signature
- libpve-common-perl (3.0-9)

  • export regular expressions for IPv4 and IPv6 addresses
  • fix upid parser for long uptimes (> 497 days)
  • do not use 'intl' variant for en an gb keyboard layouts
- libpve-storage-perl (3.0-18)
  • ZFS plugin: add support for istgt

Updates can be applied via GUI or via apt as usual (no reboot necessary).

__________________
Best regards,

Martin Maurer
Proxmox VE project leader
 
martin said:
Updates can be applied via GUI or via apt as usual (no reboot necessary).
Click to expand...

Thanks guys for your commitment in always improving an already very good software... and for listening the community :)

I'm trying the new 3.1, and saw the node > updates section, now I can check "release log" for each update: great!
How does the "upgrade" button behave? will it upgrade all together (like an apt-get upgrade) or only the selected update (like the release log button) ?

Marco
 
thanks for that java-related upgrade. now if only HP would upgrade their ILO applets.....
 
no. I got them on my testing 3.1 node, with community repos
as i got it, entreprise repos (stable) get updates AFTER they go into community repos (testing)

Marco
 
I'm running the latest version of proxmox and java (7u45) but I still got the warning when I launch the console on the webinterface :
Java warning:
java.PNG


Java :
java_version.PNG

Proxmox :
pveversion --verbose
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-23-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
 
Update fails

starting apt-get update
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://ftp.ca.debian.org wheezy Release.gpg
Hit http://ftp.ca.debian.org wheezy Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://ftp.ca.debian.org wheezy/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
Hit http://ftp.ca.debian.org wheezy/contrib amd64 Packages
Hit http://ftp.ca.debian.org wheezy/contrib Translation-en
Hit http://ftp.ca.debian.org wheezy/main Translation-en
Ign https://enterprise.proxmox.com wheezy Release.gpg
Ign https://enterprise.proxmox.com wheezy Release
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages The requested URL returned error: 401

E: Some index files failed to download. They have been ignored, or old ones used instead.
TASK ERROR: command 'apt-get update' failed: exit code 100



Is there something I can do? Or, do I just try again later?
 
Unless you have a subscription to support, you should not have pve enterprise repos.

Sent from my Nexus 5
 
Dear All,

The Master ISO of Proxmox 3.1 is contain corrupt file in \var\lib\dpkg\info\dconf-gsettings-backend:amd64.list
do you have check this ?

Regards,

Agus S
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back