pkgsrc/devel/ruby-activejob42/distinfo

$NetBSD: distinfo,v 1.3 2018/11/29 13:49:44 taca Exp $

SHA1 (activejob-4.2.11.gem) = 62e9f17f7245c0a7ba2268d8b3e5016fc16ac4a8
RMD160 (activejob-4.2.11.gem) = 9f56f5dc961737fd0437c5bbfb274962dd317ca5
SHA512 (activejob-4.2.11.gem) = 6adfc01934722a193ccee2527ba9f55d363552442455d9c1aa77814be91355a60a97b227b6963c5e6d3daf79a5cd513db50f3ab014c0ea66d8c6c843e69415ce
Size (activejob-4.2.11.gem) = 19456 bytes
devel/ruby-activejob42: update to 4.2.11 ## Rails 4.2.11 (November 27, 2018) ## * Do not deserialize GlobalID objects that were not generated by Active Job. Trusting any GlobaID object when deserializing jobs can allow attackers to access information that should not be accessible to them. Fix CVE-2018-16476. Rafael Mendonça França 2018-11-29 14:49:44 +01:00			$NetBSD: distinfo,v 1.3 2018/11/29 13:49:44 taca Exp $
Import ruby-activejob-4.2.8 as devel/ruby-activejob42 Active Job is a framework for declaring jobs and making them run on a variety of queueing backends. These jobs can be everything from regularly scheduled clean-ups, to billing charges, to mailings. Anything that can be chopped up into small units of work and run in parallel, really. It also serves as the backend for Action Mailer's #deliver_later functionality that makes it easy to turn any mailing into a job for running later. That's one of the most common jobs in a modern web application: Sending emails outside of the request-response cycle, so the user doesn't have to wait on it. The main point is to ensure that all Rails apps will have a job infrastructure in place, even if it's in the form of an "immediate runner". We can then have framework features and other gems build on top of that, without having to worry about API differences between Delayed Job and Resque. Picking your queuing backend becomes more of an operational concern, then. And you'll be able to switch between them without having to rewrite your jobs. 2017-04-21 23:20:33 +02:00
devel/ruby-activejob42: update to 4.2.11 ## Rails 4.2.11 (November 27, 2018) ## * Do not deserialize GlobalID objects that were not generated by Active Job. Trusting any GlobaID object when deserializing jobs can allow attackers to access information that should not be accessible to them. Fix CVE-2018-16476. Rafael Mendonça França 2018-11-29 14:49:44 +01:00			`SHA1 (activejob-4.2.11.gem) = 62e9f17f7245c0a7ba2268d8b3e5016fc16ac4a8`
			`RMD160 (activejob-4.2.11.gem) = 9f56f5dc961737fd0437c5bbfb274962dd317ca5`
			`SHA512 (activejob-4.2.11.gem) = 6adfc01934722a193ccee2527ba9f55d363552442455d9c1aa77814be91355a60a97b227b6963c5e6d3daf79a5cd513db50f3ab014c0ea66d8c6c843e69415ce`
			`Size (activejob-4.2.11.gem) = 19456 bytes`