Re: Security Vulnerability on my Jenkins Server

Thanks, guess we'll have to wait. It's not based on what we do, it's just a security scan software. It's not like anyone can get to it anyway, it's inside the wall, but it is what it is. This one will have to become a POAM. Do you have any clue when the fix is coming up? Again, THANKS for all

Re: Security Vulnerability on my Jenkins Server

I’ve re read your first message, you as for “Jenkins CLI over SSH”, there you cannot do anything until we replace the ssh-module. The module will support those MACs and is not posible to disable them. However, I doubt that the Jenkins CLI use those MACs , and you can always use HTTPS. El El mié,

Re: Set-Variable : Cannot process command because of one or more missing mandatory parameters: Name.

FYI, I started to look at this again and will hopefully have a PR soon. On Tue, Feb 9, 2021, 08:07 Slide wrote: > That will cause problems, the ssh-agents-plugin is not set up to handle > PowerShell as the default shell. I looked into it a while back but didn't > make good progress. > > On Tue,

Re: Security Vulnerability on my Jenkins Server

My MACs line says: MACs hmac-ripemd160,hmac-sha2-256,hmac-sha2-512,hmac-ripemd...@openssh.com I believe this is hardened, isn't it? Thanks, Eric On Wed, Feb 10, 2021 at 9:40 AM kuisathaverat wrote: > hmac-* are Message authentication code algorithms (MACs), so you have to > configure your

Re: Security Vulnerability on my Jenkins Server

hmac-* are Message authentication code algorithms (MACs), so you have to configure your Message authentication code algorithms (MACs) supported, for example MACs hmac-sha2-256,hmac-sha2-512 see https://www.ssh.com/ssh/sshd_config/#common-configuration-changes-for-the-enterprise El mié, 10 feb

Re: Security Vulnerability on my Jenkins Server

Hmmm, I already hardened by that link: https://www.ssh.com/ssh/sshd_config My /etc/ssh/sshd_config has: Ciphers aes128-ctr,aes192-ctr,aes256-ctr This is still showing up on my security scan though. Am I missing something? Thanks, Eric On Tue, Feb 9, 2021 at 12:23 PM kuisathaverat wrote: >

Re: How to set limits for Checkstyles, findsbugs and PMD

See quality gates: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md > Am 09.02.2021 um 19:06 schrieb Ashok reddy : > > Hello Folks, > > Below is the my pipeline script, How can

Re: How to Hide findbug graphs

Which version of the warnings plugin are you using? Since https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/v8.8.0 empty trend charts are hidden. You can also hide the charts using the property `trendChartType`.

Re: Issue with master-agent communication over ssh

you attached the Jenkins build log and the Agent log, should be also an exception in the Jenkins log, Is the same you posted before `invalid type code: 6D`? El mar, 9 feb 2021 a las 21:23, Jigar R () escribió: > Any recommendations on how should I go about this new error? > > On Thursday,

RE: Documentation

Hi, good to know those are going to improve, thanks for the heads up. regards, Jerome From: jenkinsci-users@googlegroups.com On Behalf Of Mark Waite Sent: February 9, 2021 7:36 PM To: Jenkins Users Subject: Re: Documentation On Tue, Feb 9, 2021 at 3:20 PM Jérôme Godbout

Re: Jenkins URL https://.com/ is not working(502 Bad Gateway)

Am Mittwoch, den 10.02.2021, 04:00 -0800 schrieb anilkumar panditi: > docker run --name myjenkins -d -u root -p 8080:8080 -p 5:5 -v > $(which docker):/usr/bin/docker -v /jenkins:/var/jenkins_home -v > /var/run/docker.sock:/var/run/docker.sock myjenkins > > And i curled from other host

Re: Jenkins URL https://.com/ is not working(502 Bad Gateway)

Hi Dirk, Thank you , Jenkins container started like below. docker run --name myjenkins -d -u root -p 8080:8080 -p 5:5 -v $(which docker):/usr/bin/docker -v /jenkins:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock myjenkins And i curled from other host and it gets

Re: Jenkins URL https://.com/ is not working(502 Bad Gateway)

Am Mittwoch, den 10.02.2021, 00:14 -0800 schrieb anilkumar panditi: > And i have curled on host where Jenkins running as docker container , So, this seems to be a Docker question rather than a Jenkins one, doesn't it? Anyway, did you start your container with an appropriate port mapping for port

Multibranch Pipeline git events on PR

I was trying to carry out git operations on *any other branch *than the PR source/destination branch in a jenkins multibranch pipeline. When I scanned the branches inside the PR build job, I didn't see any other branches. I only got below branches on* git branch -a *command on pipeline: * PR-2

Jenkins URL https://.com/ is not working(502 Bad Gateway)

Hi, I have configured jenkins URL , Manage Jenkins>System configuration>Jenkins Location>Jenkins URL ex: https://.com/ And i have curled on host where Jenkins running as docker container , [root@ip- ~]# curl -kv https://.com/ * About to connect() to DNS.com port 443 (#0) * Trying x... *