<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAP userid password cracking tool? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487863#M1062335</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; we either need to&lt;/P&gt;&lt;P&gt;&amp;gt; 1) chg the ALEREMOTE password and update all the corresponding SM59's in all the different systems &lt;/P&gt;&lt;P&gt;&amp;gt; 2) somehow figure out what the current password is, so we "know" what it is and can then create a new Source system connection in RSA1 and feed it the ALEREMOTE password&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; sounds like there is no way for us to use the latter option sadly...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) will be your best short-term option. Please do investigate the option of 'trusted rfc'  to rid your system of ale passwords completely. The problem you're facing should be a good motivation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Sep 2008 15:50:18 GMT</pubDate>
    <dc:creator>jurjen_heeck</dc:creator>
    <dc:date>2008-09-10T15:50:18Z</dc:date>
    <item>
      <title>SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487851#M1062323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi - can anyone confirm if SAP has a tool/utility they can use to crack a password - we have a situation where it is much easier for us if we could have them help us determine what a password is for an ALE user than changing it and aligning the new pwd is the many different places it is used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i assume SAP has a tool for this, but not sure if they are willing to help customers w/ it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i can see the hash code in usr02.bcode field for my user in question and could provide them that info...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 00:49:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487851#M1062323</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T00:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487852#M1062324</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; hi - can anyone confirm if SAP has a tool/utility they can use to crack a password - we have a situation where it is much easier for us if we could have them help us determine what a password is for an ALE user than changing it and aligning the new pwd is the many different places it is used.&lt;/P&gt;&lt;P&gt;To avoid problems like this one have a look at trusted rfc connections. That way there is no need to store passwords.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; i assume SAP has a tool for this, but not sure if they are willing to help customers w/ it.&lt;/P&gt;&lt;P&gt;I doubt it and I actually hope they do not have it. How would that help customers to become sox-compliant? &lt;/P&gt;&lt;P&gt;Besides that hashing passwords is generally a one-way trick. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; i can see the hash code in usr02.bcode field for my user in question and could provide them that info...&lt;/P&gt;&lt;P&gt;Hopefully they can't do a thing with that &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 06:12:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487852#M1062324</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-09-10T06:12:37Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487853#M1062325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The idea is to manage the connections by co-ordinating the passwords, both the &lt;STRONG&gt;one&lt;/STRONG&gt; enetered in SU01 and the &lt;STRONG&gt;one&lt;/STRONG&gt; entered in SM59.&lt;/P&gt;&lt;P&gt;This is much easier and more secure when you respect the cardinality of the connections, i.e. avoid MANY (sm59) to ONE (su01) connections.&lt;/P&gt;&lt;P&gt;Besides, in higher releases you cannot even see the SM59 hash in RFCDES anymore....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Such a publicly available tool would be predestined for misuse... &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 06:43:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487853#M1062325</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T06:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487854#M1062326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ben,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; i assume SAP has a tool for this, but not sure if they are willing to help customers w/ it.&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Beleave me or not:&lt;/P&gt;&lt;P&gt;I can confirm, that we (SAP) do not have such a tool.&lt;/P&gt;&lt;P&gt;Do you think, that high sensitive customers still would buy the software, if SAP could crack their passwords with a tool?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nevertheless: any password is crackable. It is only a quesiton of which time you are willing to spend on that crack (100 years, 200 years,....).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So do not calculate with that possibility of password decryption from SAP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b.rgds,&lt;/P&gt;&lt;P&gt;Bernhard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 07:48:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487854#M1062326</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2008-09-10T07:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487855#M1062327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; I can confirm, that we (SAP) do not have such a tool.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for confirming! Sigh of relief here &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 08:00:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487855#M1062327</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-09-10T08:00:29Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487856#M1062328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Of course, SAP has such a tool. Not in a complete form, but the most important and hardest to write part is there. Just reflect what is necessary:&lt;/P&gt;&lt;P&gt;1. A dictionary. Freely available on the net.&lt;/P&gt;&lt;P&gt;2. The hash of the password to crack. Is in the database.&lt;/P&gt;&lt;P&gt;3. The seed (I assume that SAP uses a seed; previous versions didn't have a seed). Is most probably in the database as well.&lt;/P&gt;&lt;P&gt;4. The hashing algorithm. This is built in every SAP kernel because this is also needed to verify a password during logon and to set a password.&lt;/P&gt;&lt;P&gt;5. A small framework tying everything together. This is trivial and there are enough password crackers around that show somebody how to write such a framework.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Of course, trying out all password is a time consuming task that can be highly parallelized, however.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, strictly spoken, SAP did not tie everything together. But a decent programmer at SAP has such a tool written inside a week.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 10:07:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487856#M1062328</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T10:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487857#M1062329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; 4. The hashing algorithm. This is built in every SAP kernel because this is also needed to verify a password during logon and to set a password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No, we can only encrypt, not decrypt with the hash algorithm used.&lt;/P&gt;&lt;P&gt;b.rgds, Bernhard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 11:25:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487857#M1062329</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2008-09-10T11:25:19Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487858#M1062330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think that you have misunderstood the question...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;He does not want to brute force or dictionary attack the SU01 password. &lt;/P&gt;&lt;P&gt;He wants to reverse the SM59 password so that he can set it in the target SU01 without "disturbing" the SM59 settings of (possibly) other systems using the same ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All round bad idea...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 11:27:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487858#M1062330</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T11:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487859#M1062331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;No, we can only encrypt, not decrypt with the hash algorithm used.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Of course, otherwise it wouldn't be very useful. But there are ways around it; they are just time consuming. Please reconsider my post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Of course, SM59 will need to store passwords with a reversible algorithm. Otherwise, it would not be able to furnish the password to the "other" server. This is just obfuscation and it should be possible to crack this (you only have to look for it long enough in the code).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 12:26:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487859#M1062331</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T12:26:37Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487860#M1062332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hie Sietze (I suppose that this is your first name - sorry if not),&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Of course, SM59 will need to store passwords with a reversible algorithm. Otherwise, it would not be able to furnish the password to the "other" server. &lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we compare only the hash values during log on. So using sm59 there is no decryption for passing the password to the remote system. I don't know, where you have found the decryption coding....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b.rgds, Bernhard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 13:23:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487860#M1062332</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2008-09-10T13:23:45Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487861#M1062333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For an un-trusted RFC, the user is a background user (no dialog logon), so the password authentication seems to be taken care by the comparision of hash values (as suggested by Bernhard)..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For that matter, for a trusted RFC, where a dialog user becomes an RFC service user, it seems there isn't any password verification. Because the source system doesnot mantain any password in SM59 and the password in the destination can always be different from what the user is having in source system. At most the system would be checking if the user is locked/unlocked/validity period apart from the necessary auth objects S_RFC and S_RFCACL.&lt;/P&gt;&lt;P&gt;Correct me if I am wrong!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 13:51:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487861#M1062333</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T13:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487862#M1062334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks all for a lively (much more than i expected) discussion.  julius was right in my intentions...i am not trying to unearth a tool to crack passwords myself.  we just have a situation w/ many SM59's using an ALEREMOTE user - and no one knows what the current password is.  so if we need to create a new Source System in RSA1 for our BW system (which uses this ALEREMOTE user by default for the ALE/sm59's between systems) we either need to&lt;/P&gt;&lt;P&gt;1) chg the ALEREMOTE password and update all the corresponding SM59's in all the different systems &lt;/P&gt;&lt;P&gt;2) somehow figure out what the current password is, so we "know" what it is and can then create a new Source system connection in RSA1 and feed it the ALEREMOTE password&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sounds like there is no way for us to use the latter option sadly...&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 15:06:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487862#M1062334</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T15:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487863#M1062335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; we either need to&lt;/P&gt;&lt;P&gt;&amp;gt; 1) chg the ALEREMOTE password and update all the corresponding SM59's in all the different systems &lt;/P&gt;&lt;P&gt;&amp;gt; 2) somehow figure out what the current password is, so we "know" what it is and can then create a new Source system connection in RSA1 and feed it the ALEREMOTE password&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;gt; sounds like there is no way for us to use the latter option sadly...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) will be your best short-term option. Please do investigate the option of 'trusted rfc'  to rid your system of ale passwords completely. The problem you're facing should be a good motivation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 15:50:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487863#M1062335</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-09-10T15:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487864#M1062336</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;BW would have been my second guess. That you are forced to have uncardinal RFC connections is in my opinion a design error in there somewhere...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My first guess had something to do with your email address which is visible in your SDN profile - you can use the option "Hide" to save it in a type of "Secure Store", which then only you can see in cleartext. (sorry for the pun &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Trusted RFC is a valid and popular solution, but you have to be very carefull in how you set it up.&lt;/P&gt;&lt;P&gt;Worste case everyone can logon as anybody else and per default you loose a layer of application security.... (except for DDIC and SAP*).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The thing about stuff like this (cracking passwords etc) is that anyone smart enough to find and work it out, is most likely smart enough to know that they should keep it to themselves... &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 15:56:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487864#M1062336</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T15:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487865#M1062337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; The Trusted RFC is a valid and popular solution, but you have to be very carefull in how you set it up.&lt;/P&gt;&lt;P&gt;&amp;gt; Worste case everyone can logon as anybody else and per default you loose a layer of application security.... (except for DDIC and SAP*).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In detail: The RFC-user must have the object S_RFC_ACL with proper values in his profile on the trusting side. Luckily this is one of the objects never included in SAP_ALL.&lt;/P&gt;&lt;P&gt;So if you connect from system A to system B you need to have an account with identical naming on either side and must have this object in the profile on system B. Trusted RFC's can both be set up with fixed userid's and 'logon user' or 'current user' (no system in reach at the moment, don't know the exact wording). The actual rights of the rfc user on system B determine what can be done there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The risk Julius mentiones is a bit like putting op a sticky note with the password beacuse you do not want to lose it again..... just giving everyone a 'starred-out' S_RFC_ACL on all systems and trust they do not know how to use an rfc connection.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 17:39:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487865#M1062337</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-09-10T17:39:31Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487866#M1062338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; ... per default you loose a layer of application security...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; The actual rights of the rfc user on system B determine what can be done there.&lt;/P&gt;&lt;P&gt;That depends on how your system is configured...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a old thread here about that topic - the distinction between an "authentication check" and an "authorization check". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Search terms:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; In the real world, if I present my passport to somebody at an airport they are able to look at it and use it to determine my real identity, then they can decide whether I am allowed to enter the airport to board an airoplane.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;=&amp;gt; "Somebody at the airport" should also determine which airoplane you board... (the entry points to the destinations).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2008 19:10:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487866#M1062338</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-10T19:10:24Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487867#M1062339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; In detail: The RFC-user must have the object S_RFC_ACL with proper values in his profile on the trusting side. Luckily this is one of the objects never included in SAP_ALL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi Jurjen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just a little comment on this.... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;==&amp;gt;don't rely on that ..... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a look at SAP note #410424 --&amp;gt;ADD_S_RFCACL.... I always set the switch to 'YES' to avoid problems for my sap_all users... &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;b.rgds, Bernhard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 05:39:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487867#M1062339</guid>
      <dc:creator>Bernhard_SAP</dc:creator>
      <dc:date>2008-09-11T05:39:38Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487868#M1062340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; Have a look at SAP note #410424 --&amp;gt;ADD_S_RFCACL.... I always set the switch to 'YES' to avoid problems for my sap_all users... &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Are your SAP_ALL "users" (a.k.a. SAP_ALL "complainers") aware than &lt;STRONG&gt;anyone&lt;/STRONG&gt; on the trusted system can logon to the trusting system as them without needing nor changing the password?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 05:48:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487868#M1062340</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T05:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487869#M1062341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; I always set the switch to 'YES' to avoid problems for my sap_all users... &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Okay, I forgot the words "by default" &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I never change this switch but prefer to tell the SAP_ALL users they might run in to the occasional boundary and that it's also for their safety. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Doesn't really matter because it only changes their request from "give me SAP_ALL &lt;U&gt;and&lt;/U&gt; SAP_NEW" to "make sure I can do everything". The following discussions are all too familiar......&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nice topic!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 06:18:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487869#M1062341</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-09-11T06:18:34Z</dc:date>
    </item>
    <item>
      <title>Re: SAP userid password cracking tool?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487870#M1062342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Last night I started thinking about this discussion, and two questions striked me. I am putting them on this forum first thing in the office:)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(1) Which table contains the hash value of the password which is mentioned in sm59-untrusted RFC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(2)Although manual update of SAP standard tables is a bad practice. What if somebody copies the hash value of password from usr02 of destination system and updates that table (containing sm59 password) in the source system? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would love to know what have a I overlooked!!:)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2008 08:16:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-userid-password-cracking-tool/m-p/4487870#M1062342</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-09-11T08:16:53Z</dc:date>
    </item>
  </channel>
</rss>

