Class: Array

Inherits:
Object
  • Object
show all
Defined in:
lib/net/ber.rb

Direct Known Subclasses

Net::BER::BerIdentifiedArray

Instance Method Summary collapse

Instance Method Details

#to_ber(id = 0) ⇒ Object

to_ber_appsequence An application-specific sequence usually gets assigned a tag that is meaningful to the particular protocol being used. This is different from the universal sequence, which usually gets a tag value of 16. Now here’s an interesting thing: We’re adding the X.690 “application constructed” code at the top of the tag byte (0x60), but some clients, notably ldapsearch, send “context-specific constructed” (0xA0). The latter would appear to violate RFC-1777, but what do I know? We may need to change this.



531
 
# File 'lib/net/ber.rb', line 531

def to_ber                 id = 0; to_ber_seq_internal( 0x30 + id ); end

#to_ber_appsequence(id = 0) ⇒ Object 



534
 
# File 'lib/net/ber.rb', line 534

def to_ber_appsequence     id = 0; to_ber_seq_internal( 0x60 + id ); end

#to_ber_contextspecific(id = 0) ⇒ Object 



535
 
# File 'lib/net/ber.rb', line 535

def to_ber_contextspecific id = 0; to_ber_seq_internal( 0xA0 + id ); end

#to_ber_oid ⇒ Object

Raises:



537
538
539
540
541
542
543
544
545
 
# File 'lib/net/ber.rb', line 537

def to_ber_oid
  ary = self.dup
  first = ary.shift
  raise Net::BER::BerError.new( "invalid OID" ) unless [0,1,2].include?(first)
  first = first * 40 + ary.shift
  ary.unshift first
  oid = ary.pack("w*")
  [6, oid.length].pack("CC") + oid
end

#to_ber_sequence(id = 0) ⇒ Object 



533
 
# File 'lib/net/ber.rb', line 533

def to_ber_sequence        id = 0; to_ber_seq_internal( 0x30 + id ); end

#to_ber_set(id = 0) ⇒ Object 



532
 
# File 'lib/net/ber.rb', line 532

def to_ber_set             id = 0; to_ber_seq_internal( 0x31 + id ); end