notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: security/tor-devel/files/patch-orconfig.h.in

Number of commits found: 3

Sunday, 13 Mar 2022
00:18 Jan Beich (jbeich) search for other commits by this committer
security/tor: drop FreeBSD < 12 remnants after 620968a43a5f

PR:		262509
Approved by:	yuri (maintainer)
commit hash: b68abca3418704836ff372114bb25f41d25b85bc commit hash: b68abca3418704836ff372114bb25f41d25b85bc commit hash: b68abca3418704836ff372114bb25f41d25b85bc commit hash: b68abca3418704836ff372114bb25f41d25b85bc b68abca
Thursday, 21 Dec 2017
20:08 yuri search for other commits by this committer
security/tor-devel: Update to 0.3.2.8-rc

This is an important update for relays running earlier versions of 0.3.2.x.

Changes in version 0.3.2.8-rc - 2017-12-21
  Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
  schedulers that had led servers under heavy load to overload their
  outgoing connections. All relay operators running earlier 0.3.2.x
  versions should upgrade. This version also includes a mitigation for
  over-full DESTROY queues leading to out-of-memory conditions: if it
  works, we will soon backport it to earlier release series.

  This is the second release candidate in the 0.3.2 series. If we find
  no new bugs or regression here, then the first stable 0.3.2 release
  will be nearly identical to this.

  o Major bugfixes (KIST, scheduler):
    - The KIST scheduler did not correctly account for data already
      enqueued in each connection's send socket buffer, particularly in
      cases when the TCP/IP congestion window was reduced between
      scheduler calls. This situation lead to excessive per-connection
      buffering in the kernel, and a potential memory DoS. Fixes bug
      24665; bugfix on 0.3.2.1-alpha.

  o Minor features (geoip):
    - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
      Country database.

  o Minor bugfixes (hidden service v3):
    - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
      the probability of reaching a service for a client missing
      microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.

  o Minor bugfixes (memory usage):
    - When queuing DESTROY cells on a channel, only queue the circuit-id
      and reason fields: not the entire 514-byte cell. This fix should
      help mitigate any bugs or attacks that fill up these queues, and
      free more RAM for other uses. Fixes bug 24666; bugfix
      on 0.2.5.1-alpha.

  o Minor bugfixes (scheduler, KIST):
    - Use a sane write limit for KISTLite when writing onto a connection
      buffer instead of using INT_MAX and shoving as much as it can.
      Because the OOM handler cleans up circuit queues, we are better
      off at keeping them in that queue instead of the connection's
      buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.

Reported by:	nickm@torproject.org
Approved by:	adamw (mentor)
Differential Revision:	https://reviews.freebsd.org/D13576
Original commitRevision:456942 
Monday, 18 Dec 2017
21:55 yuri search for other commits by this committer
security/tor-devel: Update to 0.3.2.7-rc; Unbreaking on systems without
timingsafe_memcmp(3)

timingsafe_memcmp(3) has only been introduced in 12, therefore limiting its use
to 12.

Reported by:	Martin Gehlen <zitlo@zitlo.de> (timingsafe_memcmp(3) bug reporter)
Approved by:	adamw (mentor)
Differential Revision:	https://reviews.freebsd.org/D13496
Original commitRevision:456682 

Number of commits found: 3