René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Set-AuthenticodeSignature does not handle MIME type \"application/timestamp-reply\"","articleBody":"Description: Problem:\nWhen using Set-AuthenticodeSignature and specifying a TimeStampServer http URL, if the time stamp server returns content/MIME type of: \"application/timestamp-reply\" the cmdlet returns an unknown error with a status of \"ASN1 bad tag value met\". This is non-compliant according to RFC3161 for Time-Stamp protocol via HTTP.\n\nExpected - Set-AuthenticodeSignature with a specified timestampserver URL appropriately handles the \"application/timestamp-reply\" content/MIME, commits the authenticode signature as well as the timestamp from said server without error.\n\nAdditionally, the success case today is when using Set-AuthenticodeSignature with a specified timestampserver URL and the response is content/MIME type of \"application/octet-stream\" the cmdlet returns without error, the authenticode signature is committed and the timestamp is commited without error.\n","author":{"url":"https://github.com/SteveL-MSFT","@type":"Person","name":"SteveL-MSFT"},"datePublished":"2016-08-12T18:24:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/1752/PowerShell/issues/1752"}