Jump to content

CA Certiciates and the hak5 irc


0xicl33n
 Share

Recommended Posts

I just got my bash bunny in the mail today, im currently trying to set it up the way i like but..CA certs are broken.. I cant connect to github and i cant connect to the IRC

With wget:

Resolving github.com (github.com)... 192.30.253.112, 192.30.253.113
Connecting to github.com (github.com)|192.30.253.112|:443... connected.
ERROR: The certificate of 'github.com' is not trusted.
ERROR: The certificate of 'github.com' is not yet activated.
The certificate has not yet been activated

With git clone:

fatal: unable to access 'https://github.com/git-repo-name/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

 

As for the hak5 irc, it seems to be broken too! :D 
 

irssi snip:

 18:32          * | Looking up irc.hak5.org
 18:33  Reconnecting to irc.hak5.org [159.203.209.103] port 6697 - use /RMRECONNS to abort
 18:33  Certificate Chain:
 18:33    Subject: CN: irc.vhirc.net
 18:33    Issuer:  C: US, O: Let's Encrypt, CN: Let's Encrypt Authority X3
 18:33    Subject: C: US, O: Let's Encrypt, CN: Let's Encrypt Authority X3
 18:33    Issuer:  O: Digital Signature Trust Co., CN: DST Root CA X3
 18:33  Protocol: TLSv1.2 (256 bit, ECDHE-RSA-AES256-GCM-SHA384)
 18:33  EDH Key: 256 bit ECDH: prime256v1
 18:33  Public Key: 2048 bit RSA, valid from Aug 25 10:27:00 2016 GMT to Nov 23 10:27:00 2016 GMT
 18:33  Public Key Fingerprint:  B0:3F:39:53:31:60:CA:3F:E2:82:75:8F:F9:38:CB:2C:B2:55:48:EB:22:75:CC:EB:C5:9C:29:2B:04:7A:0D:3F (SHA256)
 18:33  Certificate Fingerprint: E9:F4:77:A7:E2:3E:62:E6:6E:27:95:7A:43:1E:21:EA:E0:64:81:27:65:28:16:B9:76:E7:68:99:96:00:B0:26 (SHA256)
 18:33  GLib warning Could not verify TLS servers certificate: certificate has expired
 18:33          * | Connection lost to irc.hak5.org
 

Link to comment
Share on other sites

3 hours ago, Darren Kitchen said:

That's strange. I'm having no problem with either. The git you'll want is git@github.com:hak5/bashbunny-payloads.git or simply https://github.com/hak5/bashbunny-payloads

Ah, it wasnt the payloads i was after. I was really trying to install fish. It does that with any git repo

 

root@bunny:~# git clone https://github.com/fish-shell/fish-shell.git
Cloning into 'fish-shell'...
fatal: unable to access 'https://github.com/fish-shell/fish-shell.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

root@bunny:~# git clone https://github.com/0xicl33n/dotfiles.git
Cloning into 'dotfiles'...
fatal: unable to access 'https://github.com/0xicl33n/dotfiles/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
root@bunny:~

root@bunny:~# git clone https://github.com/0xicl33n/phonepwn.git
Cloning into 'phonepwn'...
fatal: unable to access 'https://github.com/0xicl33n/phonepwn/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

As for the irc, that was done on my host machine, not the bunny

Update:

T-the date on the bunny was completely screwed up! It said December 31 1969!

[root@bunny[/src]$date
Wed Dec 31 20:59:17 PST 1969
[root@bunny[/src]$ apt-get install ntp
[root@bunny[/src]$ntpd -gq
ntpd: time set +0.161456s
[root@bunny[/src]$date
Sat Mar  4 23:04:10 PST 2017

Fixing the date fixed everything. Except when i rebooted the bunny it was set back to 1969..It wont save the change.

Edited by 0xicl33n
Link to comment
Share on other sites

I had a few problems when running the BB from stock kali. It seemed like the clock time was off so i did an `apt-get install ntp ntpdate` and ran a `ntpdate -s time.nist.gov` to update it. I was able to do a gpg import and `apt-key add` after that. When you reset though, that clock time will get wiped away so you might want to add it to some kind of setup script whenever you need to pull down something like a git repo or gpg key.

I could be totally wrong though! it's what worked for me.

Link to comment
Share on other sites

On 3/6/2017 at 11:53 PM, nucleardreamer said:

I had a few problems when running the BB from stock kali. It seemed like the clock time was off so i did an `apt-get install ntp ntpdate` and ran a `ntpdate -s time.nist.gov` to update it. I was able to do a gpg import and `apt-key add` after that. When you reset though, that clock time will get wiped away so you might want to add it to some kind of setup script whenever you need to pull down something like a git repo or gpg key.

I could be totally wrong though! it's what worked for me.

 

The clock gets wiped every time you reboot the device for me, i cant save it. Mine wont save the time..at all..

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...