Monthly Archives: February 2015

AVG

Connect, Click and Clean with AVG Cleaner for iOS

From the day you first turn it on, your iPhone or iPad slowly accumulates hidden clutter that take up storage space and negatively affect performance, especially on 16 or 32GB models.

If you have an iPhone or an iPad and are struggling to find space for all your pictures, music or movies, or just want to make space to install the latest operating system, AVG Cleaner for iOS can help.

Since there’s no way for an iOS app to clean up that clutter, you have to do it from your PC.

 

How to clean up your iOS device:

  • Install AVG Performance 2015 from this page. Once complete, click on Performance to launch the 2015 release of AVG PC TuneUp.
  • From here, click on Clean up iPhone, iPad and iPod touch.
  • Hit Scan Now and have a look at the results. To clean up your phone, hit the Clean Now
Video

How To Clean Up Your iOS Device

 

Note: in case anything goes wrong, you can always go to Rescue Center and restore the files.

Don’t worry: All we clean are cache files, temporary files, age-old system logs and thumbnail files you will no longer need.

 

How much space can you get back?

Just how much space can you clear up using our AVG Cleaner for iOS? Well results for each device will differ but in our internal labs we found 340 MB of files on an iPhone 6 that was only four weeks old.

340 MB of junk files cleaneda 4 week old iPhone 6 7.5 GB of junk files cleaned on a 1 year old iPad Air 712 MB of junk files cleaneda 9 months old iPod touch

 

Don’t forget: you can’t clean up these files from your phone, you have to use AVG Cleaner for iOS as part of AVG Performance 2015.

So what are you waiting for? Unlock the hidden potential of your iOS device with AVG Cleaner for iOS now! Download AVG Performance today.

AVG

Legacy Contacts and managing a Digital Legacy

Emails, photos, random postings… We all have a digital footprint and depending on your privacy settings, it’s available to many people including strangers.  Not to mention our passwords to accounts, and other digital assets, including financial ones. Who can access them when we pass on? What happens to the data?

In the world of Internet services, digital legacies and the policies around them have been murky at best.

Because of our position as a leading provider of security for data, devices and people this is an issue we at AVG have long been concerned about. And that’s why we’ve been focused on educating our users on this sensitive topic and advocating for people to provide a digital codicil to their wills, specifying a digital executor to act on their behalf.  (You can see our most recent article here. We also published an ebook dealing with digital death.

 

Today, different sites have different policies, and requirements vary on the actions that can be taken, and the forms of identification and proof that are required in case of a user’s death.  Twitter has a policy to deactivate accounts after six months of prolonged inactivity, but also will work with authorized individuals to delete a deceased user’s account and or certain imagery. Until last week, Facebook’s policy was to allow users to specify if they wanted to “memorialize” or permanently delete their accounts. Last Thursday, Facebook moved to a step further to allow account holders to appoint what it calls a “Legacy Contact” to manage their memorialized accounts.

Facebook legacy contact

 

You can read the full announcement here that Facebook released Feb. 12.

But briefly: Facebook now allows the appointee to write a post for your profile, and update your profile picture and cover photo. It also allows the appointee to respond to new friend requests, for example a friend who hadn’t been on Facebook at the time of the user’s death. The Facebook executor, however, can’t go back and delete material, log into the account or remove any of your friends.

In its statement, Facebook said: “By talking to people who have experienced loss, we realized there is more we can do to support those who are grieving and those who want a say in what happens to their account after death.”

The Facebook move is good news, in many ways, not the least of which is that it helps bring this important issue of Digital Legacy to the forefront in one of the largest social venues, where many of us are living our digital lives. It also recognizes that users need more control of their accounts, including deciding how they want them managed when they pass.

Digital legacy is something that everyone online needs to consider. No one wants to consider their own death, but as the physical world morphs into the digital, it’s a very important part of our legacies. One we shouldn’t ignore.

CentOS

CEBA-2015:0238 CentOS 6 emacs FASTTRACK BugFixUpdate

CentOS Errata and Bugfix Advisory 2015:0238 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0238.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
c5892aeea82a18c5d819a032c445dd0c61c22191ab92a0b9f7a05d4e3f73b2ed  emacs-23.1-28.el6.i686.rpm
e8dc441e046c6102cc8769e865e2cec622080e3d0a205dfd55726f557670e7af  emacs-common-23.1-28.el6.i686.rpm
53e139565006eb5e70d90ce4aaa6ba2a32a585ae9078a836ac046f7382d2bba9  emacs-el-23.1-28.el6.i686.rpm
3ba4ceca1dc4737b4a679791beb01e0c90f1476fbce4118a2359d7a44ca45853  emacs-nox-23.1-28.el6.i686.rpm

x86_64:
86142caef2e8be1ad12be345d384101574fbf5aa590034955283ee426aa24a28  emacs-23.1-28.el6.x86_64.rpm
9c9b20bd73aa7e99ad992683c5736af88fd5fa7c1b567b557030599c4fa1591f  emacs-common-23.1-28.el6.x86_64.rpm
adb22826248066218c9882e0943ec2f21d4346f5917fcb1b529de1789ecda8d6  emacs-el-23.1-28.el6.x86_64.rpm
adb704163645a5cc8a2345e6fd89460246540b3e2b628b534743e0a5aaddb8e7  emacs-nox-23.1-28.el6.x86_64.rpm

Source:
609513920f3f3716d95657d28e9f6a34d1e8e3ec25a9b3a7d1232a8799532ac0  emacs-23.1-28.el6.src.rpm
CentOS

CEBA-2015:0237 CentOS 6 gvfs FASTTRACK BugFixUpdate

CentOS Errata and Bugfix Advisory 2015:0237 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0237.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
7dcaac6f48780a284f3719ff9fc56bde1cc28ad20077cbcf66f1bd8716635dc0  gvfs-1.4.3-20.el6.i686.rpm
996d087774c30b30ebf9924653298e5dd1c34281713b7b151aea6bc4f44298d2  gvfs-afc-1.4.3-20.el6.i686.rpm
a500f0aab82536ac3f925abc9acefb7c6a14ab285c468a8382a28ab450cfebd2  gvfs-archive-1.4.3-20.el6.i686.rpm
42ca7904f7d729d4e02764e9166c4f8e325e1e6e98cea11f0b1b23954e57d163  gvfs-devel-1.4.3-20.el6.i686.rpm
a6a94b87e8dd01a7cd2337a55d35307b5a12ed4d292ca5e33b039f4141af8940  gvfs-fuse-1.4.3-20.el6.i686.rpm
c2359488071b687dc059cee51b3d5e4f065818ca7bdef2e8baf4d9c46aa54595  gvfs-gphoto2-1.4.3-20.el6.i686.rpm
ddc1e972dfeeabf839df9b2c6ae2eeca41b65227e0a36b1e7f39bea27bdfb272  gvfs-obexftp-1.4.3-20.el6.i686.rpm
252b41a9c772c870ef96e3f2b6ee4f11c04380786f6bbeba4fa496c69590dc3a  gvfs-smb-1.4.3-20.el6.i686.rpm

x86_64:
7dcaac6f48780a284f3719ff9fc56bde1cc28ad20077cbcf66f1bd8716635dc0  gvfs-1.4.3-20.el6.i686.rpm
357f42ae60d8fa546df7f331e29cc8fe36cc7245f7cf9393c67d93165c2afc46  gvfs-1.4.3-20.el6.x86_64.rpm
12b45feabfa48e979bb5d67fa7a23c4a2fe23299130211dfd4d0cc65c0e51fd1  gvfs-afc-1.4.3-20.el6.x86_64.rpm
33ebb87255508129c54b5b9cbfd0941ed24d9fa7d80d2e6534f3c6218dab1329  gvfs-archive-1.4.3-20.el6.x86_64.rpm
42ca7904f7d729d4e02764e9166c4f8e325e1e6e98cea11f0b1b23954e57d163  gvfs-devel-1.4.3-20.el6.i686.rpm
1ef766e1eab01c490e44bd46824929b171c5d237085eba90b4bf9870f82574bd  gvfs-devel-1.4.3-20.el6.x86_64.rpm
b463bcb86914c367ae3fbdd6d9b674b5cef2eae21103d1aabcb152805a303019  gvfs-fuse-1.4.3-20.el6.x86_64.rpm
2d6b3096555b0e40b6a7eed103c1580a21fb84e7d3f5a68ff1c88f50cc897d19  gvfs-gphoto2-1.4.3-20.el6.x86_64.rpm
5175db6be3517df7c17f01566e2f20867f9ef57dc90c14512639f09e005f0e71  gvfs-obexftp-1.4.3-20.el6.x86_64.rpm
edb9f926821fd6611b0d9463f04bef794360668534134338d3b990b4dc19eb28  gvfs-smb-1.4.3-20.el6.x86_64.rpm

Source:
d34f8a284468fb3022805f1a3f928ea272b22d29906bf295d82b4dd710006f09  gvfs-1.4.3-20.el6.src.rpm
NVD

CVE-2014-5352 (kerberos)

The krb5_gss_process_context_token function in lib/gssapi/krb5/process_context_token.c in the libgssapi_krb5 library in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly maintain security-context handles, which allows remote authenticated users to cause a denial of service (use-after-free and double free, and daemon crash) or possibly execute arbitrary code via crafted GSSAPI traffic, as demonstrated by traffic to kadmind.