Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Upcoming Changes to pScheduler Limit Configuration

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Upcoming Changes to pScheduler Limit Configuration


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Khalid Mustafa <>, "" <>, "" <>
  • Cc: Shafiq Urrahman <>, "Mohammed O. Sharief" <>
  • Subject: Re: [perfsonar-user] Upcoming Changes to pScheduler Limit Configuration
  • Date: Mon, 31 Jan 2022 15:57:06 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Z7CHBbS6yccHVUo9gtKspHTTkub9cs3jRimsLEwUpZk=; b=nIzvaaB0BR3P/+TeJq5IRFOzOKJqe5RvDb2SULZKptzyrC2ni8fQfyVhZzelLAXyDG5wOQ77gIdXURcgULXsBwyWlBn4MNHX4UVsbcDEn5hK5oQojD/pwmWEcRXJNEcQPDG8OQMND7J7wCjcVdjKUXmaHG27HqB/wg1dB0iOR2QNkqrHSSSweztMtxuSYzV2TQ2B16uNHXk1APD1lqaJ/nOfN854VPLKSUNdL9wyD7sUX0m7+ui7ATeJRcrtJQM5zzmWyND5mAdaDR0y6fplP6rSfngwOttvj7/DZkzgO9OuPLFj6FOqYVXZTICLgKJ8oYGBjq+mwXaSAAAyXFuDDQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dh08NCa9e/9yBTtn6/hjOsBrxlvRuKxXdNAW5XmGm4+qULaWXEWGgvZ3KNJBEOkDWi5m5yoy9fMZUBcH1M4FqWCsGrI+30GYVKbeBO9xiMHlwJNBcGdS/Fzmititqqyms78qokwbf2r8CXdp36NwS5WBr58v02tqvSbXfrIMpe7MdtX5CwUjuDoZ0TmJKmr6aTbMrf01BBRSqKFgPb8PVXzY5KtM2xjR3Ve8LuZiENade0062Htdy6X++9RhI930Few48avSjxbU/DuzUQTcaAREjip6KgtiUN5mbC/nZRp0ZIvkVakuIihEw/XSUQhr2LdMbiecsrqc9qnR+sZ7gw==

Khalid Mustafa writes:

 

In fact, I have a question regarding the Log4j. our Security Tools shows that our perfSonar is vulnerable  for Log4j. is this correct? And if so, what the action that we need to do?

 

I’d refer you to our statement on that from last month:  https://lists.internet2.edu/sympa/arc/perfsonar-user/2021-12/msg00008.html

 

Log4j 1.x, which has its own set of vulnerabilities, is present in the system but is not used in a way that any of them should be exercised.  As covered in the statement, we’re looking at ways to replace it.

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page