SealsWithClubs.eu | Largest Bitcoin Poker Site | No Banking | Fast Cashouts

[notserp]

Does seals offer any kind of preventative measures againnst cheating?  If I can prove that i was colluded against, would anything be done?

Contact support.

This is a hypothetical question.

I have heard of people getting funds back when they have reported colluding and it could be proven.

yeah i got funds back twice awhile ago but i was not the one to report it

[1714027955]

1714027955

[1714027955]

1714027955

[apuestascoin]

Thinking about to accepting litecoin and dogecoin?

 

[darkmule]

I have heard of people getting funds back when they have reported colluding and it could be proven.

There was a ring of pretty brazen PLO cheats at the 6 handed tables for a while, and they shut those guys down, seized their funds and refunded players.  

There are ways of colluding that are not so readily apparent, though.  Just using collusive strategies in a few key hands can give a significant advantage without standing out like a sore thumb.  If the cheats don't get greedy they can get away with it for a while.  If they've already cashed out by the time they're caught, the site ends up holding the bag.  Pretty sure Seals would make good on it, but there's no guarantee any particular cheat gets caught.

Note:  not at all unique to Seals.  There was (and I assume is) plenty of suspicious activity even on a completely on the up and up cash site like Poker Stars, and they have a very active anti-cheating program.

What's funny is a lot of the worst cheats who get caught are also terrible players who lose despite cheating.  But a good player who cheats is pretty much unbeatable.

Anyway, the action on Seals is no more shady than on any other poker site and better than some real money sites, especially if you remember the old Absolute/UltimateBet, which was shady as hell.  Not just the notorious cases, but even at the lower levels where I played.  They honestly couldn't give a shit if people were blatantly colluding.

[wwwin]

I have heard of people getting funds back when they have reported colluding and it could be proven.

There was a ring of pretty brazen PLO cheats at the 6 handed tables for a while, and they shut those guys down, seized their funds and refunded players.  

There are ways of colluding that are not so readily apparent, though.  Just using collusive strategies in a few key hands can give a significant advantage without standing out like a sore thumb.  If the cheats don't get greedy they can get away with it for a while.  If they've already cashed out by the time they're caught, the site ends up holding the bag.  Pretty sure Seals would make good on it, but there's no guarantee any particular cheat gets caught.

Note:  not at all unique to Seals.  There was (and I assume is) plenty of suspicious activity even on a completely on the up and up cash site like Poker Stars, and they have a very active anti-cheating program.

What's funny is a lot of the worst cheats who get caught are also terrible players who lose despite cheating.  But a good player who cheats is pretty much unbeatable.

Anyway, the action on Seals is no more shady than on any other poker site and better than some real money sites, especially if you remember the old Absolute/UltimateBet, which was shady as hell.  Not just the notorious cases, but even at the lower levels where I played.  They honestly couldn't give a shit if people were blatantly colluding.

Yeah, I agree, probably Bovada has more colluders because their player number is different everytime they play.

[nioc]

ponzi bump

[lluboski]

1)  fucking donkdown.   my source of endless fail.  Please don't go there until I figure out wtf is wrong. 

2)  blind structure for Sunday 1k is in need of some levels IMO.   I am not opposed to crowd-sourcing a newly updated "normal" structure and applying it slowly to our bigger MTTs.  Just be warned, this won't go fast even once I have the structure in hand and approved by most.   It will certainly help to have something ready to fire.    obviously 150-300 a/25 was missing throughout.  This will be corrected, eventually.   Feel free to fire out some structures that will work properly for both 1500 and 3k chips. 

2) All I would like to see for Sunday 1k is change levels from 8 min to 10 min and add 300 BB level.
   

[notserp]

down?

[tonino]

down?

yeah what happened? did they run with gox together? 

[notserp]

i dont know but i was just starting to run good on the omaha tables

[tonino]

i dont know but i was just starting to run good on the omaha tables

and then what happened?

[donk4u]

Looks like the denial of service specialist is back in town.

[NLNico]

URGENT: We are under a DNS hijacking attack. If your browser warns you about an untrusted certificate, DO NOT login to the site. -ST6

URGENT: If anyone is unfamiliar with what to watch out for, here it is in Chrome / Firefox / Internet Explorer: https://i.imgur.com/4dTNmhr.png  - ST6

URGENT: News from Android developer that users should avoid using Android until a client update is pushed that detects the attack.

If you have client version v0.2.18 of the Desktop client and are logging in, the attack would be detected and you should be safe.

https://twitter.com/SealsWithClubs

[halcyon]

what´s the worst that can happen when one does login via a wrong certificate 
Can´t imagine how a potential hacker would get my seals password by doing this.

[NLNico]

I am not an expert at server level, but my understanding is this:

The certificate makes sure you are connected to the right server. So if there is an error, there is a server (from the hacker) between you and the actual Seals server. Obviously the hacker would log your password as you login.

Basically you should never add an exception when you see an untrusted certificate error. (unless you are a developer and know what you are doing or smth)

Luckily most times this error means an expired certificate, but in this case it was actually a hacker. According to the Seals dev this attack was "limited".

[Micon]

Right from ST6:


We're currently under what is called a DNS hijacking attack. This is where the attacker tries to hijack all traffic going to the sealswithclubs.eu domain to redirect to his server, thus putting himself in the middle of all communications.

If you're using the browser, you might see an invalid certificate message if you're suceptible to this attack. It is critical you do not proceed after seeing this message. It'd be best to just wait it out. For an example of these messages on common browsers, you can see the image here: https://i.imgur.com/4dTNmhr.png

If you're using the Desktop Client, be certain you're using the newest v0.2.18 version. This one will refuse to communicate with the bad guy's server, which will protect your credentials. However, this may temporarily prevent you from using our site. Again, it's best you just wait it out. If you want to try to fix the issue, make sure you following the install instructions for the client carefully:
> Please follow these install instructions carefully to prevent any issues:
> 1. Remove any copy of the old client by deleting its folder.
> 2. Download the extracting archive below.
> 3. Find where you have downloaded the file to.
> 4. Double-click the file from the download location. On Windows, a black
> console window will pop up while it extracts the client. On Mac/Linux,
> extract the file using the archive tool.
> 5. When step 4 is finished, you may see a swc_client folder in the same place
> you ran the downloaded file from. If so, open that folder.
> 6. You’ll see a swc_client program with an icon of a seal. Double-click that to
> run the client. Do not move that program out of its home folder or it may not
> be able to communicate with the server properly.

DO NOT use the Android client until a new update is pushed. It is the most suceptible client out of all three to fall for the attack without warning.

[Micon]

 -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We're currently under what is called a DNS hijacking attack just past midnight Las Vegas time 2014-02-26. This is where the attacker tries to hijack all traffic going to the sealswithclubs.eu domain to redirect to his server, thus putting himself in the middle of all communications. He'll likely be using this to gather user credentials to compromise the account at a later time.

If you're using the browser, you will see an invalid certificate message if you're susceptible to this attack. It is critical you do not proceed after seeing this message. It'd be best to just wait it out. For an example of these messages on common browsers, you can see the image here: https://i.imgur.com/4dTNmhr.png

If you're using the Desktop Client, be certain you're using the newest v0.2.18 version which can be found at https://sealswithclubs.eu/pc-client/. The newest version will refuse to communicate with the bad guy's server, which will protect your credentials. However, this may temporarily prevent you from using our site. Again, it's best you just wait it out. If you want to try to fix the issue on your end, make sure you following the install instructions for the client carefully:
> Please follow these install instructions carefully to prevent any issues:
> 1. Remove any copy of the old client by deleting its folder.
> 2. Download the extracting archive below.
> 3. Find where you have downloaded the file to.
> 4. Double-click the file from the download location. On Windows, a black
> console window will pop up while it extracts the client. On Mac/Linux,
> extract the file using the archive tool.
> 5. When step 4 is finished, you may see a swc_client folder in the same place
> you ran the downloaded file from. If so, open that folder.
> 6. You’ll see a swc_client program with an icon of a seal. Double-click that to
> run the client. Do not move that program out of its home folder or it may not
> be able to communicate with the server properly.

DO NOT use the Android client until a new update is pushed. It is the most suceptible client out of all three to fall for the attack without warning.

If you worry that you have been compromised, you can e-mail support@sealswithclubs.eu specifically stating your account name and that you'd like to have the account temporarily locked. As long as your e-mail matches your account, we will fulfill you request. As soon as it is safe, we will e-mail you back when we've unlocked the account again for you.

- - X @ SealsWithClubs
GPG/PGP Pub Key: ​http://pastebin.com/raw.php?i=1Rse0Xzt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (MingW32)

iQIcBAEBAgAGBQJTDirsAAoJECPwCPQtsswGmgAP/0uJ342Cnq3V7+W2rC1WpaI0
MdQF9MbaQFFTdktq7BobCu7FrjNRmKzSI/IqJ9LMJ3naEyWSGlLavgs8LGZIqKlQ
gRKAm7gP8wFkFt2Mg0GeXaTsubjnq/6/lnjDbriZFL9iZYVASJcIAsKxQSDitKvF
BJm+JWjXH6SJ8R+fO9ACQaf73FHdQyNxSuvBxN9ex+jjtcE5S/hzJ4DMhyaqGZ/d
i+u9GwTdbfQJyzqjbWL/x1a6jhL5Z4YRsWgqr0vj3GznATPOCuPFR/IKFwydIQFS
Bo3fPMQ3lgL64/jE1h2H7nfBMhBUsPQ/gNIuwwSFuehY/O8atr3SP5tSEiaPsmHM
Q0crZNNveeiQxw1UMxEpiqHx5tBsu9rPA/m5aWuwgHMIEisxdG2zjkqVnHy2pk75
vbi7YYJeqP+VN0fe5YnkViVN7I9gNIvLEmRhNo6Jlua7CwPr0ILZrbfgkH7iuF7y
pUsvZ8FEq+tqmzvos9LpkY4kU8TmapGH1wh2iKwAUoZUhIilmhb2lrQ4gwkIBLWP
91G0aE5QE3VqVO9Ble9Wz3q808DPB2G9KBIepugQk1sv/zNIqczJadhMOyM5qrQr
9tBaLUJlaYFLlmQYg//YNIY1G3bs6DZu3D5Oot/c1ifr5jeTKtNjJM/sqywbNWry
uFPTchqNDmUai6Af99rl
=Qjrw
-----END PGP SIGNATURE-----

[donk4u]

I am  playing now when I try and access cashier get a cannot communicate with cashier error which is usually a pre cursor to some sort of crash.

[cAPSLOCK]

what´s the worst that can happen when one does login via a wrong certificate 
Can´t imagine how a potential hacker would get my seals password by doing this.

Man in the middle

DO NOT LOG IN IF YOU SEE A BAD CERT.

If you have you better get them to lock your account, and change passwords anywhere else you use that one.  You will have just given it to the hacker.

[curtl]

Man in the middle

DO NOT LOG IN IF YOU SEE A BAD CERT.

If you have you better get them to lock your account, and change passwords anywhere else you use that one.  You will have just given it to the hacker.

One trick I always use with sites when I have a concern is to type in a random wrong password the first time.  If I get an error message, then I have a reason to believe I am at the correct site.

[Micon]

ST6 reports that the cert issue from earlier today may have been a bug and not an attack.

It is always best to stay vigilant, but this does appear to be a non-issue at this point.  Anyone who hits the site and gets a bad cert please report publicly.