If any of you have tried to use the PC-BSD Translation / Pootle web interface in the last year you probably don’t have a lot of good things to say about it. A 35 word translation might take you a good 30 minutes between the load times (if you could even login to the site without it timing out). Thankfully those days are behind us! PC-BSD has upgraded their translation system to use Pootle version 18.104.22.168 and it is blazingly fast. I went through localizing a small 35 word applet for PC-BSD and it took me roughly 4 minutes compared to what would have taken at least half an hour before due to the slowness of the old pootle software. Check out the new translation site at translate.pcbsd.org.
There’s a couple of things you are going to want to keep in mind about the new translation system. You will have to create a new account. Upgrading Pootle directly was proving disastrous so we exported all the strings and imported them into the new Pootle server. What this means is no accounts were transferred since a direct upgrade was not done. This also means that the strings that were brought in also appear as “fuzzy” translations. If you have some free time you can help by going to the translation site and approving some of the fuzzy translations. Many languages have already been done they just need to be reviewed and marked as acceptable (uncheck the fuzzy box if you are 100% certain on the translation).
I hope you guys are as excited as I am over the new translation possibilities! For more information on how you can help with localization / translating contact me at firstname.lastname@example.org.
Hey guys check out our video on KDEConnect in PC-BSD on YouTube! It’s an awesome new app that allows you to receive text messages, phone notifications, incoming calls notifications, media remote control, and more!
Hey everyone just a quick heads up we’ve just started a PC-BSD YouTube channel! If you want to check it out you can follow this link https://www.youtube.com/channel/UCyd7MaPVUpa-ueUsGjUujag. Don’t forget to subscribe for new videos and if you have a video or tutorial you’d like to submit send it my way! We only have a couple videos right now so we need your help to grow our channel :). Also we’d love for you to submit your ideas we can do for videos in the future.
As many of you are probably aware, there is a serious security issue that is currently all over the web regarding the GNU BASH shell. We at the PC-BSD project are well aware of the issue, a fix is already in place to plug this security hole, and packages with this fix are currently building. Look for an update to your BASH shell within the next 24 hours in the form of a package update.
As a side note: nothing written by the PC-BSD project uses BASH in any way — and BASH is not built-in to the FreeBSD operating system itself (it is an optional port/package), so the level of severity of this bug is lower on FreeBSD than on other operating systems.
According to the FreeBSD mailing list: Bryan Drewery has already sent a notice that the port is fixed in FreeBSD. However, since he also added some good recommendations in the email for BASH users, we decided to copy that email here for anyone else that is interested.
From: Bryan Drewery — FreeBSD mailing list
The port is fixed with all known public exploits. The package is
However bash still allows the crazy exporting of functions and may still
have other parser bugs. I would recommend for the immediate future not
using bash for forced ssh commands as well as these guidelines:
1. Do not ever link /bin/sh to bash. This is why it is such a big
problem on Linux, as system(3) will run bash by default from CGI.
2. Web/CGI users should have shell of /sbin/nologin.
3. Don’t write CGI in shell script / Stop using CGI
4. httpd/CGId should never run as root, nor “apache”. Sandbox each
application into its own user.
5. Custom restrictive shells, like scponly, should not be written in bash.
6. SSH authorized_keys/sshd_config forced commands should also not be
written in bash.
For more information the bug itself you can visit arstechnica and read the article by clicking the link below.
31 — Warden CLI upgrade + IRC Announcement">PC-BSD Feature Digest 31 — Warden CLI upgrade + IRC Announcement
Hey everyone! After a brief hiatus from feature updates we are back! We’ve switched from Fridays to Mondays and rather than trying to get an update out every week we aren’t on a specific schedule. We will continue to push out these feature updates when we have some cool new features come out we think you’ll want to know about.
The Warden and PBI_add backend (CLI) management tools have received some exciting new features we’d like to tell you about. You can now create jails on the fly when adding a new PBI to your application library. For instance say you’re adding a PBI using the “pbi_add” command and you want to install the PBI into a new jail that you haven’t created yet. You would specify: “sudo pbi_add –J apache” without the quotes to create a default named jail with the PBI apache installed directly into it. The –J being the new flag that specifies the creation of the new jail.
There’s also a new option now to do a bulk jail creation. By simply using the new –bulk and –ip4pool flag you can easily roll out your preset number of jails quickly and efficiently. To use this cool new feature just type: “warden create <jailname> –bulk 5 –ip4pool 192.168.0.2″ and voila you’ve got 5 brand spanking new jails created in no time starting at IP address 192.168.0.2 .
The PC-BSD team is now hanging out in IRC! Get involved in the conversation and come visit us on Freenode in channel #pcbsd. We look forward to seeing you there!