Recherche avancée

Sur d’autres sites (6593)

• Secure and track every change to your Piwik installation with the Activity Log plugin

  14 novembre 2017, par InnoCraft — Plugins

  Are you wondering how your colleagues are using Piwik ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Piwik some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Piwik websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

  Activity log for better security

  The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

  1. detect any suspicious actions
  2. detect hacker attacks
  3. help identify performance problems
  4. see clearly who did what, and when
  5. find out how people are using Piwik within your company

  1 – detect any suspicious actions

  With audit trail you can easily identify if a former employee still has access to your Piwik installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

  2 – detect hacker attacks

  When an unregistered user is trying to access your Piwik, each failed login attempt is registered within the Activity Log report.

  3 – help identify performance problems

  Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Piwik is getting performance problems, then it is likely that the plugin update caused it.

  4 – see clearly who did what, and when

  It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Piwik, created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

  5- find out how people are using Piwik within your company

  By having a look at how people are using Piwik you will have an overview of how your colleagues use Piwik. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

  Did you know ?

  You can help the Piwik core team make Piwik even better by sharing anonymously how you use Piwik on a day to day basis. You just need to install the following plugin : http://plugins.piwik.org/AnonymousPiwikUsageMeasurement

  What’s in it ?

  Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

  

  If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Piwik and which actions they performed.

  Those reports are critical as they allow the super user to :

  • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
  • identify suspicious behavior. As those reports are gathering all major Piwik users activities it is easy to identify non conventional behavior.
  • replay the sequence some users went through in order to fix any potential issues.

  Activity log view report you can access through the admin panel

  So you will see in a second if an unusual user got access to Piwik and the different actions the user performed.
  It is also a good way to see the features that your users are using and identify potential misuse.

  As a regular user or admin, activity log is providing only the historical actions that this user performed :

  

  Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

  • Annotation
  • Custom Alert
  • Custom Dimension
  • Goal
  • Privacy settings
  • Scheduled report
  • Segment
  • User
  • Website
  • …

  This is a ideal to remember the actions they previously performed some weeks/months ago.

  Where can I start from here ?

  Activity log is a premium feature you can acquire through the Piwik marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

  I want to try the Activity Log plugin

  Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Piwik. Discover all their special plugins through the premium marketplace.

   

• pixfmt : remove misleading and broken documentation

  28 mai 2015, par wm4

  pixfmt : remove misleading and broken documentation
  This was probably broken some time ago. The breakage is now part of the
  
  ABI. For example, we have :
      AV_PIX_FMT_XYZ12BE
  
      AV_PIX_FMT_NV16
  
      AV_PIX_FMT_NV20LE
  AV_PIX_FMT_NV20LE is wrong. It has the value 113, but as little-endian
  
  format it should be even. This must have been quite obvious when these
  
  formats were added (because of the AV_PIX_FMT_XYZ12BE entry), but
  
  nobody cared or knew about this.
  The future libavutil major bump will also break this additionally,
  
  because disabling FF_API_VDPAU will remove an odd number of entries from
  
  the middle of the enum.
  Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
  

  • [DBH] libavutil/pixfmt.h

• Merge commit ’3399a26d3f57d462e839c0ee51223ae9aca20852’

  25 juin 2016, par Clément Bœsch

  Merge commit ’3399a26d3f57d462e839c0ee51223ae9aca20852’
  * commit ’3399a26d3f57d462e839c0ee51223ae9aca20852’ :
  
    nvenc : allow setting the number of slices
  
    nvenc : De-compensate aspect ratio compensation of DVD-like content.
  
    nvenc : list the major contributors in the copyright header
  
    configure : Don’t require nonfree for nvenc
  
    nvenc : drop the hard dependency on CUDA
  
    nvenc : only support HW frames when CUDA is enabled
  
    nvenc : write the VUI signal properties for HEVC
  
    nvenc : only write the VUI signal type fields if they are set
  
    nvenc : Generate bufferingPeriod/pictureTiming SEI
  
    nvenc : Delay frame output to increase encoding speed
  
    nvenc : add support for lossless encoding
  
    nvenc : Generate AUD NAL units for better compatiblity
  
    nvenc : fix the rc option definitions
  All these commits are noop as requested by Timo Rothenpieler.
  <BtbN> andrey_turkin, ubitux, yeah, I like the current state of nvenc in
  
  ffmpeg, I think most remaining differences should be merged on the libav
  
  side of things. At least I’m not aware of anything that’s missing in
  
  ffmpeg.
  Merged-by : Clément Bœsch <u@pkh.me>