tutorial-photo-gallery-angular
tutorial-photo-gallery-angular copied to clipboard
Bump node-forge and @angular-devkit/build-angular
Bumps node-forge to 1.3.1 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.
Updates node-forge
from 0.10.0 to 1.3.1
Changelog
Sourced from node-forge's changelog.
1.3.1 - 2022-03-29
Fixes
- RFC 3447 and RFC 8017 allow for optional
DigestAlgorithm
NULL
parameters forsha*
algorithms and requireNULL
paramters formd2
andmd5
algorithms.1.3.0 - 2022-03-17
Security
- Three RSA PKCS#1 v1.5 signature verification issues were reported by Moosa Yahyazadeh ([email protected]).
- HIGH: Leniency in checking
digestAlgorithm
structure can lead to signature forgery.
- The code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. For more information, please see "Bleichenbacher's RSA signature forgery based on implementation error" by Hal Finney.
- CVE ID: CVE-2022-24771
- GHSA ID: GHSA-cfm4-qjh2-4765
- HIGH: Failing to check tailing garbage bytes can lead to signature forgery.
- The code does not check for tailing garbage bytes after decoding a
DigestInfo
ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used. For more information, please see "Bleichenbacher's RSA signature forgery based on implementation error" by Hal Finney.- CVE ID: CVE-2022-24772
- GHSA ID: GHSA-x4jg-mjrx-434g
- MEDIUM: Leniency in checking type octet.
DigestInfo
is not properly checked for proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest.- CVE ID: CVE-2022-24773
- GHSA ID: GHSA-2r2c-g63r-vccr
Fixed
- [asn1] Add fallback to pretty print invalid UTF8 data.
- [asn1]
fromDer
is now more strict and will default to ensuring all input bytes are parsed or throw an error. A new optionparseAllBytes
can disable this behavior.
- NOTE: The previous behavior is being changed since it can lead to security issues with crafted inputs. It is possible that code doing custom DER parsing may need to adapt to this new behavior and optional flag.
- [rsa] Add and use a validator to check for proper structure of parsed ASN.1
... (truncated)
Commits
a0a4a42
Release 1.3.1.a33830f
Update changelog.740954d
Allow optional DigestAlgorithm parameters.56f4316
Allow DigestInfo.DigestAlgorith.parameters to be optionalcbf0bd5
Start 1.3.1-0.6c5b901
Release 1.3.0.0f3972a
Update changelog.dc77b39
Fix error checking.bb822c0
Add advisory links.d4395fe
Update changelog.- Additional commits viewable in compare view
Updates @angular-devkit/build-angular
from 12.2.18 to 16.0.0
Release notes
Sourced from @angular-devkit/build-angular
's releases.
v16.0.0
16.0.0 (2023-05-03)
@angular/cli
@schematics/angular
Commit Description update to TypeScript 5 and drop support for TypeScript 4.8
@angular-devkit/architect
Commit Description allow registered builder teardowns to execute
@angular-devkit/build-angular
... (truncated)
Changelog
Sourced from @angular-devkit/build-angular
's changelog.
16.0.0 (2023-05-03)
Breaking Changes
@angular/cli
The deprecated
defaultCollection
workspace option has been removed. UseschematicCollections
instead.Before
"defaultCollection": "@angular/material"
After
"schematicCollections": ["@angular/material"]
The deprecated
defaultProject
workspace option has been removed. The project to use will be determined from the current working directory.Node.js v14 support has been removed
Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.
@schematics/angular
ng g resolver
andng g guard
now generate a functional resolver or guard by default. It is still possible to generate a (deprecated) class-based resolver or guard by usingng g resolver --no-functional
orng g guard --no-functional
.- The CLI no longer allows to generate
CanLoad
guards. UseCanMatch
instead.
- TypeScript 4.8 is no longer supported.
@angular-devkit/build-angular
Deprecated
outputPath
andoutputPaths
from the server and browser builder have been removed from the builder output. Useoutputs
instead.Note: this change does not effect application developers.
@angular-devkit/core
- Several changes to the
SchemaRegistry
.
compile
method now returns aPromise
.- Deprecated
flatten
has been removed without replacement.
ContentHasMutatedException
,InvalidUpdateRecordException
,UnimplementedException
andMergeConflictException
API from@angular-devkit/core
have been removed in favor of the API from@angular-devkit/schematics
.UnsupportedPlatformException
- A custom error exception should be created instead.
@angular-devkit/schematics
... (truncated)
Commits
95e1b40
release: cut the v16.0.0 release4f0c1df
refactor: bump@angular/pwa
peer dependency version for v16c8cb641
refactor: bump peer dependencies for v16 release869609c
release: cut the v16.0.0-rc.4 release26dced9
fix(@angular-devkit/build-angular
): JIT support for standalone applications7d792b2
refactor(@angular-devkit/build-angular
): update esbuild builder option status...4cc35f3
build: update all non-major dependenciese17dc92
release: cut the v16.0.0-rc.3 release4d8de73
refactor(@angular-devkit/build-angular
): exclude `@angular/platform-server/in...e690b7c
fix(@angular-devkit/build-angular
): always enablelooseEnums
build optimize...- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.