search for: dek

...e() [1] "2001-11-21 16:00:23 Romance Standard Time" > > summary( hbl ) sample lab dev cal day HbA1c% 0289 3962: 50 SDC:1055 nyTosoh :470 BioRad :135 Min. :1.0 Min. : 4.700 0308 5530: 25 AAS: 74 Tosoh : 74 DEKS-0521:577 1st Qu.:6.0 1st Qu.: 7.300 0303 9481: 25 V2BioRad:450 DEKS-1321:276 Median :7.0 Median : 8.200 0303 8453: 25 VCBioRad:135 Tosoh :141 Mean :6.8 Mean : 8.583 0299 7761: 25 3rd Qu.:8.0 3rd Qu....

...SH with LibreSSL 2.6.x fixes the issue. I had fixed this > issue early on with LibreSSL 2.7 by converting the key to "new file > format" (to verify the ecdsa key wasn't corrupted I loaded it in > > Fail: > -----BEGIN EC PRIVATE KEY----- > Proc-Type: 4,ENCRYPTED > DEK-Info: AES-128-CBC,<snip> > > -----BEGIN RSA PRIVATE KEY----- > Proc-Type: 4,ENCRYPTED > DEK-Info: AES-128-CBC,<snip> > > Success (both keys after converting): > -----BEGIN OPENSSH PRIVATE KEY----- > > I've been digging through ssh-keygen to find a way t...

...>>> issue early on with LibreSSL 2.7 by converting the key to "new file >>> format" (to verify the ecdsa key wasn't corrupted I loaded it in >>> >>> Fail: >>> -----BEGIN EC PRIVATE KEY----- >>> Proc-Type: 4,ENCRYPTED >>> DEK-Info: AES-128-CBC,<snip> >>> >>> -----BEGIN RSA PRIVATE KEY----- >>> Proc-Type: 4,ENCRYPTED >>> DEK-Info: AES-128-CBC,<snip> >>> >>> Success (both keys after converting): >>> -----BEGIN OPENSSH PRIVATE KEY----- >>&gt...

...ebug3: Not a RSA1 key file /Users/jd/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace ... debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype The ssh connection attempt just hangs and sits at: ... debug2: service_accept...

.... I was wondering if there is a way to get a Fedora kernel and boot with that instead of my host kernel. Anyway, including the diagnostic output in case it helps. libguestfs: new guestfs handle 0x12da3c0 libguestfs: [00000ms] febootstrap-supermin-helper --verbose -f checksum '/usr/local/home/dek/sw/libguestfs-1.12.3/lib/guestfs/supermin.d' x86_64 supermin helper [00000ms] whitelist = (not specified), host_cpu = x86_64, kernel = (null), initrd = (null), appliance = (null) supermin helper [00000ms] inputs[0] = /usr/local/home/dek/sw/libguestfs-1.12.3/lib/guestfs/supermin.d checking modpa...

Hi, After reading through the btrfs documentation I''m curious to know if it''s possible to ever securely erase a file from a btrfs filesystem (or ZFS for that matter). On non-COW filesystems atop regular HDDs one can simply overwrite the file with zeros or random data using dd or some other tool and rest assured that the blocks which contained the sensitive information have

...3: Not a RSA1 key file /home/andreas/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whites...

...pdate my 2048-bit keypairs to 4096 bits, it really doesn't matter that much, because they're still only encrypted with 3DES, which provides an effective 112 bits of symmetric encryption strength: $ head -4 ~/.ssh/id_rsa -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,XXXXXXXXXXXXXXXX $ According to NIST[1][2], a minimum of 112-bit symmetric / 2048-bit asymmetric keystrength is recommended for protection up until about 2030. For protection beyond 2030, or for the paranoid, larger keysizes are recommended. Other recommendations (e.g.,...

*Hola!!! resulta que tengo unos datos de divisas ordenados por fechas (días) los que he convertido a formato tipo YYYY-MM-DD donde DD siempre es 01:* * * * EUR.resto$date<-as.Date(EUR.resto$date) EUR.resto$mo <- substr(EUR.resto$date,6,7) EUR.resto$yr <- substr(EUR.resto$date, 1,4)

Hello! I am not able to joing new Samba DC to existing domain: Linux side: OS: Centos 7 Samba version: 4.9.8 (Tranquil repo) Hostname: adserver9 Windows side: OS: Windows Server 2016 Domain/forrest level: Windows Server 2008 R2 Hostname: adserver8 Domain: spcr.local I am following this guide: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory I am getting this

...EM private key done: type RSA debug1: identity file /.ssh/identity type -1 debug1: identity file /.ssh/id_rsa type -1 debug2: key_type_from_name: unknown key type '-----BEGIN' debug2: key_type_from_name: unknown key type 'Proc-Type:' debug2: key_type_from_name: unknown key type 'DEK-Info:' debug2: key_type_from_name: unknown key type '-----END' debug1: identity file /.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version OpenSSH_2.9.9p2 debug1: match: OpenSSH_2.9.9p2 pat ^OpenSSH Enabling compatibility mode for protocol 2.0 debug1: Local v...

http://bugzilla.mindrot.org/show_bug.cgi?id=887 Summary: Problem connecting OpenSSH Client to a F-Secure SSH Server Product: Portable OpenSSH Version: -current Platform: All OS/Version: other Status: NEW Severity: major Priority: P2 Component: sftp AssignedTo: openssh-bugs at

...on every vNIC until it gets a response (or the vNIC list ends). I would like to know if there is a way to specify that the dhcp request should be triggered on a specific interface and if it fails stop or try again on same interface (if rebootTimeout is set). Best Regards -- Pasquale Porreca DEK Technologies Via dei Castelli Romani, 22 00040 Pomezia (Roma) Mobile +39 3394823805 Skype paskporr

On 13/07/2019 13:03, Michal Sl?dek via samba wrote: > Hello! > > I am not able to joing new Samba DC to existing domain: > > Linux side: > OS: Centos 7 > Samba version: 4.9.8 (Tranquil repo) > Hostname: adserver9 > > Windows side: > OS: Windows Server 2016 > Domain/forrest level: Windows Server 20...

...g3: Not a RSA1 key file /Users/peter/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whites...

https://bugzilla.mindrot.org/show_bug.cgi?id=3147 Bug ID: 3147 Summary: Confusing error message when the public key is missing. Product: Portable OpenSSH Version: -current Hardware: All OS: OpenBSD Status: NEW Severity: trivial Priority: P5 Component: ssh

...sh_connect: needpriv 0^M debug1: Connecting to localhost [127.0.0.1] port 22.^M debug1: Connection established.^M debug2: key_type_from_name: unknown key type '-----BEGIN'^M debug2: key_type_from_name: unknown key type 'Proc-Type:'^M debug2: key_type_from_name: unknown key type 'DEK-Info:'^M debug2: key_type_from_name: unknown key type '-----END'^M debug1: identity file /home/dave/.ssh/id_rsa type 1^M debug1: identity file /home/dave/.ssh/id_rsa-cert type -1^M debug1: identity file /home/dave/.ssh/id_dsa type -1^M debug1: identity file /home/dave/.ssh/id_dsa-cert t...

...a type 1 debug3: Not a RSA1 key file /root/.ssh/id_dsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: no key found debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: no key found debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: no key found debug3: key_read: no space debug3: key_read: no space debug3: key_read: no space debug3: key_read: no space debug3: key_read: no space debug3: key_read: no space debug3: key_read: no space debug3: key_read: no space debug3: key_read: no space debug3: key_re...

I'm sorry, but grep -i crypt /var/log/anaconda/anaconda.program.log returns nothing. But I have got an entry in /etc/crypttab. I only found this with grep -i luks /var/log/anaconda/anaconda.*: /var/log/anaconda/anaconda.storage.log:20:47:55,959 DEBUG blivet: LUKS.__init__: /var/log/anaconda/anaconda.storage.log:20:49:25,009 DEBUG storage.ui: LUKS.__init__:

I've just compiled and installed openssh-2.9.9p2 (compiled against openssl-0.9.6b using gcc-3.0.0) on a Slackware 7-based Linux machine (kernel 2.4.6ac2). The previously installed version was 2.9p2, compiled against openssl-0.9.6a, also with gcc-3.0.0, but with a different build of gcc-3.0.0. Everything seems to work fine except for one problem: passphrase matching for ssh2 keys