search

dbolin / Apex.Serialization

High performance contract-less binary serializer for .NET
MIT License
86 stars 13 forks source link

Bump Hyperion from 0.9.16 to 0.11.2 #149

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 3 years ago

Bumps Hyperion from 0.9.16 to 0.11.2.

Release notes

Sourced from Hyperion's releases.

Hyperion v0.11.2

0.11.2 October 7 2021

  • Fix exception thrown during deserialization when preserve object reference was turned on and a surrogate instance was inserted into a collection multiple times. #264
  • Add support for AggregateException serialization. #266

0.11.1 August 17 2021

We've added a deserialization safety check to block dangerous types from being deserialized. This is done to add a layer of security from possible code injection and code execution attack. Currently it is an all or nothing feature that can be turned on and off by using the new DisallowUnsafeTypes flag inside SerializerOptions (defaults to true).

The unsafe types that are currently blocked are:

  • System.Security.Claims.ClaimsIdentity
  • System.Windows.Forms.AxHost.State
  • System.Windows.Data.ObjectDataProvider
  • System.Management.Automation.PSObject
  • System.Web.Security.RolePrincipal
  • System.IdentityModel.Tokens.SessionSecurityToken
  • SessionViewStateHistoryItem
  • TextFormattingRunProperties
  • ToolboxItemContainer
  • System.Security.Principal.WindowsClaimsIdentity
  • System.Security.Principal.WindowsIdentity
  • System.Security.Principal.WindowsPrincipal
  • System.CodeDom.Compiler.TempFileCollection
  • System.IO.FileSystemInfo
  • System.Activities.Presentation.WorkflowDesigner
  • System.Windows.ResourceDictionary
  • System.Windows.Forms.BindingSource
  • Microsoft.Exchange.Management.SystemManager.WinForms.ExchangeSettingsProvider
  • System.Diagnostics.Process
  • System.Management.IWbemClassObjectFreeThreaded

0.11.0 July 8 2021

Possible breaking changes

The change to the object serializer field ordering might cause a deserialization failure of persisted objects that are serialized using the Hyperion serializer.

Please report any serialization problem that occurs after an upgrade to this version at the issue tracker

0.10.2 June 30 2021

... (truncated)

Changelog

Sourced from Hyperion's changelog.

0.11.2 October 7 2021

  • Fix exception thrown during deserialization when preserve object reference was turned on and a surrogate instance was inserted into a collection multiple times. #264
  • Add support for AggregateException serialization. #266

0.11.1 August 17 2021

We've added a deserialization safety check to block dangerous types from being deserialized. This is done to add a layer of security from possible code injection and code execution attack. Currently it is an all or nothing feature that can be turned on and off by using the new DisallowUnsafeTypes flag inside SerializerOptions (defaults to true).

The unsafe types that are currently blocked are:

  • System.Security.Claims.ClaimsIdentity
  • System.Windows.Forms.AxHost.State
  • System.Windows.Data.ObjectDataProvider
  • System.Management.Automation.PSObject
  • System.Web.Security.RolePrincipal
  • System.IdentityModel.Tokens.SessionSecurityToken
  • SessionViewStateHistoryItem
  • TextFormattingRunProperties
  • ToolboxItemContainer
  • System.Security.Principal.WindowsClaimsIdentity
  • System.Security.Principal.WindowsIdentity
  • System.Security.Principal.WindowsPrincipal
  • System.CodeDom.Compiler.TempFileCollection
  • System.IO.FileSystemInfo
  • System.Activities.Presentation.WorkflowDesigner
  • System.Windows.ResourceDictionary
  • System.Windows.Forms.BindingSource
  • Microsoft.Exchange.Management.SystemManager.WinForms.ExchangeSettingsProvider
  • System.Diagnostics.Process
  • System.Management.IWbemClassObjectFreeThreaded

0.11.0 July 8 2021

Possible breaking changes

The change to the object serializer field ordering might cause a deserialization failure of persisted objects that are serialized using the Hyperion serializer.

Please report any serialization problem that occurs after an upgrade to this version at the issue tracker

0.10.2 June 30 2021

... (truncated)

Commits


Dependabot compatibility score

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)
dependabot[bot] commented 2 years ago

Superseded by #157.