Posts made by atripp

Hi @davidroberts63 ,

Thanks for digging into this further and providing those logs; looking over the code, I'm think that you must have the licenses feed feature enabled?

This setting is on the manage feed page.

When that feature is enabled, we should see logs like:

• Detecting licenses for {package}...
• Found {licensesCount} licenses: {licenseCodes}

The info is also recorded in the database in the same block.

I can't say why you have other records; they may have come from other feeds, or maybe the feature was disabled later on... the PackageLicenses23 table is not feed specific.

anyway let us know what you discover; it's a little weird to see the behavior, so we would like to confirm and twaeak the UI a little bit to make it clearer

Thanks,
Alana

Hi @caterina ,

Thanks for investigating this! I just made the following changes via PG-2818:

• do not update Stage, Status upon import of SBOM
• set Release Null when editing build (not empty string)
• validate build number is unique

This will go in the next maintenance release, shipping next Friday

Thanks,
Alana

Hi @caterina ,

Thanks for the additional detail.

So I investigated this a little further, and now I see there's a bug in the method that imports the SBOM file - basically it's just overwriting the Stage Name with "Build". That's not intentional.

It looks like the BuildStatus_Code is also reset to Active. I'm not sure if that should be the case; maybe an inactive build should not allow a new sbom added... what do you think

As for the duplicates, we know it's not possible to enter a row in the table with a constraint, so it means there's either whitespace in the buildnumber (two different builds) or there's an incorrect join (build displayed twice).

Just take a look at the projectBuildId querystring parameter for the "2.0.0" builds -- that will clue us in to which case it is.

If it's whitespace, we'll have to figure out where it could be added -- and just trim before adding to database

Thanks,
Alana

Hi @caterina ,

Sorry on the slow reply, I swear I replied to this.... but clearly not.

As you can see from the 500/crash error (which we should obviously not do), there is a data constraint that prevents two builds within the same project and release from having the same number. Specifically, the constraint is <Project_Id, Release_Number, Build_Number>; so it's not possible to have build 3.0.0 twice -- but maybe it's in a different project or release.

As far as "Import SBOM" vs "Create Build", the Import SBOM will create a Project (based on the Component name) and a Build (based on the Version) if it does not exist. Then, it adds the packages within the SBOM Document to the build's list of packages, and then adds the SBOM document itself to the build's SBOM documents.

When importing an SBOM, nothing is deleted; it's always added. As you've seen, Create Build will definitely error out if the build already exists.

Hope that helps clarify,

Alana

Hi @daniel-lundqvist_1790 ,

Based on the problems you're trying to solve, I think ProGet sounds like a good fit.

There are quite a few tools that can generate an SBOM document in the CycloneDX format that ProGet uses; see https://github.com/CycloneDX for the most popular ones. We consider pgutil scan to be a "lightweight" version that works in most cases.

But I think you'll just want to generate your own. It's a pretty simple XML format and easy enough to generate. ProGet can just acts as the SBOM repository in this case.

There shouldn't be a problem to extend the trial extension; you're able to request one on MyInedo on the day of expiry.

Cheers,
Alana

Hi @davidroberts63,

Without looking at the database it's really hard to guess; we'd be happy to investigate your database is you send us a back-up.

But maybe we can figure it out as well.... behind the scenes, there is a table called PackageLicenses23 which associates a specific package version (e.g. Microsoft.Identity.Client 4.66.0) with a specific license Id (MIT). The "Unlicensed Local Packages" page uses that table to find packages (FeedPackageVersions) without an entry.

Data is added into the PAckageLicenses23 table whenever a package is analyzed. So I presume that, if you go to the package and Re-analyze it, then the message goes away? This reanalysis should also occur on a nightly basis with the compliance check job.

If you poke around in the database, note there are PackageLicenses23_Extended and FeedPackageVersions_Extended views won't require you to do a bunch of joins to find.

Thanks,
Alana

Hi @scampbell_8969,

ProGet does not have this feature; we've thought about it after some customer discussions in years past, but I don't think anyone's asked about it until now. And it wasn't the right solution for those customers.

We concluded it would be kind of complicated to document / configure / troubleshoot, especially once we got into the details and specifics. Here's some of those:

• A new version could be unwanted, especially after the "Moq Meltdown" from last year
• Patch versions are probably okay, but new major versions should still be vetted
• Licenses can (and do) change between versions
• New versions It's also a vector for malicious update attacks
• Some kind of filter would be needed to select package for auto-promotion
• Very few packages get frequent updates, so this doesn't seem like it's solving a big problem

Instead we created a "latest version" compliance flag that allows you to flag packages that aren't the latest patch version. We'll see if that's popular.

Thanks,
Alana

@caterina thanks, we'll discuss this internally and get back to you soon!

Hi @caterina

If you're getting that message, it means that the package cannot be checked for "package status" (i.e. listed, deprecated) because it's not local to your feeds. If you cache the package, then it should go away.

Thanks,
Alana

Hi @udi-moshe_0021 ,

You're going to get a lot of headaches trying to use server-side virus/malware scanning with a tool like ProGet and we do not support using such tools in conjunction with ProGet.

These types of tools are hyperaggressive and really dumb -- they often quarantine "dangerous" files like .dll, block "malicious" files like Javascript, or think that ProGet loading plugins is "malware behavior".

In addition, the tools are totally unnecessary, as ProGet already has vulnerability detection built in.

Cheers,
Alana

Hi @Scati,

pgutil will construct an purl using this method:
https://github.com/Inedo/pgutil/blob/c5b5e3733390b9e5dfb07752e36a3f6efaaa0f9c/pgutil/Packages/QualifierOptions.cs#L26

So I'm thinking there's something off about your url, but I can't spot it. Maybe try

https://serverip/api/packages/unstable-lin/delete?purl=pkg:deb/scatimysqlcluster@7.3.0.0-0.202406122314.6df3a85167?arch=amd64&distro=jammy&component=scati

That appears to be the order that pgutil uses...

Cheers,
Alana

Hi @jw ,

We'll get this fixed via PG-2814 in the next maintenance release (Oct 18). Or if you prefer a prerelease let us know and we can build one for you.

As a work-around, you can add Custom-Telerik-EULA as a SPDX code and the license will be found, allowing you to view the page.

Thanks,
Alana

Hi @Scati ,

The request looks OK to me on a first glance, but I wonder... did you try using pgutil to delete the package?

pgutil packages delete --feed=myDebianFeed --package=myDebianPackage --version=2.3.4 --component=main --distro=stable --arch=amd64

I'm not sure if you're using the latest version of ProGet, but I think there was a bug regarding this.

Thanks,
Alana

Hi @caterina ,

I guess those never made it over... they were undocumented and we basically started fresh. Following in my other post, we want to really make surea ll commands fit together nicely and are documented well.

I'm almost certain know you contributed them, but can you help to document what they are?

I found the code here:
https://github.com/Inedo/pgscan/blob/master/PgScanCommon/Program.cs#L231

Does this only work with .NET?

Also... I don't think we have the identify command anymore, right?

Thanks,
Alana

Hi @caterina

It's very possible this was overlooked; we seem to have accepted a lot of pull requests without documenting them or knowing how they work

We want to make sure the tool is well documented... can you share what all this does, and how we can document it? It might be easy to add back in ... we just want to make sure all these switches are documented and still make sense.

Thanks,
Alana

Hi @forbzie22_0253 ,

Yes, we use Kestrel under the hood.

You can configure HTTPS under Admin > HTTPS:
https://docs.inedo.com/docs/installation/installing-on-iis/installation-windows-https-support

No real "gotchas" -- but note that with port sharing (i.e. binding to a hostname as opposed to an IP), that needs to use the HTTP.SYS component of Windows.

Cheers,
Alana

Hi @forbzie22_0253,

Following Microsoft's guidance to no longer use IIS for modern .NET applications, we no longer recommend using IIS to host modern versions (2022+) of our products.

Instead, you should use the Integrated Web Server instead, which is our (and Microsoft's) recommended web server. Although IIS is still supported, there are no benefits aside from a more familiar user interface.

That said, even with IIS this is not a supported nor recommended configuration; if there was ever a need to segregate feeds (for example Docker Container Images used for production applications and NuGet packages used for developers), then it should be done at an instance/server level.

Cheers,
Alana

Hi @marc-ledent_9164

BuildMaster is not writing that HTML, so it must be some kind of reverse proxy or something that's replacing the HTML.

If you view source, none of the hyperlinks in BuildMaster will have a domain name -- nearly everything should be a relative/rooted URL like /something.

Cheers,
Alana

Hi @marc-ledent_9164 ,

That's unusual; can you Inspect the element on that link and let us know what you see? I looked in my BuidMaster v7 instance, and here's what I see:

Can you access that URL directly? E.g. something like:
https://your-buildmaster.corp.local/administration/security/built-in/change-password

It should show you a page like this:

Cheers,
Alana

Hi @marc-ledent_9164 ,

That refers to our build server :)

That part of the error message is the stack trace, and that shows us exactly where the error is occurring in the code, should we need to debug it.

That said, if you're seeing those errors in your execution logs, then it's probably related to configuration of some kind..... we can help if we could see more context

Cheers,
Alana

Just as an update, we discovered abug with pulling packages for this feed, and we will fix it via PG-2812 in an upcoming release

Hello,

Can you share your credentials with us? Easiest way for us to figure iit out is to attach a debugger and see what's happening.

NOTE - I see you also submitted a ticket (EDO-10807), so you can just reply to that. I'll reply here once we figure out a resolution :)

THanks,
Alana

Hi @lucas_001

I'm a bit rusty with these and I'm going off memory, but I know that AHVALUEDRIFTED is supposed to point to a boolean.

Have you tried a script like this instead?

$EnvironmentVariableDesiredValue = $EnvironmentVariableValue
$EnvironmentVariableCurrentValue = [System.Environment]::GetEnvironmentVariable($EnvironmentVariableName, [System.EnvironmentVariableTarget]::Machine)
$EnvironmentVariableDriftedValue = $EnvironmentVariableValue -ne $EnvironmentVariableCurrentValue

Write-Host "Current value of environment variable '$EnvironmentVariableName' is '$EnvironmentVariableCurrentValue'."

if ($ExecutionMode -eq "Collect") {
  if ($EnvironmentVariableValue -ne $EnvironmentVariableCurrentValue) {
    Write-Information "Environment variable '$EnvironmentVariableName' has drifted from the desired value."
  } 
  else {
    Write-Information "Environment variable '$EnvironmentVariableName' is set to the desired value."
  }
} 
  
elseif ($ExecutionMode -eq "Configure") {     
  if ($EnvironmentVariableDriftedValue) {
    [System.Environment]::SetEnvironmentVariable($EnvironmentVariableName, $EnvironmentVariableValue, [System.EnvironmentVariableTarget]::Machine)
    Write-Information "Environment variable '$EnvironmentVariableName' has been set to the desired value."

  } 
  else {
    Write-Information "Environment variable '$EnvironmentVariableName' is set to the desired value."
  }
}   

That might do the trick... note the only thing aside from logging that's happening is in the execute portion.

Can you try that? Obviously the logging experience should be improved. No idea why there's a JSON parse error happening.

Thanks,
Alana

@tekla-buildmaster_8300 it's on our list for this year :)

https://blog.inedo.com/inedo/roadmap2025/

Hi @david-cheng_0852,

This is where using LDAP or SAML comes in; we strongly recommend using that instead, so that users don't have to store/track yet another password.

ProGet's built-in users are really only intended for simple use cases (like ProGet Free edition) or when you're first getting started with ProGet. After that, you should switch to LDAP or SAML.

We can consider adding a password policy, but we'd like to first understand why it's not possible (or too difficult) to use LDAP/SAML.

Thanks,
Alana

Hi @david-cheng_0852 ,

ProGet's Built-in User Directory does not have a password policy/restriction.

Thanks,
Alana

Hi @frei_zs ,

I'm not really sure how signing keys work to be honest, but they seem to be really just used for the InRelease index?

Anyway, it was trivial to add a button to Delete the existing signing key. When you click that button, it will then show a page that allows you to Create a signing key:

So we'll get that in via PG-2807 in the next maintenance release (shipping on Friday).

As far as uploading a custom key, doing via API, etc., that's not trivial... but I'm thinking this will cover your bases. I can't imagine you are swapping these out often (or ever).

Thanks,
Alana

Hi @jw ,

Unfortunately the "deprecated dialog" isn't shown if a package is not in compliance; the noncompliance message is instead displayed. This is something we're aware of and plan to review/fix with the UX redesign.

Alana

Hi @jw ,

These are some "compromises" we've made over the versions that have led a suboptimal UX. Basically, the issue is that we have a single box to work with, and the message is based on:

• if a package has an "unknown license" dialog, it shows that option to add a license
• else if a package has a Block or Warn compliance status, then you see the noncompliant reason
• else if a package is Deprecated, then you see the message/warning about deprecation
• etc.

Displaying multiple boxes doesn't work very well, and the code is already complex enough, so we don't want to mess with it too much more. That said, we are planning to "rethink" the Package Overview Page UI as a whole with the help of a UX agency, hopefully in time for ProGet 2025.

Regarding Visual Studio, something must have changed. The message should be there as we are emitting in the API, but perhaps doing so incorrectly. We'll fix this via PG-2806, hopefully in the next maintenance release.

Thanks,
Alana

Hi @frei_zs,

This is not supported; is there a reason that you'd want to do that?

My understanding is that signing keys are an outdated/vestigial concept that only makes sense if you're not using SSL/HTTPS.

Thanks,
Alana

Hi @andy222

I'm afraid we don't have that capability in OtterScript, and it would require a new variable function to do that. You might be able to add that in an extension, or we could add it as well.. but we have a few things we want to finish first on our BuildMaster 2024 roadmap.

Since you're creating build variables using the API, I wonder if you could just create a variable called @BuildVariables that is just a list of the variables you're creating. Then you can use $BuildVariable(name) to get the value.

Hope that helps,
Alana

@pariv_0352 oh interesting - for some reason I thought NuGet was used for C++ packages...

I just did a quick look, and it doesn't look like vcpkg supports private registries; it only looks for package files on disk (share drive?) or in a Git repository:
https://learn.microsoft.com/en-us/vcpkg/maintainers/registries

So I guess the first step would be to ask the vcpkg team to create a package registry :)

Hi @daniel-lundqvist_1790 ,

I'm not really sure what you're trying to accomplish, but I'll try to give some background surrounding your questions.

First, some quick terminology:

• Assets are basically just files in folders, like an S3 bucket or share drive. You could put whatever you'd like in an asset directory.
• A Build is basically a "set of related SBOM files" and is basically a way to organize/track SBOMs and their compliance
• An SBOM is basically a list of purls (package type/names/versions/etc) and purls almost always refer to third-party, OSS packages. However, ProGet can (and often will) cache these OSS packages in feeds.
• Universal Packages are intended for your own, proprietary content. They are basically an alternative to storing things in folders or in a file like myApp-3.2.zip
• Dependencies in Universal Packages always reference other a Universal Package or range of packages; they are basically just another metadata field like package description, but with a standard format

I can't say if Universal Packages or Builds/SBOMs are a good fit for your product. It really depends on what what problems you're trying to solve. If you can talk more about that, we'll try to help better.

That said, you could technically craft an SBOM that references Universal Package purls (pkg:/upack/myPackage@4.2.1), and then create/add that to a build, but it doesn't make a lot of sense to me. SBOMs (and SCA in general) is intended for OSS compliance, and that's how ProGet uses it.

pgutil builds scan will generate and upload a basic SBOM file during the build process for .NET, npm, and Python applications. It's basically a lightweight alternative to CycloneDX, which also generates SBOM files.

As for dependencies, neither pgutil nor CycloneDx will read "dependency metadata" from package manifest files; instead they inspect the packages that were installed/downloaded by the build tool. Package dependencies are somewhat orthogonal to SCA/SBOM.

I'm not sure if any tool out there can generate an SBOM file given a list of rpm packages, but they're pretty easy to create with a script and upload to ProGet.

Hope that helps,
Alana

Hi @pariv_0352

I haven't heard of vcpkg before, and it's not listed on our Other Feed Types page - so that probably means you must be the first person to ask :)

Can you share some more information about vcpkg? It looks new... how does it compare to Conan?

Thanks,
Alana

Hi @mars , I'm afraid rafts do not support this setting.

I'm not sure if it's possible, given the library that we use. We are planning to add an option to bypass certificate validation in BuildMaster 2024, so it might be possible to add this option to raft repositories as well. I'll add a note and we'll investigate -- the plan is late October for both BuildMaster 2024 and OTter 2024

Thanks,
Alana

Hi @caterina ,

Thanks for checking; I was able to reproduce this; it seems to be a regression.... we'll get it fixed via PG-2795 in next week's maintenance release. Thanks for letting us know.

Thanks,
Alana

Hi @caterina,

I'm not seeing any changes in 2024.14 that would cause this behavior, so I'm not sure what it could be offhand.

The first thing I would check is the connector filtering; can you try that out? It's under Admin > Manage Feed. There might be something in ther.e

You may also see some recent connector errors under Admin > diagnostic Center.

Thanks,
Alana

Hi @jw ,

This doesn't seem like a a trivial change, due to the way those pages work, so I'll add it to the "wishlist" - we've got a lot of other ProGet 2025 roadmap stuff prioritized ahead for the time being :)

Cheers,
Alana

Hi @dan-brown_0128 ,

It doesn't look like there's been much interest in this so far (we haven't heard any othe rrequests for it), but I wanted to mention that Terraform repositories are planned and something we hope to accomplish in the coming months.

Cheers,
Alana

Hi @dan-brown_0128,

Thanks we'll definitely keep this in mind when we explore updating/expanding the feature!

In the meantime, I think there might be a better workflow for you to consider. We wouldn't recommend using "download blocking" for an application packages like this.

The reason is... the status could change, and when you go to deploy the application, it will probably fail in an inconvenient place and the person doing the deployment won't quite get why there's a random error/crash.

Instead, how about using pgutil builds audit as a means to achieve a similar goal? You would run it as a deployment precheck, and the tool would output errors if the compliance status of packages were not acceptable. This will be much more intuitive of a failure, and you could run it early in the process.

I'm not quite sure if pgutil builds audit is suitable today, but I know that's on our shortlist to get working, and create HOWTO guides for using it.

Cheers,
Alana

Hi @jw ,

This can be accomplished with a script using the Set Package Status API; there are a couple scripts that should get you going on there.

Cheers,
Alana

@sebastian said in Problem with PGV-22381O7 (tree-kill1.2.2 incorrectly flagged vulnerable):

There should be a special treatment for withdrawn vulnerabilities within ProGet. Maybe not deleting them (because I'm pretty sure there will be cases where I will be looking at a package and think "I swear this one had a vulnerability, but now I can't find it?" ), but maybe auto-assess a special status to it.

That's what we were worried about as well, having them dissapear. Perhaps we just delete ones without assessments, and if you set a withdrawn vulnerability unassessed, it gets deleted

Hi @dan-brown_0128 ,

Thanks for sharing!

#1 and #2 will be pretty easy UI changes - and I'm almost certain there's already a URL for Builds, but it's just not linked.

#3 is complicated, since we do not model package consumers (which would allow you to say "show me all packages that use X") nor do we have the concept of "application packages" (e.g. MyCorp.Package is also a project), so we'd have to really think about how to create a use case for this.

As an FYI, our team we're currently pretty heads-down on feeds (new Maven feed, then Rust/Cargo, Terraform, PHP/Composer, C++/Conan), PostgreSQL migration, and a few other things, but our rough plan is to resume working on SCA stuff in Q1.

If these are a particular blocker for rolling out the feature, we can consider to shift focus.

Hi @sebastian,

Thanks for sharing this...

I don't really know the answer, but I searched for "tree-kill" on Inedo Security Labs, and found three results:

• https://security.inedo.com/vulnerability/details/PGV-22381P5
• https://security.inedo.com/vulnerability/details/PGV-22381O7
• https://security.inedo.com/vulnerability/details/PGV-2065719

We can see that PGV-22381O7 does say it "affects tree-kill (npm), versions (all)", so that's where the data is coming from in ProGet. My guess is that it's a data update/aggregation problem, maybe related to the Withdrawn status?

There is apparently some use case for all as a version, and I guess it's exactly what you specified? A lot of Redhat/Linux system packages have all versions and get updated later.

Anyway, ISL is managed by a different team, so I'll submit an internal request to review. It doesn't seem so urgent, just inconvenient/incorrect and easy to workaround in ProGet. But let me know if I misread that.

As for "Withdrawn" vulnerabilities... we're open to ideas for what to change in ProGet 2025. There used to just be a handful, but there are a lot more now. Our original was to just delete them from ProGet, but instead we just showed the icon. Maybe we should delete them.

Thanks,
Alana

Hi @caterina ,

Can you try to download the latest version of Inedo Hub at https://my.inedo.com/

That should allow you to install the older version. You can also install an offline installer for the ProGet 2023 version you'd like.

Thanks,
Alana

Hi @steviecoaster ,

I'm not really a PowerShell guru, but I think you'll want to do ...

    $base64Salt= [System.Convert]::ToBase64String($saltBytes)

... and then pass that in.

Hope that does it!

Alana

Hi @chris-cantrell_1211 ,

We do not support nor recommend this type of configuration for a couple reasons.

First, it doesn't change the attack surface, since the APIs are already the "weakest link". The Web Site use cryptographically-secured authentication tickets with anti-CRSF protection. The API just requires an API key to access.

Second, it's confusing to end-users who are trying to troubleshoot why some urls aren't accessible. The API may provide them with a link (for example to a vulnerability in a package), and then it will give some kind of error because the page is blocked. This causes everyone a headache.

Obviously you can use a lot of tools to block/allow access to URLs, just not using ProGet.

Cheers,
Alana

Hi @tamir-dahan_7908 ,

Either you're making a typo somewhere, or there is something odd about your Docker/server configuration that is preventing a local network connection. I'm afraid I'm not a Docker expert, so I don't know what else to look for -- it could be specialized security configuration you have or a monitoring tool that's blocking things.

If you have a Docker expert on your team, I would check with them to get some help. Ultimately, ProGet is just an ordinary .NET application making a connection on an ordinary SQL Server that's on the same local network (i.e. inedo-sql)... it's a super-common use case and just works out of the box.

The most common issue is a typo (i.e. inedo-sql in one command and inedosql in another), but since this is such a common use case, if you search "Docker" and "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible", you'll find a ton of results with lots of different things to try as well.

If you're new to Docker, i would suggest installing with Inedo Hub - it's a lot easier to use.

Cheers,
Alana

Hi @tamir-dahan_7908,

The error message coming from ProGet is this:

Unhandled exception: Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)

So basically it's a network error, and the ProGet container can't talk to the SQL Server container. I'm not an expert on troubleshooting Docker, but my "guess' would be that the network is different between containers.

This is specified by the net command, and I know I've mistyped that a few times. Here's the script I use to get up and running on Docker:

docker run --name inedo-sql \
  -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=«YourStrong!Passw0rd»' \
  -e 'MSSQL_PID=Express' --net=inedo --restart=unless-stopped \
  -d mcr.microsoft.com/mssql/server:2019-latest

docker exec -it inedo-sql /opt/mssql-tools/bin/sqlcmd \
  -S localhost -U SA -P '«YourStrong!Passw0rd»' \
  -Q 'CREATE DATABASE [ProGet] COLLATE SQL_Latin1_General_CP1_CI_AS'

docker run -d --name=proget --restart=unless-stopped \
  -v proget-packages:/var/proget/packages -p 80:80 --net=inedo \
  -e PROGET_SQL_CONNECTION_STRING='Data Source=inedo-sql; Initial Catalog=ProGet; User ID=sa; Password=«YourStrong!Passw0rd»' \
  proget.inedo.com/productimages/inedo/proget:latest

Hope that helps,
Alana

Hi @jw ,

This error should not be logged and you can ignore it; we'll get it fixed in an upcoming maintenance release of ProGet via PG-2740

Cheers,
Alana