search for: hex

...68.0.201(137) header: id=27220 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=*<00> rr_type=33 rr_class=1 ttl=0 answers 0 char ................ hex 00000000000000000000000000000000 answers 10 char ................ hex 00000000000000000000000000000000 answers 20 char ................ hex 000000000000000000000000000000 *Case 2:* nmb packet from 192.168.0.201(137) header: id=27185 opcode=Query(0) response=Yes header: flag...

...I was working on ldap to convert but I'll try ldb-tools >> >> I was off on a bash mission here is what I had so far it isn't correct >> so I'll keep working on it >> >> #!/bin/bash >> if [ "$(echo $1|wc -c)" = "41" ];then >> hex=$(echo $1|base64 -d| od -x -w28 --endian=big|head -n1|sed >> 's/^0000000 //'|sed 's/ //g') >> echo ${hex} >> hex_chunk=$(echo ${hex}|cut -c1-2); >> echo ${hex_chunk} >> rev=$(echo "ibase=16; ${hex_chunk}" | bc) >> hex_chunk=$(echo ${hex}...

On Sat, 4 Nov 2017 18:42:36 -0600 Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > I decided to continue trying the ldap route as well > > littlehex2int() > { > hex=$1 > hex_chunk=$(echo ${hex}|cut -c$2-$3) > little=$(echo ${hex_chunk}|awk '{print > substr($0,7,2)substr($0,5,2)substr($0,3,2)substr($0,1,2)}') > echo "ibase=16; ${little}" | bc > } > > base64_to_sid() > { > OBJECTSID="$1...

Not bad but I wanted an ldap version because I was having issues running ldbsearch as a normal user. I created the following functions to get it in and out of base64 and hex swap_endian() { local input=$1 local output="" while [ "${input}" != "" ];do output="${input:0:2}${output}" input=${input:2} done echo $output } base64_to_hex() { echo $(echo $1|base64 -d|hexdump -ve '/1 "%02x"') } hex2sid() { local hex=$...

Thank you, Clayton. It works now! Our debugger server responds "name:J28;generic:fp;bitsize:32;encoding:uint;format:hex;gcc:60;dwarf:60". And I also set other "generic" attributes like sp, pc, ra, arg1~arg8 to related registers. I dig a little and find llvm dwarf generator uses TargetRegisterInfo::getFrameRegister() to obtain frame base, and uses TargetFrameLowering::getFrameIndexReference() to obtai...

...(137) header: id=10137 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=KOVAITEST<1c> rr_type=33 rr_class=1 ttl=0 answers 0 char .KOVAI-X30KWI8Z3 hex 0C4B4F5641492D5833304B5749385A33 answers 10 char .D.KOVAI-X30KWI8 hex 0044004B4F5641492D5833304B574938 answers 20 char Z3 D.KOVAITEST hex 5A332044004B4F564149544553542020 answers 30 char ...KOVAITEST hex 2020202000C4004B4F56414954455354 answers 40 char...

Thank you, Clayton. This is very helpful. We use the LLDB specific GDB remote extensions, and our debugger server supports "qRegisterInfo" package. "reg 0x3c" is the frame pointer. In the example mentioned above, we have SP = FP - 40 for current call frame. And variable "a" is stored at address (FP + -24) from asm instruction [FP + -24] = R3;; Thus we can conclude

That looks easier I was working on ldap to convert but I'll try ldb-tools I was off on a bash mission here is what I had so far it isn't correct so I'll keep working on it #!/bin/bash if [ "$(echo $1|wc -c)" = "41" ];then hex=$(echo $1|base64 -d| od -x -w28 --endian=big|head -n1|sed 's/^0000000 //'|sed 's/ //g') echo ${hex} hex_chunk=$(echo ${hex}|cut -c1-2); echo ${hex_chunk} rev=$(echo "ibase=16; ${hex_chunk}" | bc) hex_chunk=$(echo ${hex}|cut -c3-4) echo ${hex_chunk} dashes=$(echo "ibas...

I decided to continue trying the ldap route as well littlehex2int() { hex=$1 hex_chunk=$(echo ${hex}|cut -c$2-$3) little=$(echo ${hex_chunk}|awk '{print substr($0,7,2)substr($0,5,2)substr($0,3,2)substr($0,1,2)}') echo "ibase=16; ${little}" | bc } base64_to_sid() { OBJECTSID="$1" hex=$(echo ${OBJECTSID}|base64 -d|od -A n -x -w2...

Hi all, Date: Thu, 10 Dec 2009 22:55:20 +0800 Subject: [PATCH] [RFC] lib: add a hex dump lib function I think it would be better to have a hex dump routine; it would make debugging much easier since it can dump the data, like fs meta data, in a hex style, just like what the 'hexdump -C file' command does. BTW, I'm not sure where should I to put the hexdump function d...

...100MB 4.0MB <= OK / 7GB 5.2GB <= NO OK Is seems this is 4 time the original size for / and /soft Getfattr for the four nodes : ylal3020:/etc/ucarp/interface # getfattr -n trusted.glusterfs.quota.size -e hex /soft/venus ; getfattr -n trusted.glusterfs.quota.size -e hex /soft/venus/test ; getfattr -n trusted.glusterfs.quota.size -e hex /soft/venus/psa;getfattr -n trusted.glusterfs.quota.size -e hex /soft/venus/soft getfattr: Removing leading '/' from absolute path names # file: soft/venus truste...

I have a probe: pid111::myfunc:entry { self->arg = arg0; } pid111::myfunc:return /self->arg/ { @[self->arg] = quantize(); } works great, but i''d like arg0 to be printed in hex. I''ve tried numerous approaches to do this but i''ve hit a wall every time. I''ve tried: 1) self->arg = sprintf(arg0); no, cuz dtrace has no sprintf 2) self->arg = string((void*)arg0); no, cuz it tried to dereference arg0, but it''s a value Then I wrote a...

...12.68.102.9(137) header: id=18463 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=ATHENA<20> rr_type=32 rr_class=1 ttl=0 answers 0 char `..Dw. hex 6000D4447701 [2003/02/18 11:07:27, 2] libsmb/namequery.c:name_query(421) Got a positive name query response from 212.68.102.9 ( 212.68.119.1 ) [2003/02/18 11:07:27, 3] lib/util_sock.c:open_socket_in(813) bind succeeded on port 0 [2003/02/18 11:07:27, 5] libsmb/nmblib.c:send_udp(741) Sending a...

...om 10.80.100.62(137) header: id=2081 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=REG<1c> rr_type=33 rr_class=1 ttl=0 answers 0 char .PDC hex 09504443202020202020202020202020 answers 10 char .d.PDC hex 00640050444320202020202020202020 answers 20 char .d.PDC hex 20200364005044432020202020202020 answers 30 char d...__MSBRO hex 2020202020640001025F5F4D5342524F answers 40 char WSE__....REG...

My stab v3 at fixing this: https://bugzilla.redhat.com/show_bug.cgi?id=1789279 It took me quite some time to go through the whole rfc 4122 just to realize we do not need to do anything with the versions. v3: - Do the check in precheck - Fix for Lazy evaluation of regexp UUID v2: - https://www.redhat.com/archives/libguestfs/2020-January/msg00221.html - Use EEXIST instead of EINVAL - Put the

I'm getting a very strange error and I'm completely mystified by it. Thank you so much for taking a look! I recently migrated some users from another dovecot server to my own, and the previous admin had the passwords in their database using the SSHA256 scheme in HEX format. All the password hashes are in my database (MySQL) with a {SSHA256.HEX} prefix, and I thought at first that they were working fine, but then I checked my logs and am seeing this: localhost dovecot: auth: Error: password(***@***.***): Unknown scheme SSHA256.HEX.b64 (I have replaced the ema...

Hello List Dwellers: I?ve looked around quite a bit, but don?t quite see an answer that I understand. I?m looking for a way to take any kind of color specification (rgb, hsv, hcl, hex) and match it to the n-nearest R official color names. Clearly it is easy to interconvert different specification schemes and color spaces, but matching to the name seems a bit trickier. Seems like if one has a specification, it could be fuzzy-matched to the list of official R colors expressed in...

...22832 opcode=Query(0) > response=Yes > header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes > header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 > answers: nmb_name=__MSBROWSE__<01> rr_type=32 rr_class=1 ttl=259200 > answers 0 char ...... hex 80000A000002 > Got a positive name query response from 10.0.0.2 ( 10.0.0.2 ) > validator failed > parse_nmb: packet id = 22832 > nmb packet from 10.0.0.2(35072) header: id=22832 opcode=Query(0) > response=Yes > header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Ye...

...at looks easier > > I was working on ldap to convert but I'll try ldb-tools > > I was off on a bash mission here is what I had so far it isn't correct > so I'll keep working on it > > #!/bin/bash > if [ "$(echo $1|wc -c)" = "41" ];then > hex=$(echo $1|base64 -d| od -x -w28 --endian=big|head -n1|sed > 's/^0000000 //'|sed 's/ //g') > echo ${hex} > hex_chunk=$(echo ${hex}|cut -c1-2); > echo ${hex_chunk} > rev=$(echo "ibase=16; ${hex_chunk}" | bc) > hex_chunk=$(echo ${hex}|cut -c3-4) > echo ${...

What is the HEX code for "transparent" color? I've tried "00000000" "FFFFFF00" "FFFFFFFF", but they don't work. Thanks [[alternative HTML version deleted]]