We have not tested any other non-SEQUENCE types.Īs I said, we have already worked around this situation, so it fine by me to leave the behavior as-is. One possible base type is the IpAddress type. Each variable also has an associated base type (this is not very accurate but good enough for this level of description). So this documentation sentence with regards to asn1.RawValue sometimes holds and sometimes not. Each variable that is referred to in an SNMP packet is uniquely identified by an OID (Object Identifier), usually written as a sequence of numbers separated by dots (e.g. Previous Vista users will experience no functional differences. The changes to Vijeo Citect undertaken in the 7.1 release to support Windows Vista significantly reduced the changes that were necessary to support Windows 7 and Server 2008 R2. Since we can unmarshal an OBJECT IDENTIFIER into an asn1.RawValue, this sentence implies that we can unmarshal SEQUENCE OF OBJECT IDENTIFIER into asn1.RawValue.Īlso as noted, unmarshaling a SEQUENCE OF SEQUENCE into asn1.RawValue seems to work: we use it for unmarshaling a SET OF X.509 Certificates so that their FullBytes can be passed to x509.ParseCertificate. Vijeo Citect 7.20 also supports the Microsoft Windows 7 and Microsoft Server 2008 R2 operating systems. We worked around this back last year before this issue was reported (also by just unmarshaling into a single asn1.RawValue and going from there), but I still thought to report it as it seems to go against the same godoc snippet that quoted:Īn ASN.1 SEQUENCE OF x or SET OF x can be written to a slice if an x can be written to the slice's element type. cubridseqput (PECL CUBRID > 8.3. So we have to unmarshal a SET OF ANY and one of the possible AttributeValues, Content Type ( ), was an OBJECT IDENTIFIER, which failed.
While in any sane situation I would just use asn1.ObjectIdenfitier, we were implementing Cryptographic Message Syntax (CMS). Tl dr: We actually worked around this even before the bug was reported, so I am fine with leaving the current behavior, but it seems to go against the documentation.
0 kommentar(er)
